Knowledge
System
A system for separating dated agent output from curated, durable knowledge — so the workspace answers what we know now, not merely what was written before.
Tier 1 — Raw output/
Dated production files stay exactly where agents already write them. They remain the audit trail: complete, unchanged, and often noisy.
source material · historical · accumulatesTier 2 — Agent knowledge/
Each knowledge-producing agent owns stable topic files and updates them in place. Durable findings get distilled here, closer to the domain owner.
curated by owner · one file per topicTier 3 — workspace/knowledge/
The consolidated system view. Cross-agent answers, syntheses, and strategic context live here — promoted only after review.
best current answer · Reghar-only writesThe Problem
Agents are productive, but their output naturally piles up. Without a knowledge layer, the system starts behaving like an archive of snapshots instead of a living memory.
Live System Stats
Derived from the current knowledge index and ownership model.
workspace/knowledge/.Agent Knowledge Map
The system stays legible because topic ownership is explicit. Durable knowledge belongs with the owning agent or gatekeeper first.
Core
23 topicsResearch patterns: cost, security, architecture, tooling, rate limits, sandboxing, self-healing.
research ownerDeveloper knowledge: routing, CRM, learnings, migration patterns, agent improvements.
technical ownerBrand voice and content brief patterns.
writer ownerDesign system knowledge and implementation patterns.
design ownerNolea
32 topics shown in briefGroup gatekeeper and consolidated Nolea view: business context, outreach, partner network, CRM, infra.
gatekeeperAnalytics and performance findings feeding up into Vessel.
analytics sub-agentChampagne, growers, pairing logic, glossary, and source knowledge.
domain sub-agentLeon
3 topics in current briefLeon gatekeeper. Consolidates deployment and business/client knowledge before any cross-group promotion.
gatekeeper*The presentation follows the requested ownership counts for the visual brief. The current INDEX.md snapshot shows fewer listed files in some directories, which suggests the map is a strategic overview rather than a strict one-to-one directory dump.
Promotion Flow
Knowledge promotion is intentionally narrow. Most agents can write raw output and their own knowledge, but system-wide consolidation passes through explicit review.
Anselme, Margot, Kevin-G, Costco Guy generate findings and pass them upward instead of promoting directly.
Vessel and Charles consolidate within their business groups. Core agents flag directly without bypassing review.
The review queue collects promotion candidates, reason, path, timestamp, and priority.
Existing topic? Merge. Contradiction? Synthesize. New topic? Promote and register in the index.
The curated system answer becomes readable by all agents, but writable only by the promoter.
Golden Rule
File Format
Every durable knowledge file uses stable topic naming and structured frontmatter so promotion, comparison, and synthesis stay predictable.
--- type: promoted | synthesis | standing topic: topic-slug owner: agent-id source: path/to/source.md sources: - path/to/source-a.md - path/to/source-b.md last-updated: YYYY-MM-DD status: current | stale | superseded --- # Topic Title
Conflict Resolution
Contradictions are not allowed to fork into competing “truth” files. The system forces synthesis.
Promotion reveals that two agent findings disagree on the same topic.
Do not create parallel contradictory entries in the consolidated workspace.
Create or update the file as type: synthesis and include both sources.
Publish the current best understanding — or leave an explicit open question if unresolved.