Decisions

Recorded choices with Why, Alternatives Considered, and What Would Change It.

• [[Adopt Layered Node Structure]] -- A node is arranged in layers of differing cost to read, each layer complete at its own scale
• [[Adopt Minimum-Viable-Architecture Stance]] -- Ship the minimum that lets the practice run and defer until use surfaces what to add next
• [[Adopt Node Atomicity]] -- A node and an atomic concept stand in one-to-one correspondence; compound nodes still name one concept
• [[Adopt Predicate Atomicity]] -- One predicate, one question, one axis of distinction; overloaded predicates refactor into single-axis families
• [[Adopt Self-Sovereign Graph Publication]] -- Each Deep Context graph stands up self-sovereignly
• [[Adopt Skills as Graph Nodes]] -- An agent-invocable capability is a graph node like any other, authored under nodes/Skills/ and conforming to a Skill Form Contract
• [[Adopt Wikilinks and Named Edges]] -- Author-declared wikilinks and named edges are the convention spine
• [[Annotate Edges With Why-They-Matter]] -- Every Relations-section edge carries an indented sub-bullet explaining why the relationship matters
• [[Classify Observations by Epistemic Status With Matched Grounds]] -- Observations carry has_epistemic_status:: with four values, and each status requires matched grounds in the body
• [[Deep Context as an Architecture for Captured Reasoning]] -- Capture reasoning as typed markdown forms with named-edge predicates
• [[Disambiguate Reference Artifacts from Traditions]] -- Reference filenames carry artifact descriptors
• [[Distinguish Adopted from Not-Adopted in References]] -- A Reference body distinguishes what this project adopts from the source from what it deliberately doesn't
• [[Document Predicate Crescents Against Adjacent Predicates]] -- Each Predicate node documents a Crescent subsection per adjacent predicate, stating what this predicate holds that the neighbor does not
• [[Embed Citation Parenthetical in Reference Filenames]] -- Reference filenames carry (Author, Year) parentheticals so the wikilink target is self-citing
• [[Embed Images via Obsidian Wikilink Syntax]] -- Image embeds use Obsidian's ![[path]] wikilink-embed syntax; attachments live in an Attachments/ folder co-located with the referring note; the render pipeline translates to...
• [[Emit Skill Runtime Aliases at Build Time]] -- Source-of-truth lives at nodes/Skills/<Title Case>/<Title Case>.md; agent-runtime discovery layouts at .agents/skills/<lowercase-hyphenated>/ and .claude/skills/<lowercase-hyphe...
• [[Keep URLs as Scalar Metadata, Not Predicates]] -- URLs appear as body URL: lines or Sources section entries; they are never encoded as named-edge predicate values
• [[Link Rendered Pages to Markdown Source on GitHub]] -- Every rendered page that has a single markdown source carries a footer link to that source on GitHub
• [[Name Decisions by Action Verb or Role Declarative]] -- Decision filenames use an action-verb lead or a Subject-as-Role declarative; named subjects embed verbatim
• [[Name Patterns by Alexandrian Evocation]] -- Pattern names evoke the move or the situation with specificity and imagery; categorical or abstract labels are excluded
• [[No Generic relates_to Predicate]] -- The relates_to:: predicate is prohibited; contributors choose a specific predicate or add one to the local vocabulary
• [[Publish via Actions Artifact Deploy]] -- Build the site in a GitHub Actions runner and deploy the artifact; do not commit built output to the repository
• [[Reference Targets Must Be Resolvable to Other Readers]] -- A Reference node's URL must resolve to a publicly-accessible artifact every reader can fetch
• [[Render Bare Wikilinks with Visible Brackets]] -- Bare wikilinks render with [[brackets]] preserved; pipe wikilinks drop them
• [[Require Alternatives, Consequences, and What Would Change It in Decisions]] -- Decisions carry Alternatives Considered, Consequences, and What Would Change It sections under stated conditions
• [[Require Body Elaboration Beyond Filename Definition]] -- A Gloss body elaborates beyond the filename definition; pure repetition of the filename clause is not permitted
• [[Require Carries Section in Predicate Nodes]] -- Every Predicate node carries a dedicated Carries section stating the positive sense of the predicate, not derivable from Crescent content alone
• [[Require Explanatory Prose Before Contract Requirements]] -- A Contract opens with explanatory prose between the H1 and the Requirements section, orienting readers before they read the spec
• [[Require Forces Authenticity in Patterns]] -- A Pattern's Forces name at least two competing demands in genuine tension; a Force nobody disagrees with is a value, not a Force
• [[Require Gap, Work, and Progress Recognition in Aspirations]] -- Aspirations carry Current Gap, Work It Asks, and Progress Recognition sections
• [[Require Heart Section at Pattern Card Scale]] -- Patterns open with a two-or-three-sentence Heart that stands alone as the Pattern at card scale
• [[Require Held-Stance Filename Shape for Convictions]] -- Conviction filenames read as held stances
• [[Require Prose, Capability-First Why in Decisions]] -- A Decision's Why is prose, and it leads with the capability the commitment provides rather than the symptom that prompted it
• [[Require Revision Conditions on Observations]] -- Observations describe concrete conditions for update, downgrade, or abandonment; no-revision Observations are misidentified
• [[Require Supersession Chain for Revised Decisions]] -- A revised Decision gets a new filename and a supersession edge; the old filename is never renamed
• [[Require What-It-Asks and Drift Recognition in Convictions]] -- Convictions carry both a what-it-asks section and a drift-recognition section
• [[Reserve Predicate Vocabularies to Specific Forms]] -- Form-specific predicates stay on their forms
• [[Restrict References to Tight Artifact Clusters]] -- A Reference captures one artifact or a tight cluster; ecosystem cataloging does not belong in a Reference
• [[Restrict YAML to Scalar Metadata]] -- YAML carries scalar metadata about the file; graph-participating predicates live in the identity block and Relations; new Deep Context keys are snake_case
• [[Use ASCII Dashes in Filenames]] -- Filenames use ASCII hyphens only; typographic em-dashes and en-dashes are prohibited; the double-hyphen separator is two ASCII hyphens
• [[Use Double-Hyphen Separator for Gloss Definitions]] -- Gloss filenames follow Concept
• [[Use Pipe Wikilinks for Display-Target Divergence]] -- Pipe wikilinks let authors choose link phrasing that fits the prose while the graph edge still resolves to the canonical target
• [[Use RFC 2119 Keywords in Contract Requirements]] -- Contract Requirements use RFC 2119 keywords

43 nodes in this section.