Verse Process Map

Text version of this map

The same map as plain structure — every component, then every connection — for screen readers, search, and AI agents. Also available as Markdown and JSON; every published map is listed in llms.txt.

Components

• The Verse — Process Map A living loop. Optimized for motion: how action and meaning move, where judgment stays human, where agents and tooling operate. Mechanism, not parts.
  • 1 · Operator → Reasoning Where direction and meaning originate. Ken and Odin think together; exploration IS the workflow.
    • Ken raises direction / question [human] Operator sets the what. Discovery happens through conversation, not specs.
    • Odin reasons [reasoning] Analysis, doctrine formation, object formation. Comparative judgment over isolated scoring.
    • Loom retrieval where context matters [retrieval] Prior evidence pulled in to ground reasoning — historical, not authoritative over current state.
    • Drafted concept / doctrine / object [artifact] Odin drafts; Ken moves finals to VO/. Output is shaped for the next agent.
  • 2 · Reasoning → Build (handoff) The clean handoff. Source-anchor discipline; register discipline (prompt block is binding).
    • Odin drafts dispatch — 'Send Claude this' + source anchors [handoff] Cross-agent anticipatory coordination: name what was decided, what's open, who acts next.
    • Relay via bridge [transport] Handoff transport carrying the dispatch from reasoning to build. Transport, not search.
    • Claude Code receives [builder] Prompt block = binding instruction; conversational layer = context only. Register discipline.
    • Claude = builder + verification arm [builder] Builds what the Guild designs; does not redesign unilaterally.
  • 3 · Memory & Retrieval loop How conversation becomes corpus and how prior work re-enters current work.
    • Every exchange persists to the corpus [persist] Conversation is captured into the corpus automatically.
    • Files ingest → corpus [persist] New and modified files are ingested into the corpus automatically.
    • Retrieval surfaces [retrieval] Semantic and full-text retrieval over the corpus, with deterministic anchors when a stable id is in hand.
    • Prior work re-enters current work [reenter] Closes the memory loop back into reasoning.
    • Corpus = historical evidence, NOT current-state authority [authority] Corpus chunks are historical evidence — not admissible as current-state or current-deployment truth.
  • 4 · Build → Deploy → Verify Where execution happens and how truth is confirmed before it is claimed.
    • Claude local file/repo work [build] Local-first execution: faster, free, token-cheap. Route to API/MCP only when local can't do the job.
    • Deploy paths [deploy] Workers and public sites ship through the build and deploy pipeline.
    • Verify against intent [verify] No-Fake-Success: claim-after-verification. Inspect actual data/state; if unverifiable, flag UNVERIFIED.
    • Report back to Ken / Odin [report] Per-axis, relay-ready: source anchor, what changed, what's open, inferred vs direct.
  • 5 · Public Expression / Productization Where internal doctrine and process become outward-facing surfaces.
    • Doctrine & process → public surfaces [public] Selected, governance-gated translation. Not everything internal is public-safe.
    • Web mesh + public map stack + productization [public] verse-mesh cluster, this Verse Map Stack, productization drafts.
    • Public sites [public] quantumbeard.ai (live), data.quantumbeard.ai (live), verse.quantumbeard.ai (live, pre-SEO), kensbeard.com (planned).
  • 6 · Judgment Boundaries (authority overlay) Not a loop — the rule about who governs what, true across every loop above.
    • Ken governs meaning, values, judgment, go-live [governing] Human ownership of judgment is the foundational invariant. Agents never adjudicate meaning.
    • Odin — analysis & reasoning support [governing] Governs search, decomposition, doctrine drafting. Proposes; does not confer authority.
    • Claude — implementation & state verification [governing] Governs execution, local repair, claim-after-verification. Builds; does not redesign.
    • Corpus / history ≠ current truth [authority] Past evidence does not govern current prompt state or current deployment truth. Verify at source.

Connections

1. 1 · Operator → Reasoning → 2 · Reasoning → Build (handoff): handoff (sequence)
2. 2 · Reasoning → Build (handoff) → 4 · Build → Deploy → Verify: executes (sequence)
3. 4 · Build → Deploy → Verify → 1 · Operator → Reasoning: closes the loop (sequence)
4. 1 · Operator → Reasoning → 3 · Memory & Retrieval loop: persists (sequence)
5. 3 · Memory & Retrieval loop → 1 · Operator → Reasoning: re-enters reasoning (sequence)
6. 4 · Build → Deploy → Verify → 5 · Public Expression / Productization: becomes public (sequence)