Drafted via ChatGPT (blocked by an interface bug from being written directly to notes) and integrated here 2026-07-19. A companion proposal to Structured Context Protocol: that proposal names session phases; this one addresses what those phases all draw on and write back to.
A shared engineering experience that humans and AI build together over time.
A task is a continuous cognitive process, not a relay race between agents. Design, investigation, implementation, review and reflection are cognitive phases. They change objective, evidence sought, context loaded, and success criteria — they do not change identity, accumulated understanding, or reasoning history.
There is one authoritative experience base. Knowledge is not partitioned by John, ChatGPT, Claude or Envoy. Everyone reasons from the same knowledge; what changes is the cognitive phase and therefore the context selected.
Rather than different agents seeing different knowledge, participants should be able to inspect the same loaded context. Reasoning should be transparent and reconstructable — the same principle already documented as Envoy's debuggability advantage over vector/RAG retrieval (see envoy).
• Reference facts• Decision records• Incident / experience records• System models• Working workspace (temporary)
• One authoritative knowledge base.• Record reasoning, invariants, trade-offs and lessons — not just procedures or conclusions.• Preserve uncertainty rather than flattening it into false confidence.• Record engineering judgement, not only outcomes.• Promote durable conclusions from temporary workspace into the permanent experience store.• Context is selected by cognitive task, not by participant identity.
Split into separate notes once there is enough material to justify it:
• shared-experience-architecture/decision-record• shared-experience-architecture/incident-record• shared-experience-architecture/system-model
Also:
• Evolve project root notes into system-model notes rather than plain indexes.• Replace ‘agent roles’ with ‘cognitive phases’ throughout the Structured Context Protocol.• Design a shared temporary workspace distinct from the permanent experience store.• Investigate context selection by cognitive task rather than by agent identity.
• Structured Context Protocol — names the session phases (orient/gather/plan/execute/verify/commit); SEA describes the single shared knowledge base those phases draw context from and write conclusions back to.
• envoy — the working implementation this generalises from: phase-aware processing, per-state instruction notes, context bundles.
• README/workflow and README/orphaning — the existing discipline (create+link together, preserve metadata, promote durable content) that SEA's ‘promote to experience store’ principle already assumes.