Conflict ledger (L3)

Cross-domain overlaps and unresolved ambiguities. Domain maps reference these IDs under CompetingSystems.

When status is open, the assistant should hard-stop on implementation guidance that assumes a single graph stack or full MCP surface until you pick a resolution path (see answer-protocol.md).

C001 — Graph runtime (**resolved**)

• Resolution: Runtime graph operations use Apache AGE via `src/lib/server/graph/age.ts` (Cypher through ag_catalog.cypher on graph AGE_GRAPH_NAME, default eigen_graph). Query-time retrieval uses precomputed thought_neighbor / community bundles — not live AGE reads.

C002 — MCP HTTP tool surface (**resolved**)

• Resolution: HTTP MCP exposes four thought tools via `registry.ts`: capture_thought, retrieve_thoughts, edit_thought, delete_thought. The in-app chat agent has a larger tool surface (Notes tools, etc.). list_thoughts and answer_question are not on HTTP MCP; browse via retrieve_thoughts with order=created_at; compose answers in the client or use in-app Chat.

Resolution playbook (short)

• C001: Resolved — AGE for ingest and visualization; precomputed links at query time.
• C002: Resolved — four-tool HTTP MCP contract; chat agent has extended surface.

When you resolve a row, set status to resolved in the heading and add a Resolution line under that ID (and update the relevant domain map CompetingSystems section).