5.8 KiB
Included source supplement — 2026-10-15
The user subsequently authorized inclusion of project-authored implementation source. Read source supplement and its exact file/exclusion manifest. This supersedes earlier blanket statements that no implementation is bundled. Some private inputs, captured fixtures and third-party dependencies remain excluded; no clean-machine full build is claimed. Work in a separate development checkout, not this integrity-checked folder.
Coverage, exclusions and what a recipient still needs
Inventory scope
The packaging inventory examined six named source trees: the live private pico workspace, separate publication snapshot, SDK-PC prototype, October8 research archive, quick-bohr extraction directory and Antigravity brain artifact tree. It found73717file entries and768Markdown versions with429unique full-file hashes. Repeated backups and appended diaries remain distinct aliases; these counts are not768independent experiments.
Git internals, dependency/virtual environments, Unity generated trees, linked directories and generated conversation transcripts were excluded from this inventory. No claim is made to have captured every private chat message, every file on a headset or an unrecorded experiment. Older archive inventories/manifests remain provenance sources, not proof that every original hardware asset was collected.
Narrative preservation
The build deduplicates original prose paragraphs without dropping their source aliases, line locations or original file hashes. English prose is retained with privacy redaction. Non-English prose is translated to English through the explicitly approved, anonymized Gemini workflow: all numeric values, hashes, addresses, paths and identifiers were masked before external translation, exact placeholder counts/block ids checked, and values restored locally before final privacy/content filtering.
verification/COVERAGE.json reports the actual translated/required block counts and the number of unmapped source paragraphs. A finished package requires translation_complete=true and zero untranslated/unmapped paragraph occurrences. This provides mechanical traceability of retained narrative, not a proof that a model translation cannot make a semantic mistake. Numeric placeholders preserve exact technical values; reviewed canonical chapters correct known contradictions.
All code/data fences, native listing/hexdump-like lines, raw JSON/log blocks, credential-like material and raw calibration/vector-like material are deliberately withheld. catalog/OMITTED_SOURCE_SEGMENTS.json identifies original source/line ranges and reasons without including their contents. catalog/OMITTED_CONTENT.json accounts for additional sensitive/code-like narrative blocks. Obtain originals privately if an exact underlying analysis must be audited. The source catalog must never be described as a byte-for-byte public copy of all private records.
Asset preservation by reference
catalog/ASSET_REGISTER.json accounts for every inventoried file through a relative source alias, size, timestamp, classification and hash where computed. Larger/unhashed files are labelled explicitly, not assigned an invented hash. catalog/SOURCE_CODE_INDEX.json supplies computed hashes for1064selected source/build files needed for continuation; it does not license or include those files.
Original firmware, SDKs, shared objects, native models, decompiled/disassembled outputs, private calibration, recordings, raw logs and opaque archives are NOT bundled. For each category use ACQUISITION.md and the source/asset aliases. Recipients must obtain their own authorized copies and exact calibration/clock data. If the owner's private source/measurements cannot be transferred, the recipient must reproduce the documented experiment on new inputs and label it a new reproduction.
Sanitized paths may replace a device serial with an alias. original_relative_path_sha256 disambiguates the original path without publishing its identifier; it is a path hash, NOT an image/content hash. Use the content SHA for binary/version validation. Exact current local instruction files may later carry a short handoff pointer; verification/SOURCE_POINTER_UPDATES.json maps their original analyzed hashes to byte-identical private backups and records the documentation-only update. These new aliases do not add previously missing research or modify implementation/runtime state.
Firmware exception: differences only
The24unique firmware diff records use one exact FW189 stock application. They include only90changed stock-position bytes for the protected diagnostic10 case and its2336new bytes, plus the analogous changed/appended regions for other catalogued candidates. No unchanged stock region or complete image is embedded. Actual local forward reconstruction and reverse-to-stock matched every exact result/source hash. These tests do not prove safe recovery or authorize deployment.
Currentness
Current state was reconciled against saved393-v2 and later optical-latency/passive/profile artifacts, not merely the stale CURRENT_WORK heading or phase number. The900-pair passive test is completed; the profile3 test remains prepared only at inspection. No current device state, remote installation, physical readiness or firmware activation was refreshed during packaging.
Verification limits
The package verifier checks text-only allowlist, absence of binary/archive signatures, local links, JSON/Python parsing, English/Cyrillic scan, known private identity/address patterns and exact package hashes. The offline utility test checks24diff round trips, wrong hashes and forbidden in-package image output. These are concrete technical controls, not a legal opinion or blanket ownership/license determination. NOTICE.md deliberately does not relicense vendor or unknown source material.