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

Service

define { name; description?; package; capabilities; protocols?; config?; } builds a typed ServiceSpec and attaches an operations field holding the runtime-op program that materializes the service:

declareCapability(c1) … declareCapability(cN)   # one per category
declareProtocol(p1)   … declareProtocol(pM)     # one per protocol
declareService(svc)
materializeUnit(svc.name)

The eager compatibility check fires inside the underlying mb.operations.service smart constructor — invalid services cannot be constructed. compatibility and descriptor are re-exported from mb.descriptions.runtime for consumer convenience.

program is a shortcut: pass either a service value or the arguments to define, and receive an internalized builder program.

prevProtocolReplServernext