Repository navigation
docs(wo29,decision-0029): record BDFL P4 resolution (2026-09-28) - #60
Merged
Merged
Conversation
The accepted record was genuinely ambiguous about whether P4 (named with the Windows is_ordinary_fixed_target citation) additionally required a fixed-volume backing class on the trust path. The BDFL resolution: P4 requires file-object ordinariness (decision 0029 section 4), not a fixed-volume backing class; is_ordinary_fixed_target is backing observation, not a sufficient file-object check and not an additional non-waivable fixed-volume admission requirement. Matching trust may cover absent/unproven locality and the already specified storage-substitution assumption. It never waives capability consent, exact-path matching, the existing lexical/component/reparse checks, ordinary-file enforcement, file-identity binding, contradictory-evidence rejection, the 1 MiB read bound, or strict UTF-8 validation. No CLI path syntax widens. Historical wording is preserved; the new sections supersede the reading only: - docs/decisions/0029: new section 15 (2026-09-28) with the dated resolution, the actual Windows ordinary-file enforcement owners (src/file_read.rs open_checked_windows_file; src/run.rs Step 4), and four report corrections: direct UNC syntax is rejected at path validation while mapped drives classify Remote (distinct behaviors); SD/MMC hardware coverage is unavailable, not impossible; unexecuted cross-target checks receive no credit. - workorders/active/WORKORDER_29.md: superseding clarification in the trust-attestation section pointing at decision 0029 section 15. Docs-only; no runtime changes; PR #59 untouched. Checks: git diff --check clean; tools/check_text_hygiene.ps1 (654 files pass); tools/check_public_readiness.ps1 (654 files pass); tools/test_workorder_status_boundary.ps1 (153 cases pass twice deterministically).
…n P4 resolution Bounded correction to the 2026-09-28 P4 resolution; the BDFL ruling, historical text, non-waivable safeguards, and CLI syntax are unchanged. 1. Ordinary-file enforcement timing: 'all before identity capture and before any payload byte' overstated the ordering — walked identity is captured earlier in the component walk and is distinct from the opened handle's identity (bound by run.rs before the read). The accurate blanket claim is 'all before payload consumption'. Production ordering is unchanged. 2. is_ordinary_fixed_target: 'its output feeds the classifier's observed facts' was inaccurate — the predicate is used by preliminary backing classification (the Fixed gate in classify_preliminary); its result is not serialized in observed_facts. It still does not substitute for the opened-handle ordinary-file enforcement. 3. Mapped-drive wording qualified: a valid drive-letter-rooted path may pass lexical validation; classification then depends on observed mapping and drive type. Remote observations and substituted mappings remain distinct (both fail closed without the grant); direct-UNC rejection is preserved; the grant covers unproven locality without guaranteeing successful admission. Docs-only; no runtime changes; no policy reopening. Checks: git diff --check clean; tools/check_text_hygiene.ps1 (654 files pass); tools/check_public_readiness.ps1 (654 files pass).
undergroundrap
marked this pull request as ready for review
September 28, 2026 22:37
undergroundrap
added a commit
that referenced
this pull request
Sep 28, 2026
Integration-only refresh: merge accepted main ab01a8e (PR #60's documented P4 resolution, Codex-accepted) into wip/wo29-slice-a. Exactly two files changed, matching main blobs: - docs/decisions/0029-what-storage-counts-as-trusted-local-for-file-reads.md blob 9b72442 - workorders/active/WORKORDER_29.md blob c46b470 All thirteen Slice A implementation files are untouched: their blobs match 5d508f0 exactly, preserving the reviewed source and all prior validation evidence. No production change, no new semantics, no rebase.
undergroundrap
added a commit
that referenced
this pull request
Sep 29, 2026
Implement WO29 Slice A with explicit per-path --trust-locality attestation, Linux and Windows locality observations, pre-read file and backing-identity binding, and human/JSON evidence surfaces. No classifier earns automatic proof. Trust does not waive capability consent, path safeguards, ordinary-file checks, file-identity binding, contradictory-evidence rejection, bounded reads, or UTF-8 validation. Preserve the accepted P4 clarification from PR #60. Slice B remains separate. Reviewed head: 708c7ae Reviewed and PR-CI-tested tree: 4af31f1 PR validation: 36497568566 attempt 1, Full successful on Windows and Ubuntu; Ubuntu exhaustive canonical-seal evidence covered 14,226 pairs. Windows native compiler tests passed, including exact_file_read_writes_checked_utf8_and_joins_forensic_events. Required aggregation and transport cleanup passed. This merge does not claim post-merge push validation, automatic locality proof, native macOS coverage, or a CI speedup.
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.
Small draft documentation PR recording the narrow BDFL resolution of the P4 ambiguity (2026-09-28).
P4 requires file-object ordinariness, not a fixed-volume backing class. The Windows is_ordinary_fixed_target predicate is backing observation, not a sufficient file-object check or an additional non-waivable fixed-volume admission requirement.
Changes (docs only, 2 files, +95 lines):
Matching trust may cover absent/unproven locality and the specified storage-substitution assumption; it never waives capability consent, exact-path matching, lexical/component/reparse checks, ordinary-file enforcement, file-identity binding, contradictory-evidence rejection, the 1 MiB bound, or UTF-8 validation. No CLI path syntax widens.
No runtime edits, no changes to PR #59. Checks: git diff --check clean; check_text_hygiene.ps1 (654 files); check_public_readiness.ps1 (654 files); test_workorder_status_boundary.ps1 (153 cases, twice deterministically).