persona-garden-patch

Domain Form

Core question: “What shared language community does this cluster of forms belong to?”

A navigational and structural index for a shared language community — a bounded context where specific terms carry compressed meaning among practitioners. Distinguished from a reference (which briefs on a domain) by being an active map: it tracks which principles, patterns, cases, and citations exist within the domain, what’s seed versus evergreen, and where the gaps are.

A domain in this garden is NOT a disciplinary classification or library science “knowledge domain.” It is a shared language context — the place where “form,” “predicate,” and “seed stage” (Deep Context Architecture), or “principal authority” and “LESS Identity” (Self-Sovereign Identity) mean specific things without explanation. See [[Domains as Shared Language Communities]]↑ for the architectural decision and rationale.

Domains cut across form types. A domain page is a gardener’s workbench: “I want to work on digital identity today” starts at the domain page. It is also a vocabulary index — the entry point for newcomers learning the shared language of that community (per L47).

Structural Contract

A domain form requires:

Domain pages serve as vocabulary indexes for newcomers — entry points explaining the shared language of a knowledge area (per L47).

Naming heuristic: knowledge area proper name, concise. One to three words that name the field. “Deep Context Architecture” not “Deep Context Architecture Domain.”

Typical Predicates

Exemplars

Category

Structural form — captures how things relate and what we understand.

Sources

Definition from [[Deep Context as an Architecture for Captured Reasoning]], lines 71-76.

Relations