FICTIONAL FIBER EXAMPLE — PRIVATE ARTICLE CANDIDATE

Compare four fictional fiber-report metadata records. A copied issuer PASS does not repair a stale issue, absent boundary or missing criterion. The original ATP index files remain unchanged; metadata match is still pending qualified review.

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_fiber_manifest.py extension-samples/fiber-manifest.json
  python -I -B test_check_fiber_manifest.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 fiber, 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.
