DIPs release: audit amendments without the parked execution model - #8
Merged
Merged
Conversation
The owner parked the instance-bound execution model (datacore-one/datacore#192) and its DIP proposal must not reach main. This removes the whole "Approved Allocation and Execution Receipts" block, 162 lines: the protocol-2 allocation lifecycle and change record, allocation space identity, the protocol-3 "Designated execution installation" proposal, and "Mandatory admission before preparation". Kept, and promoted from a subsection to its own section: "Canonical alias compatibility". It sat inside the removed block but is about DIP-0015 space discovery, not allocation -- it corrects an earlier blanket alias refusal that stopped automation on a redundant link to an already-discovered canonical space. Losing it would reinstate that break, so it is extracted rather than dropped with its parent. No dangling references remain: protocol 3, instance-bound, execution installation, admission-before-preparation and approved-allocation all return nothing in this file. scripts/validate_dips.py: OK — 45 DIPs valid, numbers unique, hygiene clean. scripts/test_validate_dips.py: 3 passed, 37 subtests. Refs: datacore-one/datacore#192 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SCyFBu8UUeUB7WVQoZHoBD
Removes the 'Proposed: execution admission for replicated delegations (2026-09-12)' section, 86 lines, and the status blockquote that existed only to say it was unratified. Both belong to the instance-bound model the owner parked (datacore-one/datacore#192), which must not reach main. The section required a controller to commit consumption outside synced Data before invoking an adapter, and referenced the allocation controller in DIP-0011 that this branch also removes. The previously ratified adapter contract is untouched; the removed blockquote was only clarifying that the Implemented status did not extend to the amendment, which is moot once the amendment is gone. No residual references to execution admission, instance-bound, designated installation or protocol 3 remain in this file. scripts/validate_dips.py: OK — 45 DIPs valid, numbers unique, hygiene clean. Refs: datacore-one/datacore#192 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SCyFBu8UUeUB7WVQoZHoBD
DIP-0009 carries no parked section — its references to the instance-bound model are cross-references scattered through otherwise compatible prose, so this is three sentence-level edits, not an excision. Three were normative and would dangle once DIP-0011 and DIP-0041 lose the execution-admission sections: - Cadence generation: dropped the execution-admission clause. The surrounding requirement stands unchanged — generation still does not set APPROVED_BY or the AI dispatch tag, and CoS review still applies. - Occurrence deduplication: 'DIP-0011's execution admission applies' replaced with the honest statement. Local serialization is still not a cross-host lock, but no mechanism in this DIP establishes cross-host exclusion; that invariant is open (audit F2) and must be selected and verified before anything relies on it. - Production scheduling: dropped 'qualified controller admission' from the requirement list and said plainly that no mechanism here supplies an OS boundary (audit F1). Left alone deliberately: - The 'do not establish ... execution admission' disclaimer. It is a negative statement and stays true whether or not the mechanism exists. - Runtime/deployment-impact rows in change records, which name admission as a separate open requirement. The handoff requires change records be retained, and their wording is still accurate. scripts/validate_dips.py: OK — 45 DIPs valid, numbers unique, hygiene clean. scripts/test_validate_dips.py: 3 passed, 37 subtests. Refs: datacore-one/datacore#192 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SCyFBu8UUeUB7WVQoZHoBD
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
1 participant
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.
Extracts the compatible half of #7 so it can merge without the instance-bound execution proposal the owner parked (datacore-one/datacore#192), which must not reach main.
What came out
Approved Allocation and Execution Receiptsblock — 162 lines: protocol-2 allocation lifecycle and change record, allocation space identity, the protocol-3Designated execution installationproposal, andMandatory admission before preparationProposed: execution admission for replicated delegations— 86 lines — and the status blockquote that existed only to mark it unratified1,241 lines of parked proposal removed. No file contains
protocol 3,instance-bound execution,designated execution installationormandatory admissionany more.What was deliberately kept
Canonical alias compatibility(DIP-0011) — it sat inside the removed allocation block but is about DIP-0015 space discovery, not allocation. It corrects an earlier blanket alias refusal that stopped automation on a redundant link to an already-discovered canonical space. Dropping it with its parent would reinstate that break, so it is extracted and promoted to its own section.Command admission(DIP-0011) — despite the name, this is about command adapters and output ownership, not instance admission. Compatible, untouched.Change records, including
Runtime/deployment impactrows naming admission as a separate open requirement. The handoff requires change records be retained, and their wording is still accurate.Negative disclaimers such as "these checks do not establish ... execution admission" — true whether or not the mechanism exists.
DIP-0009's three edits
It carries no parked section; its references are scattered through compatible prose.
APPROVED_BYor theAIdispatch tag, and CoS review still applies.qualified controller admissionfrom the requirement list and says plainly that no mechanism here supplies an OS boundary (audit F1).Status integrity
No DIP is newly marked Implemented or Accepted. The only top-level status edits on this branch downgrade claims — DIP-0034 ("the historical Implemented header does not…") and DIP-0046 ("remains Draft").
Verification
scripts/validate_dips.py: OK — 45 DIPs valid, numbers unique, hygiene cleanscripts/test_validate_dips.py: 3 passed, 37 subtestsParked work
#7 and its branch keep the full proposal reachable under datacore#192. Nothing here adopts, ratifies or deploys it.