FICTIONAL FIRST-BUILD EXAMPLE — PRIVATE ARTICLE CANDIDATE

Compare a fictional R1/R2 baseline chain, the frozen prior completed record, individual adoption references and one local exception. initial_revision explicitly names R1 as the single initial root; every other revision must reach it. Each baseline change has an explicit affected_racks population, checked for every consuming rack along the ancestor chain. An empty list is not global permission. A local exception has its own exact rack and revision applicability. These are unauthenticated declarations, not work approvals. The original rack-inventory files remain unchanged. Use their README for the distinct asset/position comparison.

All IDs, quantities and references are invented. Python 3.12+ standard library only. No installation, network, device access, deletion or input mutation is performed. Extract to a local directory you control.

Run from the extracted package folder:
  python -I -B check_first_build.py extension-samples/first-build.json
  python -I -B test_check_first_build.py

The checker prints JSON to stdout and writes no files. Exit 0 means only that no discrepancy was found under the declared documentary rules. Exit 1 means it returned documentary discrepancies. Exit 2 means invalid/unreadable input. The supplied sample deliberately returns 1; compare the parsed JSON with extension-samples/expected-report.json. Never treat a missing or invalid report as a favorable finding.

Input is UTF-8 JSON (optional BOM), at most 1 MiB, with explicit null for an unknown optional field. Empty or padded strings and C0 controls in checked fields are rejected. IDs are exact and case-sensitive. Duplicate JSON fields and duplicate register IDs are rejected. Additional fields are not a substitute for the required schema. The program does not establish a complete population or authenticate any declaration.

The sample defines the field structure. Edit a retained copy of it; preserve the original requirement and earlier returns. Do not put customer identities, topology, credentials or permissioned records in a public sample. No performance, credentials, engineering adequacy, technical result, acceptance, work authorization or purchasing authority is established.

For first-build, see the owning article additions and SOURCE-BOUNDARIES.txt. Existing ancestor members, if present, retain their original bytes and historical claims. Their old checksum file covers its original population; EXTENSION-SHA256SUMS.txt covers only new files. These are separate scopes, not one self-hashing manifest or a new review of unchanged legacy code.
