Product / Context
More context is not better context
Unbounded context wastes tokens, buries the signal, and slows every downstream decision. Omnacta Context seeks the smallest sufficient, current, and explainable context for the decision in front of it.
Structural, lexical, and Git sources are implemented for the engineering reference workflow. Semantic memory and cross-session validation are in active development.
Seven context sources
Each source contributes a different kind of signal. None is treated as sufficient on its own.
Structural
File and module layout, dependency graphs, build configuration.
Lexical
Direct text and symbol matches across the repository.
Semantic
Meaning-based retrieval over code and documentation embeddings.
Git
Commit history, blame, and change frequency for the affected paths.
Diagnostic
Compiler, linter, and test output relevant to the current task.
Instruction
Project rules, style guides, and agent-facing conventions.
User-selected
Files, links, or notes a user explicitly attaches to the mission.
What travels with every piece of context
Context is never used bare. Every retrieved item carries structured metadata so a decision can be explained after the fact.
| Field | What it captures |
|---|---|
| Provenance | Which source produced this context and how it was retrieved. |
| Freshness | How recently the underlying source was read or re-indexed. |
| Contradictions | Whether this context conflicts with another retrieved source. |
| Omissions | What was deliberately excluded and why, not silently dropped. |
| Confidence | How strongly this context is expected to be relevant to the decision. |
| Security class | Whether the content carries handling restrictions before reuse. |
Active stopping, not exhaustive retrieval
Context assembly stops once an active stopping certificate is satisfied: enough signal has been gathered to proceed with a bounded confidence interval, rather than continuing to pull in marginal material.
- Incremental indexing re-scopes context as the repository changes, instead of re-scanning everything.
- Invalidation removes stale context rather than letting it silently persist.
- Raw source content is not persisted in the mission ledger by default; only references and derived summaries are.
- Semantic memory validation/revocation is in development and not yet uniformly enforced across all sources.
Context feeds execution
Assembled context becomes the input to planning and capability selection in the Execution stage.