• conforms_to::[[Reference Form Contract]]
• serves_as::[[Foundational Framing]]
• authored_by::[[Christopher Allen]]↗
• has_lifecycle::[[Seed Stage]]
• has_curation::[[Working Draft]]
• in_domain::[[Deep Context Architecture]]

Creating Shared Language and Shared Artifacts Post (Christopher Allen, 2009)

URL: https://www.lifewithalacrity.com/article/creating-shared-language-and-shared-artifacts/

The Life with Alacrity blog post, published 2009-09-17, that frames shared language as something groups must intentionally develop rather than discover, and names collaborative artifacts (shared objects — models, diagrams, documents developed together) as a primary mechanism for that development. The post's foundational claim — that meaning is not inherent in words but is provided by the people who use them — is upstream of this project's later positions on vocabulary sovereignty and author-declared edges.

Adopted

• Meaning is provided by users, not words. The post's framing that specialized terms carry whatever meaning a group has collectively established is the substrate under this project's commitment to author-declared edges. A contributor's critiques:: and another's challenges:: both carry genuine meaning the authors agreed to, and the graph commits to preserving both rather than normalizing to a canonical term.
• Shared language is an intentional project, not a byproduct. The stance that groups must deliberately develop shared language informs this project's treatment of vocabulary as a first-class concern — why CONVENTIONS.md exists as a living document, why Predicate nodes carry Carries and Crescent sections, why vocabulary diversity is a Conviction.
• Shared artifacts as mediums for negotiating meaning. The post names collaboratively-developed objects as the place where shared language gets worked out. This project's graph itself is a shared artifact in that sense — not just a record of decisions, but the medium through which contributors negotiate what distinctions matter.

Not adopted

• Specific facilitation techniques. The post's examples (napkin-drawing, whiteboard sessions, workshop practices) describe in-person facilitation. The project's "facilitation" happens asynchronously through git and markdown files; the mechanics transfer only by analogy.
• The constraint-for-completion mechanism. The post emphasizes that artifacts must be bounded in scope to reach completion, and that reaching completion reinforces trust. The project's artifacts (nodes) have discrete forms and completion criteria (Contracts with Requirements), but the trust-reinforcement framing is not directly adopted — the project uses different cohesion mechanisms (the form contracts, the Decision log, the cascade discipline).
• The banker/cryptographer/layperson example of "trust." The post illustrates its argument with how different communities use "trust" to mean different things. The project generalizes this into a graph-level stance (cross-vocabulary translation over convergence) rather than carrying the specific example forward.

Key moves to remember

• The 2009 framing precedes the 2014 "deep context" framing and establishes the philosophical substrate the later work specializes. When later work assumes that vocabulary is collectively-negotiated and artifact-mediated, it is drawing on this post's foundation.
• The post's argument that artifacts must be bounded suggests a discipline the project implements differently (through form contracts that bound what each node does) — a lineage worth acknowledging without collapsing into identity.

Relations

• informs::[[Deep Context Shared Languages Post (Christopher Allen, 2014)]]

  • The later post by the same author that specializes this foundational framing into community-specific shared language carrying "deep context." The 2014 post is downstream; this 2009 post is the substrate it rests on.

• informs::[[Vocabulary Diversity Is a Feature]]

  • The Conviction whose "author-declared edges preserve distinct claims" commitment rests on the 2009 framing that meaning is provided by users, not words. Without that substrate, the Conviction's sovereignty argument does not land.

• informs::[[Translation Over Convergence]]

  • The specialized Conviction that encodes the translation-not-normalization operational rule. The 2009 stance that different communities legitimately use the same word differently (the banker/cryptographer/layperson example) is the upstream of the project's translation-over-convergence commitment.