Candidate construction guide · native Resolve not tested
Historical builder snapshot: 2026-09-15. Earlier README and handoff statements about being unrendered or unpublished describe that authoring stage. The current selected report verifies both content exports at 2026-09-15T01:53:06.347148+00:00; those earlier statements do not describe their current availability. Native Resolve execution and source-quality approval remain unverified.
A working surface, beyond the conversation
Public packet instructions
This is the Batch10 r02 packaging derivative for detached-working-preview.
It retains r01's distribution layout and fixes the new public checker's ZIP
snapshot binding: one bounded byte buffer supplies both member checks and the
reported ZIP hash, even if the file path is subsequently replaced.
Recipes, Content JSON, SVGs, source
metadata, timing, runtime and original helper bytes are unchanged. Python 3.11+
and Node.js 22.18+ are required for the portable checks; no install is needed.
Read ORIGINAL-README.md for the original study, source limitations, field
constraints and render commands, and RESOLVE-HANDOFF.md for native construction.
Those historical documents are not receipts for current renders or publication.
Extract the outer detached-working-preview.zip into a new directory. Keep that outer ZIP
beside the extracted directory. From the extracted kit directory:
python3 -B verify_public_kit.py --zip ../detached-working-preview.zip
python3 -B reconstruct.py --core core-publication-v08.zip --dest clean
python3 -B test_kit.py --project clean/project --core core-publication-v08.zip -v
python3 -B handoff.py verify --guide guide.json --project clean/project
python3 -B handoff.py frames --guide guide.json --project clean/project > controls-check.csv
cmp controls.csv controls-check.csv
python3 -B resolve_controls.py --recipe clean/project/recipes/detached-working-preview.json > fusion-check.csv
cmp fusion-controls.csv fusion-check.csv
The self-contained equivalent reconstruction is
python3 -B test_kit.py --core core-publication-v08.zip --reconstruct another-clean.
Both commands require a new destination. The included core is pinned to
307fb6b927e35e6d73779652873d994f5c3e36cb7deba65f22fa64748057a0de.
active-assets.zip is the byte-identical original asset-overlay.zip. Core plus
overlay create project/; this kit has no core/overlay collisions. Do not accept
recipe replacement or overwrite a previous project for this derivative, even
if the generic generated START-HERE instructions permit replacement elsewhere.
Content files are now defaults.json, adaptation.json and custom.json at the
kit root, not inputs/. These are exact original bytes. Both original helper
fallbacks support this layout. For later authorized custom rendering, copy the
chosen Content into the reconstructed project/inputs/ as the original guide
requires. Preserve all type, track and unfinished-state constraints. Use the
unchanged original README render commands from clean/project, only when
rendering is authorized. No renderer, dependencies or source media are added.
Inventory and provenance contract
PUBLIC-PROVENANCE.json maps all 27 original download members and three external
sidecars to their delivered names and exact SHA-256 values. All original archive
members are retained, including both standalone helpers. The original archive
container itself is not nested in this packet. Its size and hash are historical
references, verified during adapter preparation, not a claim to have rehashed
that unavailable container during public-kit checking.
ORIGINAL-kit-files.json, ORIGINAL-kit-files.sha256,
ORIGINAL-input-output-manifest.json, ORIGINAL-input-output-manifest.sha256
and ORIGINAL-kit-checks.json retain their exact original bytes. Their internal
names and claims describe the original kit only. Do not run their checksums
directly against the flattened distribution. The public checker verifies their
mapped delivered bytes and explicitly reports the original archive reference
as not rehashed. ORIGINAL-README.md, ORIGINAL-START-HERE.md and
ORIGINAL-controls.csv likewise preserve the original documents, not aliases
for newly generated publication documents.
PUBLIC-INVENTORY.json freezes every static member of the intended final outer
packet. FREEZE.sha256 checks only that inventory. Both exclude themselves from
the inventory to avoid self-hashing; FREEZE is not an old checksum renamed.
The public checker enforces an exact flat member set and static sizes/hashes.
To bind an independently obtained expected inventory digest, append
--inventory-sha256 EXPECTED_SHA256; a self-contained checksum is not proof of
origin. The parent must independently bind the final outer ZIP and all its
members in the publication manifest.
Exactly five generated-wrapper files are required but excluded from the frozen
static inventory: START-HERE.md, controls.csv, bindings.json,
render-verification.json and CRITIC.md. The checker records their current
hashes as observations, never certificates of their claims. It additionally
requires controls.csv to equal ORIGINAL-controls.csv as raw bytes. Both CSVs
retain CRLF record endings and embedded LF field data. No missing or additional
file is silently ignored. Checking the ZIP is read-only, so local reconstruction
and exported check CSVs do not become extra distribution members.
The adapter tests private public-style fixtures. This input freeze does not claim successful construction of the eventual generated public ZIP. The parent owns common filename admission, final-wrapper content, render/export/browser checks, independent review and final ZIP execution using its included core. No source-quality, native Resolve, moving-review or all-hands synchronization approval is conferred by packaging checks.