Abstract

A method is disclosed for verifying a blind rebuild — a reconstruction of a running platform, or of one of its components, from documentation alone — so that neither the rebuild nor its verification can take the live platform as its target. A pure binding function turns an environment map into a bound target record or a typed refusal: "unbound" when any of four required variables (target namespace, image tag, source commit, tenant identifier) is missing or the tenant identifier or target namespace is not a valid DNS label, and "live target" when the target or data namespace belongs to a protected set formed as the union of configured live names and built-in defaults, or the public host ends with the live domain. The same function is the first call of a planner whose own code launches no process, emitting an ordered, non-executing command plan with a verification predicate per step, and of an oracle whose entry point builds its real dependencies only after binding succeeds. The oracle's five check classes are pure functions over injected dependencies: readiness probed inside the rebuilt workload; topology, including a requirement that the rebuilt edge tunnel is its own; a three-way migration-ledger count; a functional cycle; and an artifact hash set whose running-tree digest must equal the same pipeline run over an archive export of the pinned commit. A thrown check is a failure. A grader deep-diffs a blind component candidate against an oracle extracted verbatim from production code, over pinned fixtures.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.

Share

COinS