P0006 (accept + execute): vodka boundary enumeration as spec convention#171
Merged
P0006 (accept + execute): vodka boundary enumeration as spec convention#171
Conversation
Acceptance:
- Flip docs/promotions/P0006 promotion_status: proposed -> accepted
- Update tags array ("proposed" -> "accepted")
- Fill Review Notes with operator decision (klappy, 2026-05-05)
Execution:
- canon/principles/vodka-architecture.md: append new section
"## Spec Convention — The Boundary Must Be Enumerated" before "## See Also"
- Section requires three enumerated sections in any vodka-compliant spec:
- ## What This Server Knows (bullet list)
- ## What This Server Does NOT Know (the vodka boundary, written down)
- ## What This Server Is NOT (non-goals to rebut for scope expansion)
- Includes Why Enumeration Matters, Failure Mode, Receipts (PTXprint v1.2 §1)
Last of the append-style amendments. Fifth of 8 stuck proposals.
Previous: P0009 (#167), P0001 (#168), P0008 (#169), P0007 (#170).
Next: P0003 — reframe-before-trimming method (NEW canon doc, larger surface).
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
2 participants
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.
What this PR does
Combined acceptance + execution of promotion P0006 — sharpens vodka-architecture from philosophy to a concrete spec-shape requirement.
Acceptance (1 file)
docs/promotions/P0006-vodka-boundary-enumeration-as-spec-convention.mdpromotion_status: proposed→accepted"proposed"→"accepted"accepted(2026-05-05)Execution (1 file, +27 lines)
canon/principles/vodka-architecture.md— new section before## See Also:## Spec Convention — The Boundary Must Be Enumerated## What This Server Knows## What This Server Does NOT Know← the vodka boundary, written down## What This Server Is NOT← non-goals to rebut for scope expansionPosition in the 8-proposal sweep
DoD
promotion_statusflippedNote
Low Risk
Docs-only change that introduces a new spec-convention requirement; risk is limited to process/workflow expectations for future vodka-compliant specs.
Overview
Accepts P0006 by flipping its promotion metadata/status to
acceptedand recording the review decision/date.Updates
canon/principles/vodka-architecture.mdwith a new spec convention that mandates three explicit sections in any vodka-compliant server spec:## What This Server Knows,## What This Server Does NOT Know(the written boundary), and## What This Server Is NOT(enumerated non-goals), plus rationale and a reference receipt.Reviewed by Cursor Bugbot for commit 04e9c63. Bugbot is set up for automated code reviews on this repo. Configure here.