Koni Field Lab Systems and principles for AI-assisted knowledge work.
systems · map

Systems

The shortest useful map of how Koni Field Lab works: what enters, what persists, what gets reviewed, and what becomes public.

The useful architecture is small: signals arrive, agents turn them into drafts, LinkCatalog keeps the record, and humans decide what becomes public. Everything else on the site should serve that understanding.

Diagram showing Discord drops, GitHub stars, and manual notes flowing through narrow agents into LinkCatalog, then through review and compile loops into Research Trails, Citta drafts, the Prototype Bench, and konidev.com.
Capture → narrow agents → LinkCatalog → review → public surfaces.

The working loop

  1. Capture. Discord drops, GitHub stars, and manual notes enter as raw signals.
  2. Draft. Narrow agents ingest, sync, watch, and draft. They propose; they do not silently turn proposals into truth.
  3. Persist. LinkCatalog is the durable private workspace. It holds saved links, pending items, trails, indexes, and provenance.
  4. Review. Human confirmation and scheduled checks decide what is accepted, compiled, repaired, or ignored.
  5. Publish. Citta and konidev.com are downstream surfaces. They publish selected records; they are not the source of truth.

Boundaries that matter

  • Agents can be wrong in draft. They should be cheap to inspect and easy to roll back.
  • Files persist longer than tools. The record should survive a publisher, agent, or interface being replaced.
  • Public pages need a reason to exist. A page should teach the architecture, document a decision, or expose a useful artifact.