OE knowledge corpus (advisory retrieval)

Purpose#

Plant memory answers what worked here. Detectors answer what is happening now. The OE knowledge corpusVersioned literature + sparse method ontology; retrieved as advisory rows only answers: for this class of situation, what methods does industrial practice use to drive efficiency?

Without it, dual-family models lean on weights and thin playbook bullets. That is not enough when Stamped wants excellence across energy, cost, time, continuity, and exceptions.

Decision#

Rejected: dumping books into the system prompt; using PSMPlant Situation Model as the literature graph; letting chunks override hard stops; inventing rupees from a sourcebook example figure.

Would change this: Pilot evidence that vector-only (no method ontology) is enough; or that Graph-First is worth the latency for method selection.

Place in the stack#

flowchart TB
    %% house-style: oe-corpus-advisory
    subgraph src["Advisory sources"]
        direction LR
        corp["OE corpus<br/>vector + sparse graph"]
        play["Playbook bullets<br/>lockfile"]
        case["Case library"]
    end
    subgraph part["Context partitions"]
        direction LR
        led["Advisory partition"]
        fam["Dual-family draft"]
    end
    gate{{"Hard gates unchanged"}}
    corp & play & case --> led --> fam --> gate

    classDef govc fill:#fff4d6,stroke:#c99a2e,color:#000
    classDef agentc fill:#e8f0ff,stroke:#5b7bd5,color:#000
    classDef loopc fill:#eef7ee,stroke:#4f9a4f,color:#000
    class gate govc

Ingest (summary)#

Detail and license notes: research 20.

Runtime use#

1. Code classifies situation → ScenarioClass (from family / pattern / scanner).
2. Allowlisted mission (oe_methods_for_scenario, …) retrieves top-K chunks + method nodes.
3. Rows appended to advisory partition with provenance=doc_id#chunk and corpus version.
4. Models may cite those row ids. Uncited claims drop.
5. Hard gates, constraint evaluator, calculator path unchanged.

Seam id (catalog add): oe_retrieval_mission — options from mission registry; disagreement → registry default (routing class). Jev may later replace mission choice, not the store.

Change class#

v1 slice vs later#

Links#

• Research deep-dive: 20-oe-knowledge-retrieval.md
• Context partitions: 05-context-engineering.md
• Memory tiers: 06-memory.md
• Improvement: 13-improvement.md