Browse all nodes

Every node in this graph. 150 nodes across 11 form types.

By form type

Each form type has its own index page listing nodes of that form with their summaries. Use this when you want to drill into a specific form.

• Contracts (12) — Form specifications — thin compliance rules with RFC 2119 keywords.
• Decisions (43) — Recorded choices with Why, Alternatives Considered, and What Would Change It.
• Convictions (9) — Normative stances the project holds about how to work.
• Aspirations (5) — Directional targets with acknowledged gaps and recognition criteria.
• Observations (9) — Descriptive claims with epistemic grounds (Empirical, Retrospective, Contested).
• Patterns (10) — Recurring craft moves that resolve specific tensions.
• Predicates (17) — Typed edges with Carries, Crescent-per-neighbor, and Typing sections.
• Glosses (25) — Interpretive definitions that frame concepts through a broader lens.
• References (11) — External sources the graph draws on, with publication metadata.
• Skills (8) — Agent-invocable workflows with numbered steps, grounded in the Decisions they enforce.
• Touch Points (1) — Guided introductions that frame a reader's lens onto a region of the graph — not summaries.

All nodes alphabetically (150)

Every node in one list, sorted by title. Each entry shows its form type so you can tell what kind of node it is. Use this when you remember a name but not the form, or when you want to scan the whole graph at once.

• A Pattern Language (Christopher Alexander et al., 1977) — Reference — Alexander, Ishikawa, and Silverstein's founding articulation of pattern form
• Acknowledge Before Revise — Pattern — The curator's first operational move in any curation pass is to name what each contribution added
• Adopt Layered Node Structure — Decision — A node is arranged in layers of differing cost to read, each layer complete at its own scale
• Adopt Minimum-Viable-Architecture Stance — Decision — Ship the minimum that lets the practice run and defer until use surfaces what to add next
• Adopt Node Atomicity — Decision — A node and an atomic concept stand in one-to-one correspondence; compound nodes still name one concept
• Adopt Predicate Atomicity — Decision — One predicate, one question, one axis of distinction; overloaded predicates refactor into single-axis families
• Adopt Self-Sovereign Graph Publication — Decision — Each Deep Context graph stands up self-sovereignly
• Adopt Skills as Graph Nodes — Decision — 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 — Decision — Author-declared wikilinks and named edges are the convention spine
• Agents Translate, Not Extract — Conviction — When agents mediate between graph and contributor, they read and translate author-declared edges rather than inferring edges from prose and imposing a schema
• Agora Project (Flancian, 2019) — Reference — A software project and running instance aggregating per-contributor git gardens into a federated wikilink namespace
• AI Agency Musing (Christopher Allen, 2026) — Reference — Christopher Allen's 2026 Musing extending the Principal Authority framework to AI agents
• Annotate Edges With Why-They-Matter — Decision — Every Relations-section edge carries an indented sub-bullet explaining why the relationship matters
• Aspiration Form Contract — Contract — A directional target the project works toward, carrying its acknowledged Gap, current Work, and Progress-Recognition markers
• assists_by — Predicate — Facilitation by agent or person
• Atomic Node — Gloss — A single markdown file resolving to a wikilink target
• built_on — Predicate — Foundational substrate the subject rests on
• Capture Reasoning, Not Just Knowledge — Conviction — The graph captures how contributors actually reason
• Classify Observations by Epistemic Status With Matched Grounds — Decision — Observations carry has_epistemic_status:: with four values, and each status requires matched grounds in the body
• composes_with — Predicate — Routinely used alongside
• Compound Node — Gloss — A folder with a designated lead where the concept has supporting material; the folder resolves to the lead, and sub-files serve that one concept
• conforms_to — Predicate — Compliance with a specification
• Consensus Creates Priesthoods — Observation — When a community converges on a shared vocabulary, the participants who helped create it acquire natural authority and newcomers face a learn-or-leave choice
• contends_with — Predicate — Open tension with adjacent concept
• Contested Observation — Gloss — An Observation whose grounds name the sides of a live dispute and why the dispute is load-bearing
• Contract Form Contract — Contract — The meta-contract: how a Contract node in this project is named, structured, declares inheritance, and conforms to itself
• contrasts_with — Predicate — Adjacent concept occupying different territory
• Contributors Across Vocabularies Can Collaborate — Aspiration — Contributors with different naming traditions co-author the same graph through translation layers, without convergence pressure collapsing any contributor's vocabulary
• Convention Overhead vs Graph Quality — Gloss — The ongoing trade-off between the cost each convention imposes on contribution and the quality that convention enables
• Convergent Motivation as Load-Bearing Signal — Pattern — Four or more independent motivations converging on one architectural solution is the signal that the solution is structural rather than contingent
• Conviction Form Contract — Contract — A held normative stance the project asks contributors to share, carrying Why-It-Is-Held and Drift Recognition sections
• Coordinate at Content, Not at Git — Pattern — When two graphs share a meta-layer, coordinate via per-node grafts and external wikilinks rather than git-level forks or merges; let neither graph claim canonical ownership of t...
• Creating Shared Language and Shared Artifacts Post (Christopher Allen, 2009) — Reference — Christopher Allen's 2009 post on groups intentionally developing shared language through collaborative artifacts
• CreativeWork Role Predicates Paper (Blockchain Commons, 2026) — Reference — Christopher Allen's Blockchain Commons paper specifying 14 role predicates for creative work contributions
• Crescent — Gloss — The non-overlap arc in a Venn-style predicate adjacency
• Decision Form Contract — Contract — A committed choice with Why, Alternatives Considered, and What Would Change It; situational rather than standing
• Deep Context Architecture — Gloss — The architecture for captured reasoning as typed markdown nodes connected by named edges
• Deep Context as an Architecture for Captured Reasoning — Decision — Capture reasoning as typed markdown forms with named-edge predicates
• Deep Context Community — Gloss — The collective of contributors to the Deep Context practice and graph
• Deep Context Shared Languages Post (Christopher Allen, 2014) — Reference — Christopher Allen's 2014 post naming "deep context" as the layered meaning that community-specific vocabularies carry
• Deep Context Welcome — Touch Point — A guided introduction to the Deep Context practice
• Disambiguate Reference Artifacts from Traditions — Decision — Reference filenames carry artifact descriptors
• Distinguish Adopted from Not-Adopted in References — Decision — A Reference body distinguishes what this project adopts from the source from what it deliberately doesn't
• Document Predicate Crescents Against Adjacent Predicates — Decision — Each Predicate node documents a Crescent subsection per adjacent predicate, stating what this predicate holds that the neighbor does not
• Egregore Framework (Egregore Labs, 2026) — Reference — A terminal-first, Claude-Code-native framework for multi-participant AI-assisted collaboration
• Embed Citation Parenthetical in Reference Filenames — Decision — Reference filenames carry (Author, Year) parentheticals so the wikilink target is self-citing
• Embed Images via Obsidian Wikilink Syntax — Decision — 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 — Decision — 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...
• Empirical Observation — Gloss — An Observation whose grounds name a specific measurement experiment or direct observation
• eOS-DeepContext Graph (eOSContinuum, 2026) — Reference — A downstream Deep Context graph carrying the eOS Continuum project's substrate-vs-glue architectural argument; first non-self instance of the practice and primary live test of t...
• extends_contract — Predicate — Strict inheritance between form contracts
• External Node — Gloss — A node that lives in another graph, referenced without being imported
• Firm Commitment — Gloss — A Decision commitment level marking the choice as decided and expensive to reverse
• Folders Serve Human Legibility, Not the Graph — Conviction — Folders exist for contributors scanning the filesystem; the graph lives in named edges, not in directory paths
• Form Contract — Gloss — A specification a node conforms to
• Founding Vocabularies Constrain Later Participants — Observation — The terms a project's architects choose early calcify into the group's vocabulary faster than the architects intend, constraining later participants who encounter the terms as g...
• frames_lens_on — Predicate — Frames a reader's lens onto a region of the graph
• Ghost Link — Gloss — A wikilink to a target that does not yet exist
• Gloss Form Contract — Contract — An interpretive definition whose filename carries the working definition, usable from the filesystem without opening the file
• Gloss the Translation Surface — Pattern — When two contributors' vocabularies meet, write the glossary entry that names what each term preserves
• Graft — Gloss — A node copied from a donor graph into a recipient graph
• grafted_from — Predicate — Per-node content provenance from a donor graph
• Graph Audit — Skill — Sweeps the graph for drift across categories (vocabulary, ghost links, orphans, un-annotated edges, forbidden predicates, non-ASCII filenames); aggregates by pattern, not by file
• Graph Inception — Skill — Performs the local Open Integrity inception ceremony that stands up a new Deep Context graph with its own SSH-signed root commit and DID
• Graph Load Audit — Skill — Surveys the graph for node integration depth
• Graph Orient — Skill — Orients an agent to this graph at first entry by reading AGENTS.md, the landing page, then Contracts, Convictions, and Predicates in a prescribed order
• grounded_in — Predicate — Normative or structural foundation
• Growth Stage — Gloss — The lifecycle stage of a node whose shape is being actively tested and elaborated through use
• has_component — Predicate — Mereological relation where the subject contains the object as a component
• Human Authority Over Augmentation Systems — Conviction — The wiki augments human capability
• in_practice_domain — Predicate — Membership in a Practice Domain
• informed_by — Predicate — Weaker influence than grounded_in
• informs_downstream — Predicate — Providing substrate or evidence to a downstream node
• Keep URLs as Scalar Metadata, Not Predicates — Decision — URLs appear as body URL: lines or Sources section entries; they are never encoded as named-edge predicate values
• Knowledge Outlives Its Tools — Conviction — Knowledge should outlast the tools used to capture it
• Let the Exercise Audit the Contract — Pattern — When a new Contract holds through speculative drafting but has not been run against real cases, exercise the first conforming skill or node against real data and let the exercis...
• Link Rendered Pages to Markdown Source on GitHub — Decision — Every rendered page that has a single markdown source carries a footer link to that source on GitHub
• LLM Assistance Widens the Participation Gap — Observation — LLM-assisted contributions from experienced members are accepted at rates comparable to their non-LLM work; LLM-assisted contributions from newcomers are rejected at higher rates
• Markdown Node — Gloss — A markdown file read as a graph node
• Markdown Node Contract — Contract — The base file-form every node inherits: encoding, filename rules, YAML scope, identity predicate block above the H1, Relations section, and named-edge syntax
• Markup Simplification Does Not Flatten Participation — Observation — Lowering the markup barrier (WYSIWYG editor, simplified syntax) does not produce durable gains in newcomer retention or productivity
• Mature Stage — Gloss — The lifecycle stage of a node whose shape has settled through repeated use
• Meaningful Wiki Contribution Requires Both Pride and Humility — Observation — Meaningful wiki contribution requires a contributor who simultaneously believes the contribution is worthwhile (pride) and accepts that others can improve it (humility)
• Minimum Viable Architecture — Gloss — The simplest architectural substrate sufficient to function and reveal what to add next
• Minimum Viable Architecture Musing (Christopher Allen, 2024) — Reference — Christopher Allen's 2024 Musing defining Minimum Viable Architecture
• Name Decisions by Action Verb or Role Declarative — Decision — Decision filenames use an action-verb lead or a Subject-as-Role declarative; named subjects embed verbatim
• Name Patterns by Alexandrian Evocation — Decision — Pattern names evoke the move or the situation with specificity and imagery; categorical or abstract labels are excluded
• Named Edge — Gloss — A predicate-annotated wikilink expressing a typed relation
• Naming Is Architectural, Not Decorative — Conviction — Names encode design decisions and activate semantic fields that shape every subsequent inference
• No Generic relates_to Predicate — Decision — The relates_to:: predicate is prohibited; contributors choose a specific predicate or add one to the local vocabulary
• Node Create — Skill — Authors a new node conforming to the form Contract it claims: filename pattern, identity predicate block, required body sections, annotated Relations edges
• Node Read — Skill — Reads a node progressively by layer (identity, H1, opening, Relations), letting an agent spend a finite context budget on the layer its task needs
• Node Validate — Skill — Verifies a single node against the Form Contract it conforms to, walking the inheritance chain and distinguishing mechanical violations from semantic ones
• Observation Form Contract — Contract — A descriptive claim with matched epistemic grounds (Empirical, Retrospective, Contested, On-Faith) and the conditions that would revise it
• On-Faith Observation — Gloss — An Observation whose grounds name an adopted source accepted provisionally without independent verification
• Open Integrity Project (Blockchain Commons, 2025) — Reference — A specification for per-repository cryptographic identity through an empty, signed root commit that produces a unique DID
• Participation Diversity Is Legible and Valued — Aspiration — The practice's measurement surfaces and norms treat different forms of participation
• Participation Takes Different Forms Not Different Levels — Observation — Volume alone mismeasures participation
• Pattern Form Contract — Contract — A recurring craft move named from practice, with Heart at card scale, Problem, Forces, Solution, and Consequences
• Predicate Form Contract — Contract — A typed-edge definition with Carries, Crescent-per-adjacent-predicate, and Typing sections; a specialization of Gloss for predicate names
• Predicate Propose — Skill — Gates additions to the local predicate vocabulary; each new predicate arrives as a proposal with Carries, Crescent per neighbor, and Typing, not as drift discovered after the fact
• Pride and Humility Are Both Cultivable — Aspiration — The practice develops the specific conditions that help contributors simultaneously feel their contribution is worthwhile and accept that others can improve it
• Progressive Summary Before Substance — Pattern — When authoring or reviewing a node, arrange content so consumers encounter progressively denser material as they commit context, with each tier complete at its own scale
• Provisional Commitment — Gloss — A Decision commitment level marking the choice as decided but explicitly revisitable
• Publish via Actions Artifact Deploy — Decision — Build the site in a GitHub Actions runner and deploy the artifact; do not commit built output to the repository
• Reconcile the Standing Account — Pattern — When a document's accuracy depends on something external that has moved, audit the document and reconcile
• Refactor the Predicate's Axes — Pattern — When a predicate carries two or more independently-moving axes, recognize the axes and split the predicate into single-axis named predicates before corpus use ossifies the overl...
• Reference Form Contract — Contract — An external source pointer with an Adopted / Not adopted (yet) split and publication metadata; cite-by-wikilink rather than cite-by-URL
• Reference Targets Must Be Resolvable to Other Readers — Decision — A Reference node's URL must resolve to a publicly-accessible artifact every reader can fetch
• Render Bare Wikilinks with Visible Brackets — Decision — Bare wikilinks render with [[brackets]] preserved; pipe wikilinks drop them
• Require Alternatives, Consequences, and What Would Change It in Decisions — Decision — Decisions carry Alternatives Considered, Consequences, and What Would Change It sections under stated conditions
• Require Body Elaboration Beyond Filename Definition — Decision — A Gloss body elaborates beyond the filename definition; pure repetition of the filename clause is not permitted
• Require Carries Section in Predicate Nodes — Decision — 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 — Decision — 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 — Decision — 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 — Decision — Aspirations carry Current Gap, Work It Asks, and Progress Recognition sections
• Require Heart Section at Pattern Card Scale — Decision — 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 — Decision — Conviction filenames read as held stances
• Require Prose, Capability-First Why in Decisions — Decision — 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 — Decision — Observations describe concrete conditions for update, downgrade, or abandonment; no-revision Observations are misidentified
• Require Supersession Chain for Revised Decisions — Decision — 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 — Decision — Convictions carry both a what-it-asks section and a drift-recognition section
• Reserve Predicate Vocabularies to Specific Forms — Decision — Form-specific predicates stay on their forms
• responds_to — Predicate — Direct reply creating a conversation thread
• Restrict References to Tight Artifact Clusters — Decision — A Reference captures one artifact or a tight cluster; ecosystem cataloging does not belong in a Reference
• Restrict YAML to Scalar Metadata — Decision — YAML carries scalar metadata about the file; graph-participating predicates live in the identity block and Relations; new Deep Context keys are snake_case
• Retrospective Observation — Gloss — An Observation whose grounds name a record or reconstruction rather than a direct measurement
• Scion Address — Gloss — The compound DID form identifying a specific node within a specific graph
• scion_of — Predicate — Content lineage from a template graph
• Second-Cycle Contributors Are the Scarce Resource — Observation — In sustained knowledge communities, the bottleneck is not first-cycle contribution but second-cycle continuation
• Seed Stage — Gloss — The lifecycle stage of a newly authored node whose shape has not yet been tested against other nodes
• Shared Languages Get Intimidating Over Time — Observation — As a community's shared vocabulary accumulates, newcomers encounter the breadth as a barrier and describe contributing as 'catching up'
• Skill Form Contract — Contract — An agent-invocable workflow as a compound-node graph node, carrying a runtime-invocation name, an Anthropic-spec description, and numbered steps
• source_voice — Predicate — Whose thinking is captured when different from the author
• Synpraxis Spectrum — Gloss — Coined term for the full spectrum of acting together
• Terms Become Common Through Unanimity, Not Precedent — Conviction — A term becomes shared only when every participant agrees to it; one contributor's usage does not establish it as the group's term
• The Curation Pass — Pattern — The composed unit of curation work
• The Graph Survives Its Tooling — Aspiration — The graph remains readable, traversable, and authorable across editor, wiki-layer, agent, and build-system changes
• The Second Cycle of Contribution Happens — Aspiration — The project reaches a second cycle of contribution
• Touch Point Form Contract — Contract — A guided introduction that frames a reader's lens onto a region of the graph
• Translation Over Convergence — Conviction — When vocabularies meet, both edges land as distinct claims and an agent translates between them
• Treat Objection as Structural Contribution — Pattern — When a participant objects to a term, predicate, or framing, the objection names a distinction the proposer did not see or a frame the proposal imposes
• Use ASCII Dashes in Filenames — Decision — 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 — Decision — Gloss filenames follow Concept
• Use Pipe Wikilinks for Display-Target Divergence — Decision — 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 — Decision — Contract Requirements use RFC 2119 keywords
• Vocabulary Diversity Is a Feature — Conviction — Contributor vocabularies carry design decisions the graph is committed to preserving rather than flattening
• Wikilinks and Named Edges Gist (Christopher Allen, 2026) — Reference — The gist specifying wikilinks plus named edges plus indented annotations as a plain-markdown graph convention
• Wikis Without Curation Drift Toward Write-Only — Observation — Collaborative wikis without active curation practice drift toward write-only dynamics
• Working Draft — Gloss — The curation state of a node whose content is authored but not yet curated for cross-graph consistency