mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-07-31 16:16:26 +00:00
20e99f434c
Wave 1 remainder + Wave 2 design-first specs, completing one build plan per sub-organ: - B1 tarot emulator, B2 SOUL/Big-3, B3 Celtic Cross - C2 4+4 metacog, C3 inference cycle, C4 Brain - D1 Ada border, D2 the medium, D3 mini-rag - E1 3 GnuCOBOL invariant stores, E2 VARIANT stores, E3 RAG family - F1 MoRAG, F2 SAE monitor, F3 subagents - G1 stress-loop contract, G2 governance, G3 defense model Each: contract + stubs for independent build; unfitted constants marked C1. https://claude.ai/code/session_015hmgREHNsxYCuim33yUF2c
2.1 KiB
2.1 KiB
E3 — RAG family (declarative memory + per-room cross-store) (DESIGN-FIRST)
1. Component
Two memories with different machinery: declarative/relational room context (vector-RAG, namespaced
per thread) and the per-room Celtic-Cross store (deterministic keyed — room_id → current cross).
2. Status / certainty
DESIGN-FIRST · cross-store + room-RAG split C4 (mechanism decided); backing C1.
3. Language & location
TBD · new location e.g. src/rag/. Sits behind Ada (D1). This is Ada-RAG = what-you-know
(declarative), distinct from mini-rag D3 (procedural).
4. Does / does-not
- Does: store/retrieve per-thread relational context (vector-RAG); store/restore each room's live Celtic Cross by exact key (not vector search).
- Does-not: hold procedural tool schemas (D3) or the invariant core (E1).
5. Interface contract (proposed)
- Cross-store:
get_cross(room_id) -> spread/put_cross(room_id, spread)— deterministic keyed, never similarity search (similarity could return the nearest room's spread → wrong lens). - Room-RAG:
retrieve(thread_ns, query) -> context[]— namespaced per thread so room A can't bleed into B. - Both behind Ada (D1); writes carry provenance tags.
6. Dependencies & stubs
B3 cross (what's stored) — stub: canned spread. D1 provenance — stub: allow-all. B2 reshuffle reads/writes the cross.
7. Invariants / laws
- L1 (C4): live cross per room → deterministic keyed store, never vector-RAG.
- L2 (C4): room relational context → vector-RAG, namespaced per thread (no cross-room bleed).
- L3 (C4): all writes carry provenance (D1).
8. Build steps
- Choose backings (keyed KV for cross-store; vector store for room-RAG). 2. Implement both contracts.
- Wire B2/B3 (cross lifecycle) + the cycle's step-2 enrich (C3).
9. Tests
Cross-store exact-key round-trip (and a test that it does NOT do nearest-match); room-RAG namespace isolation.
10. Open items
- Backings (C1). Vector store choice (copyleft-first). Provenance tag format (shared with D1/E1/E2).