Conversation
… behind vodka architecture) The empirical principle behind why vodka architecture wins as a design pattern: substrates win by refusing to own layers above them. Every opinion the substrate adopts is a layer the substrate must defend forever, and a layer that the layers above cannot replace. The principle walks the empirical lineage — TCP/IP, Unix pipes, HTTP, oddkit, AMS — and names the three structural forces that make the inversion work: layered orthogonality, composability under uncertainty, and maintenance asymmetry. Tier 2. Sibling to vodka-architecture (the discipline), kiss-simplicity-is- the-ceiling (the surface-area constraint that follows), and dry-canon-says- it-once (the duplication-avoidance pattern that follows). Two AMS-overlay principles already serve as downstream applications: ams://canon/principles/per-query-dynamic-orchestration and ams://canon/principles/envelope-altitude-consensus. Companion PR in klappy/agent-messaging-service lands the resonance batch that surfaced this upstream-promotion as a needed canon move.
Canon Quality —
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR: canon/principles/doing-less-enables-more — the empirical principle behind vodka architectureSuggested branch:
canon/inversion-principle-doing-less-enables-moreSuggested commit message:canon: add doing-less-enables-more principle (the inversion principle behind vodka architecture)Suggested PR title:canon: add doing-less-enables-more — the empirical principle behind vodka architecture---## SummaryThis PR adds one new Tier-2 principle:klappy://canon/principles/doing-less-enables-more.The principle is the empirical claim behind whycanon/principles/vodka-architecture.mdworks as a design pattern. Vodka architecture is the discipline; this principle is the structural reason the discipline pays. The two articles are complements: discipline + rationale.The empirical lineage walked in the principle: TCP/IP, Unix pipes, HTTP, oddkit itself, and AMS. Each substrate was contemporaneously criticized as too thin to be useful. Each enabled an ecosystem that opinionated alternatives could not host. The principle names the three structural forces that make the inversion work: layered orthogonality, composability under uncertainty, and maintenance asymmetry.## File| File | Status | Notes ||------|--------|-------||canon/principles/doing-less-enables-more.md| new (12.8 KB) | Tier-2 principle. Frontmatter shape matches existingcanon/principles/files. Section structure matchesvodka-architecture.md,kiss-simplicity-is-the-ceiling.md, anddry-canon-says-it-once.md: pull-quote intro, Summary, The Lineage in Detail, Why the Inversion Works, Smell Test, Failure Modes, Relationship to Vodka Architecture, See Also. |## Why This Belongs UpstreamThe principle generalizes beyond any one program. Two AMS-overlay principles already inklappy/agent-messaging-serviceare downstream applications of the same claim:-ams://canon/principles/per-query-dynamic-orchestration— applies the inversion to the agent-orchestration latency budget-ams://canon/principles/envelope-altitude-consensus— applies the inversion to the 2025–2026 agent-comms protocol clusterBoth reference the new upstream principle in theirderives_fromandcomplementsfields. The pattern follows the established overlay/upstream split:klappy://for general principles,ams://for AMS-specific applications. The pattern is the same one that producedklappy://canon/principles/vodka-architectureupstream andams://canon/principles/vodka-architecture-appliedin the AMS overlay.## Relationship to Existing Canon-canon/principles/vodka-architecture.md— this principle is the empirical complement. Vodka architecture says infrastructure should be thin, stateless, and domain-agnostic. This principle says why the discipline wins: refused opinions become composable layers above; adopted opinions become irrevocable constraints below.-canon/principles/kiss-simplicity-is-the-ceiling.md— sibling principle. KISS is the surface-area constraint that follows from this principle's structural claim.-canon/principles/dry-canon-says-it-once.md— sibling principle. DRY's duplication-avoidance is one specific application of this principle to governance.-canon/principles/prompt-over-code.md— sibling principle. Prompt-over-code is the same pattern applied to governance specifically.No existing principle is duplicated or contradicted. The principle adds a new abstraction level (empirical claim) that complements the existing pattern level (vodka architecture) and rule level (KISS, DRY, prompt-over-code).## Companion WorkThis PR is a companion to a separate PR inklappy/agent-messaging-servicethat lands the resonance-batch and security-as-subscriber-pattern work that surfaced this upstream-promotion as a needed canon move. The two PRs are independent; either can land first. Thederives_fromandcomplementsreferences resolve once both are merged.## Validation- Voice-cliché audited againstklappy://canon/constraints/ai-voice-cliches. Zero formulaic transitions, summary clichés, sycophantic openers, or puffing-importance hits.- Em-dash density within bounds (one bullet-list paragraph in the Smell Test section; each em-dash separates a bolded label from its explanation as distinct semantic work, matching the pattern invodka-architecture.md).- Frontmatter shape verified againstvodka-architecture.md,kiss-simplicity-is-the-ceiling.md,dry-canon-says-it-once.md.- No README index update needed (per the existingcanon/principles/convention of no README index).Note
Low Risk
Documentation-only change adding a new canon principle; no runtime or behavioral impact. Risk is limited to potential conceptual/terminology inconsistencies with existing canon references.
Overview
Adds a new Tier-2 canon principle document,
canon/principles/doing-less-enables-more.md, articulating the inversion principle that substrates win by refusing higher-layer opinions.The new article ties the claim explicitly to
canon/principles/vodka-architecture.md, provides historical/internal examples (TCP/IP, Unix pipes, HTTP, oddkit, AMS), and includes guidance sections (smell tests, failure modes, and related links) for evaluating substrate proposals.Reviewed by Cursor Bugbot for commit d5fc1f2. Bugbot is set up for automated code reviews on this repo. Configure here.