bodencrouch/independent-reconstruction

Audits run provenance, hashes, approvals, exposure, cache validity, and bounded evidence claims. Use explicitly before handoff, integration, resumption, or release reporting.

Defines observable ABI and binary interoperability contracts without transferring disassembly or original internal structure to implementers. Use explicitly for native SDK, executable, or binary compatibility reconstruction.

Compares candidate and pinned oracle behavior using approved cases, explicit normalization, and reproducible environments. Use explicitly for differential conformance validation or a compatibility audit.

Inventories npm, Python, Cargo, and Go manifest dependencies and prioritizes authorized reconstruction candidates without assuming a complete license audit. Use explicitly for dependency scanning and replacement planning.

Reconstructs parser and writer contracts for file formats, including canonicalization, malformed inputs, and round trips. Use explicitly for format interoperability or archive/document compatibility.

Reviews specifications, conformance corpora, and feedback for source leakage, unsupported claims, private data, and implementation contamination. Use explicitly before approving an implementation handoff or a case corpus.

Implements a candidate from an approved behavioral pack in a fresh context and separate workspace. Use explicitly for the implementation lane of an independent reconstruction.

Defines the scope, evidence access, versions, roles, and acceptance criteria for independent reconstruction. Use explicitly before collecting evidence or when a reconstruction brief is incomplete.

Records model training uncertainty, retrieval exposure, provider handling, and tool-mediated contamination risks. Use explicitly when planning model separation or assessing a reconstruction provenance claim.

Collects reproducible behavior from authorized APIs, binaries, CLIs, logs, and documentation with provenance and uncertainty. Use explicitly to create an observation corpus for reconstruction.

Coordinates evidence, behavioral specifications, review, isolated implementation, and conformance evidence. Use explicitly for a clean-room reconstruction, compatibility replacement, or independently authored port.

Defines observable resource, latency, throughput, and failure constraints with controlled comparison environments. Use explicitly when performance or bounded resource behavior is part of reconstruction acceptance.

Plans independent implementations across programming languages while preserving defined runtime semantics and public interfaces. Use explicitly for behavior-based ports or language migration reconstruction.

Reconstructs observable state machines, ordering, retries, recovery, and negotiation for stateful protocols. Use explicitly for network services, session APIs, or persistence behavior.

Records accidental source exposure or boundary failure, preserves evidence, and creates an honest recovery lane. Use explicitly when restricted information reaches an implementer or an approved handoff is compromised.

Builds a release evidence packet that separates compatibility, process provenance, isolation, and unresolved distribution questions. Use explicitly before sharing or publishing a reconstruction candidate.

Integrates an independently implemented dependency replacement through consumer checks, rollback, and bounded compatibility claims. Use explicitly after a reconstruction candidate and approved contract are available.

Converts restricted observations into a testable behavioral specification with evidence links, uncertainty, and compatibility scope. Use explicitly before an implementation handoff.