IMPLEMENTATION SPECIFICATION Engineering Blueprint A Software-Production Controller That Can Reconstruct Its Missing Tools 1 November 2026 System specification This specification defines the boundary between an LLM that proposes actions and a system that can execute, verify and deliver the requested software. Its design target is a resumable software project that can acquire a missing engineering tool during the build. Every work item names the product behaviour it serves, the capability it needs, the authority under which it can execute, and the evidence that permits its successor to run. Discovery of a missing tool creates a child obligation under the original project. Success returns a pinned capability identifier to that obligation and wakes the blocked work. The blueprint specifies a target architecture. The companion experiments exercise individual paths. The worked design below is marked separately from the measured protocol fixture. LLM host intent + typed calls Controller job + obligations Receipt store state + causal history REA + reference observations / traces Candidate builder recipe + evidence Registry admitted versions missing requirement admit Acceptance runner user-visible outcomes Isolated executor pinned recipe + grants Artifact / target local or authorized host resolved dependency Component architecture and the boundary between an admitted tool and an ac- cepted product. 1. Contracts between components Component and owner Input → durable output Boundary checked before handoff Host adapter and project intake User request, host features, intended destination → versioned project brief Record deliverable, target platform, permitted spend, disclosure boundaries and required human decisions. Preserve the exact request. 1 Autonomous software synthesis Engineering blueprint Component and owner Input → durable output Boundary checked before handoff Requirements compiler Brief → product scenarios, invariants, explicit assumptions, test oracles Each required behaviour has an observable success and failure case. Ambiguity that changes a material product decision is surfaced. Dependency planner Scenarios, target profile, installed inventory → typed AND/OR recipe graph with witness plans A selected plan satisfies every prerequisite with compatible, authorized providers. A cycle needs an independently available seed. Capability resolver Requirement fingerprint → eligible published digest or missing-capability job Match input domain, effects, semantics, target, grants and valid evidence. An operation name alone is insufficient. Reconstruction laboratory Missing job, reference rights, approved observations → contract, candidate artifact, evidence dossier Untrusted references run in an isolated environment. Inspection permission and distribution permission are evaluated separately. Builder and independent evaluator Contract, material lock, candidate digest → test evidence and scoped verdict Builder lacks access to the sealed promotion tests and to registry signing. Verifier cannot relax the product criteria. Registry and artifact store Candidate, provenance, independent verdict, policy decision → immutable record and release channel Resolve channels only at plan time. Execute by verified digest. A quarantined digest is denied on subsequent invocations. Durable controller and workers Graph, pinned providers, scoped work assignment → receipts, artifacts, next eligible node Persist a lease, revision and logical action identity. Recover unknown results before retrying a consequential action. Invocation broker and isolated runners Typed call, grant, artifact → checked output or classified failure Match tenant, grant, effect, destination, clock, budget and runner target. A model cannot directly mint these bindings. Delivery and operating adapters Approved release manifest, target grant → receipt and target-side probe Verify install/start, workflow, persistence and recovery at the named destination. Keep artifact production, external submission and acceptance as distinct outcomes. The host adapter can be replaced without rebuilding the capability when it preserves the contract. The runner can be replaced only after its declared target passes the portability tests. Keep signing, secret issuance and spend authorities outside model-accessible shells. Route each verifier to the artifacts and oracles appropriate to its assignment. A separately named agent that can modify the oracle or validator does not provide independent evaluation. From an ordinary request to executable acceptance Retain the original text and its revision beside the interpreted requirements. For each claim store the actor, action, object, permitted starting state, observable consequence, delivery target, evidence source and whether the user stated it or the planner inferred it. A second reader compares those claims with the original request before the implementation worker receives them. Only the owner can grant external effects. A planner can propose a target but cannot turn its proposal into credentials or spending authority. For “save titled links between restarts,” the persistent object is the title–URL pair. An acceptance case inserts a previously unseen pair, stops the application process, restarts against the same data store, and 1 November 2026 2 Autonomous software synthesis Engineering blueprint retrieves exactly that pair through the user-facing interface. A test that asks the running process to read back its own in-memory state misses the consequence implied by “between restarts.” Record a local- only destination as an explicit assumption if the user did not specify hosting. If a public destination is required, create a separate delivery obligation and retain the working local build while the destination grant is resolved. Delegate a branch as a work item with the project revision, product obligation ID, expected artifacts, permitted inputs, write scope, budget and completion predicate. The tool-builder returns a candidate and evidence. A separate evaluator can accept, reject with a counterexample, or record an unobserved requirement. The controller makes concurrent writers claim disjoint artifacts or explicit revision leases. It verifies every handoff against its declared outputs and resumes the same product obligation on successful admission. 2. Finding the missing operation Represent a capability requirement as a semantic contract, a target profile, admissible effects and ver- ification obligations. Each recipe lists all prerequisite capabilities, external facts, expected resources and an operation that yields the new capability. Alternative recipes can supply the same operation. A recipe that compiles a binary for one architecture does not satisfy an obligation to run it on another architecture without a verified translation or execution path. Begin with provisioned, executable seeds. Examples include a pinned operating-system image, lan- guage runtime, artifact reader, compiler where needed, and a trusted verifier. Add a recipe’s output only after every prerequisite has a compatible witness and every required external fact has a current receipt. Iterate until the target is reached or no new fact can be added. Record one predecessor set per reachable output. On failure, expose the smallest observed missing set for a particular recipe and any alternative recipes examined. A global minimum blocking set requires explicit enumeration or an appropriate solver. Two distinct predicates drive implementation. Structurally reachable means the graph contains a sup- ported recipe under its declared assumptions. Ready to execute additionally requires concrete tool and environment digests, grants, test evidence and live resource availability. A target is delivered only when product-level oracles pass in the designated delivery environment. The graph can generate a useful engineering plan even when no live provider or grant is available. resolve(requirement, target, grants, active_stack, budget): if requirement in active_stack: return cycle witness filter published versions by contract, effect, target, grants, evidence verify integrity and choose an eligible pinned version if present for each admissible recipe in deterministic cost order: resolve every prerequisite with this requirement on active_stack if all succeed: return recipe plus prerequisite witnesses join or create one reconstruction job keyed by requirement and scope preserve original waiter and remaining budget in durable storage return job handle or a precise unresolved obligation Cost is considered only after feasibility and authority. Rank candidates by route preference, expected test/build cost, expected implementation effort, then immutable identity as a tie-break. For a single product, direct use of a verified existing tool may meet the objective immediately. If the objective is independent self-hosting, a wrapper around a vendor service leaves that obligation open. A new patch release that changes the error semantics or resource profile must reacquire evidence for those changes. 1 November 2026 3 Autonomous software synthesis Engineering blueprint CLI editor GUI editor Edit source OR Board access external fi xture Firmware image prior build Physical validation measure on target AND Simulator check emulator available Dependency graph excerpt. An unfulfilled physical fixture requirement survives suc- cessful emulation. 3. Reconstructing a capability with evidence Freeze a reference dossier before observing behaviour. Record the owner or public source, reference bytes or version, allowable analysis and distribution route, execution target, input generator, network policy, oracle, and known inaccessible state. The REA adapter receives the minimum authorized artifact set. Material obtained from references may include executable behaviour, untrusted instructions or data. It has no control authority. Reference output is retained with its origin, time, environment, invocation and digest. REA’s documented modalities and provider requirements inform the inspections below [B9]. When REA can emit a reconstruction obligation ledger, import its claim ID, obligation revision, ob- servation authority, implementation-owner digest, fixtures and verifier references. Preserve candi- date and unresolved states. A static finding can nominate a required behaviour. It cannot replace process-level observation when process behaviour is the claim. The Foundry adds the relation from each upstream claim to a product obligation and the independently observed outcome in its delivery environment [B11]. Reference class Proposed investigation Candidate and decisive check Licensed source, library or build tool Pin release and transitive inputs. Trace public calls, data formats, error paths and build outputs. Record which source was read and which was reused. Adapt permitted source or implement a contract separately. Rebuild in a clean environment and compare artifacts or their specified semantics on unseen projects. Native binary or command-line tool Inspect headers and static call/reference evidence where a compatible provider is available. Vary arguments, environment, input files and exit conditions in isolated processes. Model input/output, errors, state and effects. Exercise malformed/truncated inputs, different locales, repeated runs and file effects. Addresses and pseudocode are evidence, not source-equivalence guarantees. 1 November 2026 4 Autonomous software synthesis Engineering blueprint Reference class Proposed investigation Candidate and decisive check JavaScript, Electron or managed application Recover module/import/IPC or managed metadata using the applicable inspection path. Probe public entry points to distinguish reachable behaviours from unused branches. Implement a bounded module or IPC operation. Compare success and error envelopes, async ordering, encodings and state after process restart. Browser or service API Capture approved requests in a dedicated test identity. Redact secrets before storage. Vary request, initial state, identity, request order and timing. Implement a protocol-compatible service on independent storage. Test create/read/update/delete, deduplication, isolation and restart against unseen sequences. Recorded response replay is a control condition. GUI, CAD, media or simulator Recover file or interaction contracts, coordinate frames, units, timing and tolerances. Use domain fixtures or documented standards where internal logic is unavailable. Verify geometry, topology, pixels, decoded samples, temporal order or invariants with a separate parser or renderer. A screenshot alone cannot certify editability, file fidelity or physical precision. Firmware or hardware-coupled operation Identify package sections, target architecture, peripheral boundary and timing needs. Static triage or emulation can inform the contract. Establish emulator equivalence only in its declared scope. Physical behaviour, signed loading, power or real-time deadlines need appropriate measurements and equipment. Source reuse records licence, notices, modifications, dependency obligations and distribution target. Under independent reconstruction, an evidence reviewer can produce an approved behaviour specifi- cation for a separate builder with no access to restricted source. Preserve both custody histories. This separation documents provenance. It does not settle rights in every jurisdiction. Unknown permission blocks that route. A licensed integration or a public protocol can provide an alternative. Split validation into development probes, repair tests and sealed promotion inputs. Define an equiv- alence relation for observable results before running the candidate. Byte equality is appropriate for canonical deterministic bytes. Stateful services require equivalent outcome traces and externally visi- ble effects from equivalent initial conditions. Numerical outputs need units, error metric, tolerances and exceptional-value rules. Nondeterministic systems require specified invariants or a distributional test with prespecified sampling and uncertainty. An exclusion of a behaviour is part of the registered contract. reconstruct(job): acquire rights and immutable reference identity derive a versioned, scoped contract from allowed evidence reserve a sealed validation batch with the evaluator while probes, candidates, elapsed time and spend remain: construct a candidate or revise it from development counterexamples run differential and property tests on the repair partition if no repair failure remains: freeze artifact, contract, material lock and provenance evaluate once against the sealed batch if accepted: request registry promotion and wake original waiters retire the batch before using a disclosed case for repair record smallest counterexample and its changed hypothesis 1 November 2026 5 Autonomous software synthesis Engineering blueprint return bounded failure, candidate history and unresolved witness An improvement that narrows the admitted input domain creates a new contract version. Check the original product requirement again before resuming. An unobserved feature may remain unspecified. A version claiming whole-product replication would require a substantially stronger equivalence ar- gument than a bounded replacement used for one build. 4. Wire contracts and portability The companion directory supplies four schema files, examples, the semantic contract of a small ex- ecutable, and an OpenAPI description. All use the JSON data model. JSON Schema Draft 2020-12 describes instance structure [B4]. Operation-specific oracles verify meaning, side effects, timing and acceptance. Pin the actual digest of a manifest, artifact, contract and suite. This design hashes the exact bytes of files and uses SHA-256 over RFC 8785 canonical JSON for interoperable JSON identity [B8]. Reject an input outside the chosen canonicalization domain or translate it through a versioned codec before hashing. The sample digest generator supports its ASCII-key, integer-only example records. Envelope Required meaning Verification outside JSON validation Manifest Stable semantic name, version, contract digest, executable digest and entry point, pinned requirements, runtime targets, effect class, scopes, rights record, run limits Verify signature on publication, material digests, rights, target availability and policy. Resolve each dependency to a locked digest in the project plan. Invocation Project, operation, logical action ID, pinned manifest, argument digest, grant reference and typed arguments Authenticate caller separately. Match artifact, content and declared effect. Look up exact scopes and targets of grant. Apply input schema. Receipt Final success carries output digest and evidence reference. Other outcomes carry structured code, outcome state and evidence reference. Resolve the evidence in tenant storage and check authority, receipt authenticity, actual output schema, and linkage to the logical action. Attestation Subject manifest, semantic contract, suite, environment, evidence, issuer, verdict, scope and UTC expiry Check issuer identity and independent role, signature, trusted clock, applicable target and revoke list. The provided fixture is unsigned and indeterminate. For host compatibility, choose a common discovery and invocation contract. In the pinned MCP pro- file, negotiate the protocol version, exchange declared features, complete initialization, list tools, then invoke by name using structured arguments. Return structured content and the text representation expected by the selected client. Unknown tools are protocol errors. Invalid operation arguments are tool execution errors [B1, B2]. For HTTP consumers, use an OpenAPI 3.1.1 operation mapping with the same input and output schema [B3]. Convert transport failures separately from domain errors. A successful HTTP response or JSON-RPC envelope does not establish product acceptance. For a strict function-calling host that admits a narrower schema vocabulary, lower the contract into its supported subset, preserving numeric ranges, null meanings, disjoint variants and required fields when possible. Keep complete server-side validation. Refuse the mapping if the host cannot carry required structured results or if critical distinctions are lost at the decision boundary. Names, aliases or descriptive metadata are untrusted hints. Text-only hosts can submit proposals to a separate tool- use harness, provided it authenticates and validates each call. A language model alone cannot operate 1 November 2026 6 Autonomous software synthesis Engineering blueprint the executor. Command-line and SDK clients are thin wrappers around the same broker. Pass CLI arguments as an array, with immutable input handles, binary output references and explicit exit-class mapping. Expose only the eligible inventory for an authenticated project. Reauthorize at invocation time. Set a polling or refresh strategy for hosts lacking change notifications. Binding a short name to a new con- tract cannot silently change an in-flight project. Make migrations explicit, run both implementations on a representative case set, preserve the old digest and roll back the release channel on regression. Controller Factory Registry Evaluator resolve capability for job J no compatible frozen version request repair for J candidate + evidence + scope passing verdict for this digest admitted version available test product built with the admitted digest acceptance receipt identi fi es product and target Dependency acquisition during an active product job. The original controller receives the admission receipt. 5. Durable product execution Persist the following relations as a minimal transactional model. Store bulk inputs, logs and deliv- erables in a content-addressed store. The primary store tracks immutable references and evidence access. Relation Key and invariant Project and requirement revision An immutable objective revision owns its acceptance set, destination and policy reference. New revisions identify affected completed checks. Work item and dependency Unique project, revision, semantic node and target. Dependencies reference input-producing nodes and selected provider digests. A parent can wait while unrelated children advance. Attempt, logical action, outbox Unique tenant and logical action. Attempt number and lease epoch vary across retries. Output events and checkpoints share one local transaction. Build job and waiter Unique tenant, rights domain, target, contract, oracle profile and trust policy. Multiple projects may wait only when sharing is allowed and artifact confidentiality is preserved. 1 November 2026 7 Autonomous software synthesis Engineering blueprint Relation Key and invariant Immutable artifact, attestation, grant Distinguish bytes and signatures from mutable release aliases, grant validity and quarantine. Recheck mutable policy when claiming a work item. Acceptance and release receipt Every mandatory criterion binds the observed product revision, target and environment. A delivery receipt identifies destination, artifact, probe result and recovery reference. Claim ready work by compare-and-swap on revision and lease epoch in a transaction. A competing worker with an expired lease cannot commit state over a newer result. Deterministically derive the logical action ID from the project, revision, node, intended effect and destination. Keep retries on that same identity. Bind the argument digest to it and reject key reuse with different content. A deliberate repeat receives a new logical action identity. begin transaction claim READY node using expected revision and lease epoch reserve cost and insert action intent with unique logical action key enqueue dispatch in outbox commit worker consumes intent, rechecks grant and resolves target receipt if key already succeeded: recover output without issuing the effect otherwise dispatch using provider-side idempotency or safe compare-and-swap begin transaction validate epoch and attach immutable evidence commit receipt, release reservation, satisfy dependent nodes commit The failure between external effect and local receipt is decisive. If the provider enforces idempotency, retry inside its key retention window with the same key and payload. If it permits querying a stable cor- relation identifier, reconcile with the target state. A lookup that returns absent does not by itself prove that another delayed request cannot still commit. Without idempotency, conditional writes or proof that no earlier request can still commit, park the work as unknown external outcome . Preserve intent and evidence. Issue no second irreversible action. Reversal requires a separately authorized compensation whose own result must be verified. Temporal’s documentation describes the re-execution window for activities that fail to report completion [B6]. Outcome or failure Controller response Pure computation crashes before publishing Retry under budget using pinned inputs. Deduplicate artifacts by digest. Incompatible interface, revoked policy or missing external entitlement Stop that route, record the exact blocker, and examine other admissible recipes. Ask for the smallest genuine grant or product decision when necessary. Failing test or new counterexample Create a repair attempt linked to the failing witness. Preserve unaffected artifacts. Use a fresh sealed set before promotion if the previous set was disclosed. Budget exhausted or repeated identical failure Close the attempt with its measured spend and smallest unresolved witness. A budget increase changes authority only when separately granted. 1 November 2026 8 Autonomous software synthesis Engineering blueprint Outcome or failure Controller response Cancellation during an external effect Prevent new dispatches, reconcile in-flight effects, release reservations once terminal, and classify any residual effect in the cancellation receipt. Known-good release fails after deployment Stop promotion, compare target-side evidence, and roll back if permitted. A database migration may need a verified forward repair or restore before the previous binary is usable. Define the product evaluator independently of the code generator. For a requirement such as “my changes survive restart”, query the deployed endpoint after terminating and restarting its process. For “other users cannot read my project”, exercise a second identity supplied by the test service. Include ordinary workflows, failure branches, target-specific probes, release packaging and handover. A del- egated worker can execute a probe. Only the acceptance service can attach a verdict to the objective revision. 6. Trust, provenance and resource allocation Authenticate projects at the boundary. Issue short-lived grants bound to subject, audience, action, destination and budget. For HTTP MCP deployments, follow the pinned authorization profile, vali- date token audience and use separate downstream credentials [B5]. The local stdio fixture uses caller- launched processes and does not establish remote authorization. Sensitive payloads belong in re- stricted object storage. Give the model a redacted evidence reference when possible. Launch untrusted references and candidates in separate disposable environments. Use a read-only base, unprivileged identity, ephemeral scratch, process/time/memory/output limits, private network namespace and an allowlisted egress broker when needed. Mount neither signing credentials nor container-management sockets. A hardened sandbox such as gVisor can reduce kernel exposure while introducing syscall and workload compatibility limits [B7]. Record the actual isolation mode. A nor- mal local subprocess does not supply the same boundary. Publish immutable material locks and machine-readable inventories of components, versions, origin, licence and modifications. Use separate provenance for construction and acceptance. A SLSA-style attestation binds outputs to build definition, inputs, builder and run details [B10]. It cannot establish what the output does. If reference or generated text requests privileged actions, treat those strings as data. If a package or tool description changes, invalidate its earlier digest binding. If the builder or verifier is compromised, revoke the corresponding signatures, quarantine descendants and rerun affected acceptance edges from trusted inputs. Initial experiment budgets can be set to 20 development probes, three candidate builds, one sealed suite per candidate, ten minutes per missing-capability job, 512 MiB of scratch and zero paid requests. These are proposed defaults for small pure capabilities. Production profiles must calibrate memory, time and output by class. Enforce an absolute project deadline and spend ceiling above all child jobs. Reserve before dispatch, charge on termination, and reclaim unused reservation. Limit recursion depth and disallow the same unresolved key re-entering its own stack. Record CPU time, wall time, peak memory, bytes, request count and human interventions separately. 1 November 2026 9 Autonomous software synthesis Engineering blueprint Plan Resolve Build + run Evaluate Wait for grant Reconstruct Repair Deliver gap admitted authority needed pass mismatch retry Unresolved Accepted no recipe receipt Job states, technical recovery, admission failure and authority waits. 7. Worked delivery path and implemented interface case Illustrative product brief. “Create a local service where I can upload a list of scores, see the scores in increasing order, and retrieve that list after restarting.” This example defines acceptance as HTTP upload plus successful retrieval after a fresh process opens the same database. The target is a local service and downloadable source. The assumptions are integer scores, preserved duplicates, no user accounts and a fixed maximum batch size. If the requested destination changes to a public multi-user site, identity isolation, online operation and release authority become new requirements. The controller selects HTTP handling, persistent storage, integer ordering, packaging and a restart probe. If ordering is absent, it opens a child job. The laboratory fixes the input domain, error conditions and independent oracle. It can register an existing operation or commission its implementation and promotion. The waiter receives a pinned manifest. The product builder wires that operation into upload, writes the result under a new identity in a transaction, reads it back through the public API and checks how malformed data affects persistent state. The acceptance worker sends novel data with duplicates, restarts the service, and retries retrieval with both valid and unknown identifiers. Delivery contains the source, release digest, startup target, test evidence and restart instructions. This is a design trace, distinct from the recorded trials in the paper. Measured interface case. The companion fixture implements the integer-ordering operation. It launches a real JSON-RPC stdio process and a separate loopback HTTP process, discovers each interface and sends inputs from separate wire paths. Six valid inputs per path produced the literal expected values, including duplicates, exact integral decimals, endpoint values, empty input and a maximal-size batch. Each path correctly rejected nine invalid inputs covering shape, bounds, type and array length. The run also checked eight protocol and description facts, nine content bindings, four valid wire envelope examples, eight invalid envelopes and agreement of four stored schemas with the typed definitions. The test used Python 3.12.14 and Pydantic 2.14.1. It exercised two scripted transport clients. Third-party LLM hosts, a production registry, signed evidence and remote OAuth flows remain separate acceptance obligations. Files and rerun instructions are in interfaces/ 1 November 2026 10 Autonomous software synthesis Engineering blueprint 8. Implementation sequence and release gates Stage Required engineering result Observable gate 1. Seed inventory Reproducible image, grantee identities, documents, process runner, artifact store, semantic contracts Rebuild the runner from pinned materials. Independently hash all seeds and resolve required target architecture. 2. Vertical delivery One product from a versioned request through packaging, launch and independent acceptance From a clean environment a fresh user completes the named product workflow. Report every manual decision and every externally provided seed. 3. Durable execution Transactional work claims, outbox, idempotency, provider reconciliation and revocation Kill workers before dispatch, after provider commit and before local acknowledgment. Duplicate writes remain absent, or an explicit unknown outcome blocks retry. 4. Capability construction Allowed reference triage, REA adapter, bounded builder search, oracle and signed promotion Remove one required capability. Observe its construction, rejection of a deliberately faulty candidate, registration, resumed original job and independent reuse. 5. Host and domain transfer Two real tool-capable hosts and a materially different product class Each host independently discovers the same digest, preserves errors, completes a product workflow and rejects an out-of-scope action. Test host reconnect and permission expiry. 6. Controlled operations Authorized staging adapters, target probes, supply-chain review, monitoring and restore Verify a release, inject a known defect, recover the earlier compatible product and data, and record destination-side observations. Production release is a separate project decision. Before claiming generality, withhold entire product families, reference implementations and host in- tegrations from development. Compare preinstalled, missing-with-reconstruction and missing-with- reconstruction-disabled conditions from clean, identical seeds. Include compatible reuse and inde- pendently implemented alternatives when they satisfy the same contract. Record failed attempts and external dependencies in the denominator. Separate wall time from model tokens, process startup and oracle time. Report both per-task acceptance and across-task variation. A passing finite experiment qualifies only its tested scope. An engineering release should also demonstrate rejection of wrong answers, unauthorized calls, stale artifacts and unreachable prerequisites. Primary technical references [B1] Model Context Protocol maintainers. Tools , revision 2025-11-25. Discovery, schemas, structured results and protocol versus execution errors. Primary source [B2] Model Context Protocol maintainers. Lifecycle , revision 2025-11-25. Session initialization, protocol versions and feature negotiation. Primary source [B3] OpenAPI Initiative. OpenAPI Specification , version 3.1.1 (2024). HTTP operations and their machine-readable representations. Primary source [B4] Wright, A., Andrews, H., Hutton, B., and Dennis, G. JSON Schema , Draft 2020-12. Instance valida- tion and the schema dialect used by the fixtures. Primary source 1 November 2026 11 Autonomous software synthesis Engineering blueprint [B5] Model Context Protocol maintainers. Authorization , revision 2025-11-25. HTTP resource audiences and downstream token separation. Primary source [B6] Temporal Technologies. Activity Definition , “Idempotency”. Authoritative discussion of retry win- dows and provider-side deduplication. Primary source [B7] gVisor project. Security Model . Isolation objective, threat assumptions and residual exposure. Pri- mary source [B8] Rundgren, A., Jordan, B., and Erdtman, S. JSON Canonicalization Scheme , RFC 8785 (2020). Canon- ical serialization of the supported JSON subset. Primary source [B9] Morluto and contributors. Reverse Engineer Anything , source repository and provider guides. Pinned revision d3ab0faf52a02ff5a618f3ed7beb608b78752abd. The research trial identifies the mate- rial and execution scope it used. Primary source [B10] SLSA authors. Build Provenance , specification v1.2. Machine-verifiable provenance fields and artifact linkage. Primary source [B11] Morluto and contributors. Reconstruction obligation ledgers , REA revision d3ab0fa. Upstream distinctions among a candidate obligation, evidence authority and a verified implementation owner. Primary source Appendix A. Reconstruction and acquisition routes Each row identifies the narrow operation the foundry can expose, a reference implementation or re- source, how to acquire or reconstruct that operation, evidence needed before admission, and what remains outside the reconstructed function. These are proposed design and testing routes. The refer- ence column names examples. The controlled trials are identified separately in the monograph and research package. Native executable evidence can establish a file layout, symbol, instruction behavior or a candidate ABI. Captured network or UI traces can identify protocol and workflow behavior. Neither observation supplies hidden service state, signing authority, hosting or hardware. Use direct, permitted integration when it already exposes the full required operation. For an absent suboperation, create a contract from permitted observations and test a separate implementation on fresh cases. External resource and authority rows require binding the actual resource or delegation. A simulated equivalent needs its own test-only identity. The accompanying file coverage/reconstruction_routes.tsv provides one record per root in cover- age/graph.json . This document presents the same records in engineering order. Host operations and human evidence Root and concrete reference Bounded operation and acquisition Admission test Persistent dependency process · POSIX spawn/wait, Linux process groups Launch one executable with fixed argv, stream both outputs, cancel its process group. Wrap the host runtime. Inspect controlled child traces for signal and pipe semantics. Known child exits, fills both pipes, spawns a grandchild and times out without leaking it. Host process API, scheduler and granted execution rights. 1 November 2026 12 Autonomous software synthesis Engineering blueprint Root and concrete reference Bounded operation and acquisition Admission test Persistent dependency files · POSIX openat, rename, fsync Atomic workspace replacement and bounded reads under a project directory. Wrap directory-relative OS primitives. Probe permissions, symlinks and crash points. Traversal and symlink escape fail. Killed replacements leave an allowed old/new state under the stated durability contract. Filesystem and host access policy. time · POSIX CLOCK_ MONOTONIC and timerfd Measure elapsed time, deliver a deadline and cancel a pending timer. Wrap the host clock. Use a fake only for deterministic scheduling tests. Under clock-wall adjustment and restart, a real deadline behaves within declared tolerances. Clock source, scheduler and persistent deadline policy. socket · POSIX TCP loopback sockets Bind, connect, stream, half-close and handle timeouts for one TCP profile. Wrap sockets. Observe authorized client/server transcripts and close/error behavior. Unseen fragmented payload, reset and half-close produce the required bytes and terminal status. Kernel network stack, reachable peers and permitted ports. policy · OPA policy evaluation plus kernel-enforced process quotas Decide one action using subject, resource, effect, deadline and budget. Enforce the result at execution. Integrate a policy evaluator. Route effects through an authenticated enforcement point. Denied calls have no side effect. Modified resource identifiers, stale grants and exhausted quotas fail at execution. Authority issuer, authenticated identities and trusted enforcement. intent · Product-owner brief and signed or authenticated scope Normalize requested outcomes and bind who can authorize each consequential effect. Capture the original brief and scope. Ask only when distinct behaviors remain material. Owner-selected examples discriminate competing interpretations. Separate permissions identify target and spend. Human goals and delegable decision authority. test_material · Independent test harness, withheld fixtures and relevant domain expert Expose a pass/fail predicate on the declared product behavior. Obtain an independent oracle, trusted specification or domain judgment. REA traces may seed separate discovery cases. A planted defect fails. Held-out expectations and reference digests were inaccessible to the candidate. Trustworthy oracle, appropriate test data and authority to use it. Development and build Root and concrete reference Bounded operation and acquisition Admission test Persistent dependency text_cli · GNU patch or Git apply Apply one textual change to a specified base tree. Reuse the tool or reconstruct a bounded hunk matcher from permitted patch grammar and paired fixtures. Patches relocate within allowed context, reject ambiguous targets and leave unrelated paths intact. Authorized files and an editor process. 1 November 2026 13 Autonomous software synthesis Engineering blueprint Root and concrete reference Bounded operation and acquisition Admission test Persistent dependency ide · Language Server Protocol and an editor client Find definitions and apply versioned multi-file edits in one language. Use documented LSP messages. Authorized UI observations can identify command-to-operation mapping. Rename across two files, reject a stale document version and compare resulting diagnostics. Language server, a compatible client and filesystem. vcs · Git plumbing and native object store Snapshot a tree, branch, merge and restore an immutable revision. Wrap Git and reconstruct a narrow object/query adapter only if its behavior is missing. Round-trip a clean checkout. Exercise conflict, symlink and competing ref updates. Persistent object store and authority to update refs. lockfiles · Pinned Python wheelhouse plus hashe