Skip to content

feat(r1): publish P07 artifact reference authority - #32

Closed
ajhcs wants to merge 3 commits into
mainfrom
codex/r1-p07-publication-20260827
Closed

feat(r1): publish P07 artifact reference authority#32
ajhcs wants to merge 3 commits into
mainfrom
codex/r1-p07-publication-20260827

Conversation

@ajhcs

@ajhcs ajhcs commented Aug 27, 2026

Copy link
Copy Markdown
Owner

Publishes exact accepted P07 head bb452c6 (tree effdb57738f08b14ab6883043c2ddf70f0265a45). Scope: strict relative artifact-path policy, ArtifactRefV1 digest authority, focused adversarial tests, and accepted documentation. Review and CI authority apply only to this exact final head/tree. History is preserved; no squash or rebase. Rejected unrelated PR #28 head 9a37eba is outside this ancestry.

cole added 3 commits August 22, 2026 19:45
Answer exactly one question deterministically and fail closed: is this
string a strict portable run-relative artifact path? Accept only NFC,
well-formed, forward-slash, relative paths of 1..16 segments (128 UTF-8
bytes each, 1024 total). Reject backslashes, leading/trailing/doubled
slashes, empty and dot-only segments, colons (foreclosing drive, UNC,
alternate-data-stream, and scheme spellings under one rule), Windows
reserved device stems with the extension ignored, edge dots/spaces that
Windows tooling strips, C0/C1 controls, invisible/format/bidi/tag code
points, solidus look-alikes, non-NFC text, and lone surrogates while
keeping well-formed astral characters legal.

The fixed validation pipeline raises identical first typed errors from a
closed 17-code vocabulary, never echoes hostile bytes (U+ notation and
offset only), captures every dynamic intrinsic at import, scans strings
by code points, and returns deep-frozen detached descriptors. Pure path
policy only: no filesystem, network, or process I/O, and no claim that
P08 artifact storage exists. Focused hostile coverage pins the rejection
matrix, ordering, bounds parity, predicate agreement, and detachment.
Bind exactly ten keys: exact run/child identifiers reusing the accepted
manifest grammars, artifact kind bound to the detached P17 capability
vocabulary, raw-vs-sanitized class with class-dependent bounded-evidence
caps (sanitized 256 KiB, raw 32 MiB), declared byte length, 64-character
lowercase SHA-256, and closed media-type/content-encoding enums. The
relative path carries no class marker; consumers trust the ref, never
the name.

Hostile inputs fail closed before any effect: live/revoked Proxies with
zero traps, accessor properties whose getters never run, symbol keys,
exotic prototypes, own undefined, sparse/extended arrays, aliases and
cycles, depth and size. Parsed results are deep-frozen detached
snapshots built property-by-property, so later caller mutation cannot
drift a digest or a comparison.

Digests follow the accepted P03 framing conventions without touching its
closed registry: SHA-256 over validator-owned canonical JSON behind an
explicit domain string, big-endian version, ratified private label, and
length-prefixed parts, so key order cannot change a digest while any
value change must. Ordering is deterministic via one total tuple
comparator plus a bounded (64) duplicate-free batch orderer. Pure schema
and path policy only: no constructor from bytes, no reader, no
sanitizer, no existence check, and no claim that P08 storage exists.
Focused hostile coverage pins proxies, accessors, coercion hooks,
closure-before-vocabulary ordering, batch hostility, and mid-call
mutation inertness.
Document the closed ten-key ArtifactRefV1 schema, the strict portable
relative artifact path policy with its fixed denial pipeline, the
domain-framed canonical digest authority, deterministic ordering, and
the pure schema/path-policy boundary that claims no P08 storage.
@ajhcs

ajhcs commented Aug 27, 2026

Copy link
Copy Markdown
Owner Author

Closed as superseded publication-topology evidence. Exact head bb452c6 is accepted P07, but it does not contain accepted P06 ancestry and conflicts with current main at CHANGELOG.md. It was not merged. The branch and immutable mismatch receipt are retained; publication resumes only from accepted combined head 0fd091e, the first accepted head containing P06 ancestry.

@ajhcs ajhcs closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant