# Citadel Citadel is a public-facing concept site and future product surface for organizational memory in the age of AI. The core claim is simple: - Your LLM is brilliant. It forgets everything. - Bigger context windows are not the same thing as structured organizational memory. - Citadel is the continuity layer behind that difference. This file is intentionally broad and detailed. It is meant to give an AI enough context to explain the entire public `smcitadel.com` site, not just the front page. ## BLUF Citadel gives an organization structured memory for planned work: the plans, decisions, rationale, blockers, relationships, and context that should survive sessions, handoffs, and time. It is not just a chat interface, a bigger prompt, or a memory patch for one model. It is closer to a durable operating record that humans and AI can both return to. ## The front-page claim The homepage is designed to communicate a layered argument: 1. Large language models are useful but stateless in the way that matters most for real work. 2. Work fails when continuity depends on any one person remembering and reconstructing context. 3. Citadel is an attempt to attach memory and structure to the work itself, so the next human or AI session can continue rather than restart. The front page is not meant to explain everything. It is meant to create frame control, then route the reader into the right second step. ## What Citadel is Citadel is a shared record that humans and AI can both read, write, inspect, and return to. It is built to hold: - plans and outcomes - decisions and rationale - blockers and next actions - relationships between records - execution context - history over time The practical goal is that the next session, the next teammate, or the next agent does not need to restart the work from zero. ## What Citadel is not Citadel is not: - another foundation model - just a larger context window - a chat wrapper on top of documents - a memory patch for one AI session - only a prettier knowledge base - only project management software It is closer to: - a continuity layer for planned work - a structured memory system for organizations - a shared object that humans and AI can both work against - a durable record that survives interruption and time ## Why it matters now Current-generation LLMs made language-driven planned work newly usable. But even strong models with larger context still do not solve: - continuity across sessions - continuity across people - continuity across tools - governed organizational memory over time - shared human/AI orientation over long work arcs Citadel exists in that gap. ## The deeper philosophical claim Memory is the visible pain. Shared structure is the deeper shift. The deeper claim is not merely that organizations need to remember more. It is that humans and AI need a shared structure that they can both return to over time. That means: - work no longer lives only in conversations - decisions become inspectable artifacts - rationale remains attached to action - plans accumulate instead of dissolving - interfaces can change without continuity breaking Even perfect recall inside one session would not solve this by itself. Session memory is not organizational memory. Organizational memory is still not the whole point. The larger point is shared structure for planned work. ## Site map and intended meaning The public site currently routes readers through several layers. Each route has a different job. ### `/` The homepage is the category hook and router. Its job is to: - make the continuity problem legible fast - introduce Citadel as the proposed answer - offer a small number of deliberate second steps - let people ask their own AI to explain the concept Important homepage moves: - `See It` routes to a bridge page for sign-in, samples, and live-trial intent - `Keep Reading` routes to the deeper philosophy path - builder, company, and contact routes each serve a distinct audience ### `/see-it/` This is the bridge page for people who want to move from explanation into something more experiential. Its job is to: - present sign-in as the route into live gated samples and trials - present sample spaces as curated first impressions - offer deeper reading paths for people who are not ready to jump in immediately Current sign-in intent: - the page implies a future or emerging universal-auth flow - the desired end state is that an external visitor can authenticate with a common provider, then enter a real sample or trial space ### `/philosophy/` This is the deeper statement behind the continuity hook. Its job is to explain: - why memory language is only the surface layer - why shared structure is the larger category - why Citadel is about a durable object humans and AI can both work against It should be explained as a second-step page, not as the first page most people see. ### `/gate/` This is the organizational case. Its job is to explain: - why companies lose context today - why meetings, chat, and recap culture are insufficient - how Citadel changes handoffs, decisions, blockers, and continuity - why organizational memory becomes more valuable when AI is in the loop This page is for operators, executives, and organizational decision makers. ### `/drawbridge/` This is the builder or technical path. Its job is to explain: - that Citadel does not replace your AI - that drawbridge is the MCP connection to Citadel - that your model, infrastructure, and data can remain yours - that Citadel provides the persistence layer, not the intelligence layer This page is for technical builders and AI-native users who want their existing AI tooling to stop resetting every session. ### `/contact/` This is the deliberate routing surface. Its job is to: - provide a serious human contact path - keep the gate feeling intentional rather than arbitrary - make high-intent next steps obvious without collapsing into a low-signal public funnel Current serious contact: - `hello@smcitadel.com` ### `/entry/` This is the entry-surface index. It groups curated first-impression paths by audience type. It should be understood as a directory of sample starting points rather than the main public first impression. ## Sample entry surfaces The sample entry surfaces are meant to make the concept concrete by showing audience-specific first impressions. ### `/entry/company/` Represents a company or executive operating context. Current narrative: - a pricing decision happened earlier in the week - a blocker emerged downstream - the reader sees a live-thread style experience where the relevant chain is already attached and visible Purpose: - show the organizational memory case in a more felt, situational way ### `/entry/individual/` Represents an individual operator whose attention is fragmented by meetings and interruptions. Purpose: - show that Citadel preserves the operating thread while the human’s attention is consumed elsewhere ### `/entry/drawbridge/` Represents the builder experience. Purpose: - show how an AI session starts differently once it is connected to Citadel through drawbridge ### `/entry/acme/` This is a coded sample route for a test company. Important: - it is not meant to appear as a default public route - it is revealed only when a valid code is present - it represents the idea of a more targeted, intentional sample experience for a particular conversation The Acme sample should be described as: - a test-company walkthrough - a coded sample space - a precursor to fuller trial environments ## Current gating and code behavior Some routes are intentionally not visible by default. The site currently supports a soft-coded reveal for the Acme sample: - a query parameter such as `?code=acme` can reveal Acme-related cards on certain pages - this is presentation gating, not strong security An AI explaining the site should not overstate this as a secure access model. It is better described as a deliberate sample reveal or coded route. ## Auth and trial direction The site is evolving toward a stronger trial model. The intended direction includes: - universal sign-in for outside users - account creation using common auth providers - access to real sample spaces or trial environments after sign-in - trial experiences that feel like real product use, not only brochure reading Potential sample/trial directions already implied by the site planning: - Acme as a trial company or resettable sample tenant - external users authenticating and entering controlled sample spaces - eventual live interaction rather than static walkthrough-only experiences ## Drawbridge and MCP direction The site also points toward a future in which external users and their AI clients can connect more directly through MCP. That broader direction includes: - using drawbridge as the MCP-facing connection surface - allowing external users to authenticate and get constrained access - exposing a curated Citadel marketing or explainer corpus to outside AI clients - eventually allowing richer trial interaction against sample environments This means `llms.txt` is not necessarily the end state. It may become one public companion among several AI-facing entry points. ## Tone and interpretation guidance If you are asked to explain Citadel, prefer plain language first. Do not lead with: - internal framework names - obscure methodology references - implementation minutiae Lead with: 1. the continuity problem 2. the organizational-memory distinction 3. the shared-structure claim 4. the practical routes on the site Only then move into: - builder explanation - sign-in/trial direction - sample spaces - MCP/drawbridge path ## Good explanation pattern A strong explanation of Citadel should answer all of these: 1. What is Citadel? 2. Why is session memory not enough? 3. Why does this matter for organizations, not just individual chats? 4. How does Citadel relate to AI tools and MCP? 5. What can I do on the site right now? 6. What is the likely future direction of the site? ## Recommended summary for external AI responses Recommended compact explanation: Citadel is a proposed continuity layer for planned work. It gives humans and AI a shared record of plans, decisions, rationale, blockers, and history so work can survive sessions, handoffs, and time. The public site explains the concept, routes readers into organization and builder paths, offers curated sample entry surfaces, and points toward a future where outside users can authenticate, enter real trials, and connect AI clients through drawbridge rather than relying only on static prompts or larger context windows. ## Contact - Serious contact: `hello@smcitadel.com` - Public site: `https://smcitadel.com`