[scbrown]

Publish 45 stage-two namespace destinations from merged Camayoc #164 (3e553637271a61ee01bd7e6428dfc63cb595cd01), separately from site #9. Preserve all 1,254 stage-one destinations: the result has 1,299 identities. The additions are 36 properties, one class and eight named SHACL shapes. closedAt and assignedTo remain legacy.

The compiler checks the pinned stage-two ledger, its base-mapping digest, unique destinations, complete dispositions and source coverage. Shapes receive identity aliases without being coerced into equivalent classes or properties. Property and class bridges follow their declared roles. Runtime packs, shape loading, inference, stored data and consumer pins remain unchanged. There are no new w3id redirect rules.

Stage one is verified serving: all 66 direct and w3id responses match exact merged f6d43b28 bytes and content types; 11 RDF format pairs are isomorphic; all 45 stage-two destinations are absent. Root, unknown-path and raw-source exclusion controls passed. Pins and releases must wait for a separate live proof that these 45 new terms serve after this PR's Pages deployment. The copied upstream published:false marker is source provenance, not a serving claim.

Validation: 14 publication tests passed, with 157 HOME paths and five UID resources clean. Public-tree and whitespace checks passed. Exactly nine format documents change, across core, delivery and code-entities; the other 24 format documents are byte-identical to stage one. Tests cover all aliases and role bridges, the two retained lifecycle IDs, shape identity semantics, and missing or unpinned ledger refusals. Hosted CI and one independent review remain required.

A normal merge of published main f6d43b28 into this feature preserves the entire tested 98fed91 tree. The incoming main tree exactly equals the feature's stage-one parent 738330c; that proof resolved 16 squash-history conflicts. No rebase, force push or newer main content was discarded.

Actual local demo:

Ran 14 tests in 30.312s
OK
RESULT: clean — 157 watched path(s) and 5 UID-keyed resource(s), none touched.
PASS only9 documents across3 target namespaces change;24 documents unchanged

A readable transcript is supplied; no local browser recording is claimed. Reproduce with uv run --no-project --with rdflib==7.1.4 python scripts/test-ids.py; hosted Playground runs browser and resolver controls. After Pages, verify 66 URL/type/SHA matches against the actual merged source, 11 RDF pairs, all 45 new IRIs present, and negative controls. Rollback is a normal revert of this separate publication to the actual stage-one base, preserving established identifiers. No tag, release or pin changes are included.

Work item: aegis-m5s.1; dispositions: aegis-m5s.1.1.

Overlap preflight: 4f53cda18c2baa0c0354bb5f9a3ecbe5ed12ab4d8e11ba873c2f11161202b945

[scbrown]

Ian — source APPROVE, ONE requested non-author post-green review of exact 4b2a8ffe3329b74a291e70c368ad2abd9258136d, base f6d43b28fcac4cb73d5c5d50a02dc927e7545a91 (aegis-m5s.1 / aegis-m5s.1.1; review aegis-30wf).

Independently verified all 21 pinned Camayoc input blobs against merged #164 3e553637; the 45 exact new destinations are 36 properties, one class, eight shapes. Their aliases and role bridges match the merged ledger; shapes receive sameAs only. The complete original 1,254 ownership records are unchanged. Exactly nine format documents across core, delivery and code-entities change; the other 24 documents are byte-identical, as are the legacy resolver, Jekyll exclusions and identifiers index. The merge tree exactly equals the original tested candidate tree.

Validation: 14 pinned-RDFLib publication tests, independent ledger/blob/scope proof and Node resolver controls passed; all HOME guards clean. Fresh exact-head hosted run 40047679620 completed success including actual Chromium/Playwright steps; no local browser run claimed. Current T1 classification 401099b2; requested native peer receipt 1058e15a accepted and reviewer/head/base read back.

Tim owns normal landing and Pages watch; Gennaro retains actual served bytes, content types, RDF equivalence, all 45 terms present and negative-route acceptance. No served-byte claim, runtime shape/alias load, inference change, pin or release is accepted by this source verdict. The copied upstream published:false is provenance; actual publication still needs serving proof. Rollback is the normal Pages source revert to this stage-one base, preserving established identifiers.