Navigation
ManualIntroductionGetting StartedBuilder SpecsOperationsPrograms And ViewsDesigning Builder SurfacesOutputs, Evidence, And Runtime ArtifactsMaterialization ModelAuthoring Production Builders
TheoryBuilders As DescriptionsInternalized ProgramsOrnaments And Domain SurfacesInterpretation And ViewsEvidence, Descriptors, And Runtime Structure
ExamplesNode service exampleSource filesNode service builder moduleserver.jsC code generation exampleSource filesC codegen builder modulemessages.defmain.cBridge exampleSource filesBridge proof moduleIDL exampleSource filesIDL builder moduleschema.protoOCI image exampleSource filesOCI image example module
API Reference
Core APIDescriptionsOperations
ProgramValidateDepsDry-runPlan-viewDescribeIntrospectMaterializeBackendsFormerPlan-export
ReferenceSchemasDatatypes
OrnamentsProject-builderDependenciesImplementationsToolEnvTestingVendoringCode-genIdlCapabilitiesProtocolServiceReplServerSandboxTransformOci-image
Library HelpersTool-envToolchainPassthruBundledDashboardContentAddress

Oci-image

OciImageBuilder refines BuilderSpec with image metadata (layers, entrypoint, cmd, env, exposedPorts, labels, architecture, os) so OCI images carry their runtime contract in the type.

The ociImage smart constructor compiles a single config record into a typed spec whose operations assemble a spec-conformant OCI image layout (oci-layout, index.json, blobs/sha256/*) entirely at build time: per-layer rootfs assembly and deterministic tar, then config/manifest/index rendering in digest-chain order, a blob self-check, scratch cleanup, and an image.oci.tar archive of the layout — each as a named step so every fold renders the assembly legibly.

prevTransformTool-envnext