@get-modular/assembly

Optional pre-1.0 construction support above the public @get-modular/core root. Node.js >=24.18.0 <25; ESM; TypeScript consumer floor 5.8.3.

assemblyFor<C>() returns bindFactory and prepare. Describe each Host-owned capability in C using CapabilityContract<Value, ExactToken>. Pass a literal Core declaration to bindFactory; its slots determine the callback's dependency record. The callback receives that record and { signal }, and returns an ordinary current-realm Promise fulfilling with { instance, capabilities }.

Module, implementation, profile and capability identities, and exact compatibility tokens, use Core's portable grammar, for example synthetic/store and synthetic/v1. Owner path segments and slot IDs remain local, for example store. Returned capability records use the full capability IDs as keys; dependency records use the consumer's local slot IDs.

Compile with public Core, then call prepare({ composition, factories, roots: { app: appHandle } }). A "prepared" result exposes prepared.run({ signal }); an omitted signal gets a fresh signal for that attempt. Preparation failures have status: "failed", a stable error.code, an opaque cause, and separate Core diagnostics.

Run outcomes have status "succeeded", "failed" or "cancelled". Successful roots.app has the instance type inferred from appHandle. Every outcome has an ordered created journal. A failed outcome also has phase, code, cause, implementationId, cancellation and returned. When returned is present, it contains the exact untransferred fulfillment and its implementation ID.

The Host owns authorization, resource ownership and cleanup. Assembly performs no rollback or disposal. Shared capability references can describe the same resource several times; Host cleanup must account for that sharing. Cancellation waits for an in-flight factory to settle. Construction does not establish readiness.

The package freezes its metadata, records, arrays and journals. Instance objects, capability values, causes and signals remain opaque. Direct thenable objects, Promise subclasses and Promises with own string properties or symbol accessors are unsupported factory carriers. Own symbol data properties used by Node async context tracking are permitted and ignored.

Build Core first, then run this package's build, typecheck and test commands. The runtime test command also invokes the minimum and build TypeScript compilers in NodeNext and Bundler modes. Test configurations disable isolatedDeclarations and erasableSyntaxOnly; production compiler settings remain independently enforced.

Packed tests install local Core and assembly archives into a disposable consumer, exercise the synthetic Host, and check typed wiring, deliberate negative fixtures and 1000 literal declarations. The scale fixture is only typechecked.

First public publication targets Assembly 0.1.0 with exactly Core 0.1.0. Availability requires registry reconciliation and downloaded-byte consumer checks; source tests alone do not establish publication or conformance.

Release validation can reuse the same consumer checks without packing or deleting supplied archives. Set GET_MODULAR_ASSEMBLY_ARCHIVE and GET_MODULAR_PUBLISHED_CORE_ARCHIVE to retained absolute archive paths, plus GET_MODULAR_ASSEMBLY_SHA256, GET_MODULAR_ASSEMBLY_INTEGRITY, GET_MODULAR_PUBLISHED_CORE_SHA256 and GET_MODULAR_PUBLISHED_CORE_INTEGRITY from the release record. Run node --test packages/assembly/tests/packed-root.test.mjs from the repository. The harness checks physical archive contents, installed byte equality, runtime and type consumers, and emits identities and observations for retention. The release operator separately authenticates the Core archive's registry origin; input hashes alone do not prove where an archive came from.