Bounded Intelligence Packs
projects owns a generic read-only assembly path:
declared materialized evidence → normalized evidence → declared joins
→ explicit agent judgments → deterministic rendered pack
It is separate from project commissioning: commissioning assembles static handoff material; this capability normalizes evidence, creates reviewable candidates, and renders validated FACT, INFERENCE, and RECOMMENDATION judgments.
Recipes use intelligence-pack-spec@1 under estate/intelligence/. Adapters currently support Chronicle JSONL, Capability Atlas JSONL, and bounded generic JSON/JSONL. Optional event/relationship sources remain coverage gaps until an authorized machine-readable snapshot is supplied.
TSE acceptance route
make intelligence-tse PAPER_KB_ROOT=/path/to/paper-kb PROJECTS_ROOT=/path/to/projects
The output is private/ignored. It never changes relationship, project, or institution truth. See the agent route for the required judgment discipline.
Adding a subject
Add a recipe with a subject, time window, declared adapters/sources, deterministic join policies, exact six sections, and human gates. A new subject must reuse adapters and joins; it must not add subject-name branching to the engine.
Implementation closure: TSE acceptance run
The private local TSE run consumed 300 bounded Chronicle records and 80 Capability Atlas records, emitted 30 declared tag-overlap candidates, and rendered eight validated judgments: 3 FACT, 2 INFERENCE and 3 human-gated RECOMMENDATION records. Authorized machine-readable event and relationship snapshots were not found/supplied, so both appear as explicit coverage gaps rather than negative claims. The same source inputs and judgment file produced byte-identical evidence, candidates, pages and manifest on a second run.
The non-TSE fixtures/demo.json recipe exercises the same generic JSONL adapter, declared tag join, validation and renderer. No TSE-specific branching exists in the assembler.
Deliberately not built: an institution database, crawler, entity resolver, embeddings/vector store, semantic search, CRM writer, outreach sender, scheduler or participating-repository runtime execution.