Declared vs Indexed Knowledge

Declared knowledge is information a person explicitly stated is true, such as a recorded decision or a set status. Indexed knowledge is information a system infers by scraping and searching activity like messages, documents, and commits. The difference matters because declared knowledge carries authority and a clear source, while indexed knowledge is a guess about intent that can confidently surface something stale, out of context, or never actually agreed.

Most AI-over-your-company tools are indexing systems. They embed your Slack, wiki, and tickets, then answer by retrieving the closest-matching text. That is powerful for discovery and dangerous for ground truth, because a search hit is not the same as a fact someone stands behind. This is the same reason async status should be stated, not reconstructed, as argued in async status: declared, not inferred.

The core difference

Declaration is an act of authorship; indexing is an act of observation. When you declare that the team chose Postgres, you are asserting a fact with your name on it. When an index finds a two-month-old thread debating Postgres versus Dynamo, it retrieves a conversation, not a conclusion. The index cannot tell whether the debate ended, which side won, or whether the decision was later reversed.

That gap is the entire problem. Indexed systems infer state from the residue of work, and residue is ambiguous. Declared systems store state as a deliberate statement, which is why they can answer "what did we decide" with authority. The broader case for building on declared state is in declared state engineering.

Declared vs indexed, side by side

Property	Declared	Indexed
Source of truth	A person's explicit statement	Inferred from activity
Authority	Attached, named	None; retrieval only
Handles staleness	Explicit expiry or update	Surfaces old text as current
When answer is missing	Says "not declared"	Fabricates a plausible one
Best use	Decisions, status, ground truth	Discovery, search, exploration

Where indexing quietly fails

Indexing fails hardest exactly where you most need to trust the answer. Because it retrieves the closest text rather than the agreed fact, it produces three predictable errors.

• Stale-as-current: it surfaces a decision that was reversed last quarter because the old message still ranks well.
• Debate-as-decision: it treats an unresolved discussion as if it were a conclusion.
• Confident fabrication: when nothing relevant exists, it generates a fluent answer anyway rather than admitting the gap.

None of these are model bugs you can prompt away. They are structural: an index has no concept of authority or finality, so it cannot distinguish a fact from a fragment. Grounding AI in what a company actually decided requires declared sources, which is the argument in how to ground AI in company decisions.

When to use each

Use indexing for discovery and declaration for ground truth. Semantic search over your documents is genuinely useful when you are exploring, brainstorming, or trying to find where something was discussed. It becomes hazardous the moment its output is treated as an authoritative answer to "what is true right now."

The practical rule: never let an indexed answer stand as a decision or a status. If a colleague will act on it, it should trace back to a declared record with a name attached. Discovery can be fuzzy; ground truth cannot.

Why StandIn declares

StandIn is a declared-knowledge system on purpose. It does not guess your team's state by scraping activity. It answers only from decisions, status, and context that people explicitly declared, so every answer is traceable to a source and a person. When a teammate asks something that was never declared, the representative refuses to speculate rather than fabricating a plausible reply.

That refusal is the feature. An indexed system fills silence with a guess; a declared system reports the gap honestly, which is both more trustworthy and a signal that a decision still needs to be made. The same principle drives our stance in silence over speculation, and it is why AI that answers only from what your team wrote is the safer foundation for anything that carries authority.

Common Questions

What is the difference between declared and indexed knowledge?

Declared knowledge is stated explicitly by a person and carries authority and a source. Indexed knowledge is inferred by a system that scrapes and searches activity like chats and docs. Declaration answers "what did we decide" with a named fact; indexing only retrieves the closest matching text.

Is indexing my company data with AI a bad idea?

Not for discovery. Semantic search over documents helps you explore and find where things were discussed. It becomes risky when its output is treated as ground truth, because an index cannot tell a reversed decision from a current one or a debate from a conclusion.

Why does an indexed AI make things up?

Because retrieval has no concept of a missing answer. When nothing relevant exists, the model still generates fluent text rather than reporting the gap. A declared system avoids this by only returning facts a person asserted and refusing when none was declared.

Can I combine declared and indexed approaches?

Yes, and many teams should. Use indexing for exploration and discovery, but require that anything acted on as a decision or status trace to a declared record with an owner. Keep the fuzzy layer for finding things and the declared layer for ground truth.