5 Commits

Author SHA1 Message Date
50d8deab55 docs: reframe consistency engine as from-scratch on Cognee; add CONTEXT.md glossary
Research into Cognee's actual API (docs.cognee.ai) confirmed the
docs made a load-bearing false claim: that the Lore Engine
'inherits and generalizes' a Contradiction node, get_contradictions
tool, 8 inherited MCP tools, and neo4j-init.cypher from the substrate.

Cognee ships NONE of that. Cognee provides DataPoint + custom graph
models + remember/recall + a Cypher/APOC graph-rule pattern. So:
  - Slice 2 (consistency) is a from-scratch BUILD, not a generalization
  - Categories A/B/D (Contradiction/Anachronism/Orphan) are ours
  - Category C (declarative OntologyRule) rides Cognee's Cypher pattern
  - '8 inherited tools' -> '8 base tools' (one wraps cognee.recall)
  - '7 inherited labels' -> '7 base types' (Lore Engine originals on DataPoint)

Fixed across 04-consistency, 01-ontology, 05-mcp-tools, 00-overview,
09-roadmap, 15-related-work, 16-comparison. Historical GraphMCP
comparisons left intact.

Added CONTEXT.md (glossary) — the grill-with-docs skill mandates it
and 6 ADRs' worth of resolved terms (Lineage/Faction/Region/Plane/
LoreSource/extraction+source confidence/disputed edge/retcon/Setting/
ConsistencyRun/Cognee) had no single home. New readers no longer mine
ADR prose for the vocabulary.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-06-17 22:36:07 -04:00
c8a8dcef2e docs: operational layer — eval policy, retcon policy, multi-setting, quickstart, Cognee boundary, prompt + model registries
The 18 design docs were the engine spec. These 12 new files are
the operational layer that goes with it:

Design (docs/):
  - 18-eval-policy.md        thresholds + cadence (lifted from slice 7)
  - 19-retcon-policy.md      declare/preserve/surface retcons; codex syntax stub
  - 20-multi-setting-policy  settings.yaml; cross-setting queries
  - 21-quickstart.md         1-page 'first 5 minutes'
  - 22-cognee-boundary.md    substrate vs domain contract
  - cognee-integration.md    recipe for prompt override + LiteLLM routing

Registries (docs/prompts/, docs/models/):
  - prompts/README.md        convention; system-prompt.md mirror, extraction-prompt.md stub
  - models/README.md         convention; minimax-m3.md primary notes

ADRs (docs/adr/):
  - 0006-cognee-version-pin.md   Cognee pinned at 1.1.2; harness is the upgrade gate

Index updates:
  - 00-overview.md           full doc set with categories
  - 07-reasoning-harness.md  link to prompt mirror
  - 09-roadmap.md            link to operational docs

Co-Authored-By: Claude <noreply@anthropic.com>
2026-06-17 22:16:07 -04:00
7d2ab8699f docs(v1.2): switch substrate to Cognee + fix counts + world_id deprecation
The /docs review surfaced two categories of work: real bugs and a
substrate decision. This commit lands both.

Pure fixes:
- Fix markdown table corruption in 01-ontology.md (3 `||` lines +
  duplicate `### Magic, culture, language` header)
- Replace wrong tool/label/doc count claims with the real numbers:
  30 -> 45 MCP tools, 14 -> 36 node labels, 14 -> 18 docs
- Resolve Phase 11 collision in 09-roadmap.md (v1.1 phases renumbered
  to 4-7 in the unified plan; v1 Polish keeps its Phase 11)
- Propagate the v1.2 world_id -> Setting/Plane deprecation to the
  v1.1 docs (11, 12, 14, 17): YAML world_id -> setting_id, Postgres
  world table -> setting table, Cypher index renamed, migration
  steps 6 + 7 added in 17-planes.md

Cognee substrate switch (the strategy change):
- 00-overview.md: substrate line now Cognee, not GraphMCP-Example
- 08-architecture.md: full system diagram, services layout, hosting,
  and resource budget rewritten for Cognee as the substrate
- 11-extensibility.md: 4-layer diagram reframed (Cognee data-model
  extension; template-watcher is a Cognee data-pipeline)
- 12-storage-strategy.md: 5 stores collapse to 3 layers; saga pattern
  removed (Cognee handles cross-store transactions)
- 13-microservice-decomposition.md: full rewrite (Cognee is the
  gateway; no monolith problem; 5+ Go services collapse to one
  in-process Python extension)
- 14-examples.md: Example 6 added (full 8-step Cognee integration
  walkthrough from "stand up Cognee" to "template-driven tool call")
- 15-related-work.md: Cognee reframed as substrate, not option
- 16-comparison.md: strategic section reframed (decision made, not
  debate); the build order is now in 09-roadmap.md (Cognee-spike-first)
- 10-critique.md: S1.4, S1.5, S2.5, S2.6 status updated for Cognee
- 07-reasoning-harness.md: system prompt mentions Cognee + cognee.recall
  fallback
- 06-ingestion.md: Path 1 (prose) via cognee.add/cognify; Path 2
  (YAML) via Lore Engine parser; Go-worker section replaced

Build plan (09-roadmap.md): the v1+v1.1 work collapses from 43 days
on GraphMCP-Example to 33 days on Cognee. The MVP is end of Phase 3
(16 days): Cognee spike, typed ontology, time model, 45 MCP tools.
Phase 4-6 add the consistency engine, TypeTemplate polymorphic
extension, and reasoning-harness validation.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-06-17 00:27:50 -04:00
Hermes Agent
09511a78e0 docs: v1.1 — extensibility, multi-store, microservice decomposition
New docs (1623 lines):
- 11-extensibility.md: polymorphic DomainEntity + TypeTemplate model.
  Adding a new domain (thieves-guild missions, war campaigns, etc.) is
  a YAML exercise, not a Go change. ~200 lines of Cypher, stable forever.
- 12-storage-strategy.md: split into 5 stores (Neo4j, Postgres, pgvector,
  Redis, S3/MinIO). Each store holds what it's good at. Cross-store queries
  compose at the handler layer. Sagas handle multi-store write consistency.
- 13-microservice-decomposition.md: split mcp-server's 1144-line main.go
  into a small gateway + pluggable handlers. Generic tool-handler protocol
  (GET /tools, POST /invoke). Macro/micro iteration at three speeds.
- 14-examples.md: three end-to-end worked examples showing the v1.1
  architecture in action. Thieves-guild mission (DomainEntity + Postgres),
  war-campaign tracker (DomainEntity + Postgres event log), black-market
  economy (NPC-tier-gated data + Postgres trade log).

Updates to v1 docs:
- 01-ontology: adds Plane, NPC, PC, Human labels (per Kay's Q2, Q3).
  Adds DomainEntity, Relation, TypeTemplate labels for v1.1.
- 02-time-model: year-level precision is the default (Kay's Q1).
- 09-roadmap: v1.1 phases (11-14), 20-day scope, recommended build order.
- 10-critique: open questions all resolved; 4 new S1/S2 risks recorded
  (closed-world ontology, single-binary iteration, polymorphic overhead,
  cross-store consistency). Polymorphic extension added to 'good at' list.

Design now v1.1: 14 docs, 4293 lines, ~280KB.
2026-06-16 05:25:21 +00:00
Hermes Agent
7c4ed58a5b docs: initial Lore Engine design (11 docs, ~140KB)
- 00-overview: goals, what we inherit from GraphMCP-Example, naming
- 01-ontology: 14 node labels, 40+ edge types, time-bound properties
- 02-time-model: era hierarchy, {era}.{year} canonical format, time_in_window UDF
- 03-macro-micro: 3 association patterns, lookup+active context, expand_context
- 04-consistency: Contradiction/Anachronism/Orphan/OntologyViolation, 4 rule categories
- 05-mcp-tools: 30 tools (8 inherited + 22 new), 5 composition patterns, 10 starter rules
- 06-ingestion: 3 paths (prose, structured YAML, dialogue), YAML schemas for 6 source types
- 07-reasoning-harness: 5 question types, system prompt, failure modes, worked example
- 08-architecture: system diagram, services layout, UDFs, schema bootstrap
- 09-roadmap: 11 phases, MVP = 19 days end of phase 4
- 10-critique: pressure-test, S1-S4 severity, open questions
2026-06-16 04:59:12 +00:00