persona-garden-patch

Form Type Definitions

Structural contracts defining what each form type answers and how it is organized.

Boundary Form — Where does this system’s authority end? — the structural contract for boundary forms

Captured Stage — Raw recording or notes exist — where meeting processing begins

Case Form — What happened when this was tried? — the structural contract for case forms

Chat Log — Text chat records from meetings or AI conversations — timestamped and attributed

Citation Form — What do I need to know about this source? — the structural contract for citation forms

Cleaned Stage — Transcript cleaned and readable — a reliable record but not yet synthesized

Conviction Form — What do we believe is true about the world? — the structural contract for conviction forms

Decision Form — Why did we choose this over the alternatives? — the structural contract for decision forms

Domain Form — What shared language community does this cluster of forms belong to? — the structural contract for domain forms

Evergreen Stage — Mature, well-linked, trustworthy — the highest confidence stage for retrieval

Form Type — The structural contract that defines what shape a knowledge object takes

Gloss Form — What does this specific source or concept mean? — the structural contract for gloss forms

Growing Stage — Structured and linked but still developing — the active tending stage

Inquiry Form — What should we think about X, and how would we find out? — the structural contract for inquiry forms

Medical Visit — Visit note type for health appointments with adaptive sections and multi-source synthesis

Meeting Note — Synchronous conversation records with attendees, outcomes, and optional compound artifacts

Model Form — How do these elements relate to each other? — the structural contract for model forms

Opus Form — What am I saying here, and how does it connect? – the structural contract for authored works

Pattern Form — What resolves this recurring tension? — the structural contract for pattern forms

Person Note — Contact records linking people to their meetings, projects, and vault references

Persona Form — Who is this agent and how does it behave? — the structural contract for persona forms

Principle Form — What must we always or never do? — the structural contract for principle forms

Protocol Form — How do independent parties coordinate reliably? — the structural contract for protocol forms

Pruned Stage — No longer current but preserved — the garden’s way of retiring without deleting

Published Stage — Shared beyond the vault — the terminal stage of meeting processing

Reference Form — What do I need to know about this domain to act effectively? — the structural contract for reference forms

Research Form — What have I investigated about this question, and what did I find? — the structural contract for research forms

Scenario Form — What might happen if these forces play out? — the structural contract for scenario forms

Seed Stage — Raw capture, unprocessed, low confidence — where every garden node begins

Sidecar — Metadata envelopes for binaries and non-local artifacts — the markdown proxy pattern

Skill Form — How does an agent execute this reliably? — the structural contract for skill forms

Summarized Stage — Synthesized into structured notes — complete as a reference, ready for distribution

Transcribed Stage — Raw transcript exists but unclean — searchable but not yet readable

Transcript — Cleaned speech record with speaker normalization — always derived from a meeting

Value Form — What do we care about? — the structural contract for value forms

35 nodes in this section.