Files

@hypit/compiler

Domain-neutral compilation orchestration.

This package is outside Core. It connects a replaceable definition-time Workspace to the already implemented compiler IR:

ResolvedSource + registered Frontends + registered manifests
  -> discovered Source/Module closure
  -> typed Source Closure
  -> AuthorGraph + public Source exports

Every Author Source reaches the compiler as a ResolvedSource with an exact Frontend. The default filesystem Workspace can obtain that binding through @hypit/source/text; another Workspace or package Source export can provide it directly. The compiler has no suffix table, body bootstrap or entry-Frontend default. A recursively imported Source may select another Frontend through its own resolution authority.

ModulePackageRegistry maps author import spellings to exact, already trusted manifests and closes their declared Resource dependencies. It does not install npm packages or execute module code. An embedding application must register the manifests and matching Frontend/package declaration implementations it has chosen to trust.

Compiler requires the host-neutral Workspace contract. The reference CLI explicitly selects @hypit/workspace/node, where every recursive Source import is confined to the canonical root that owns the importing SourceUnit, symlink escapes are rejected and each edge is locked to the first bytes read for that compilation. The Host may explicitly mount another Source root; the Compiler sees only the resulting Workspace units and does not know whether that root came from an installed data package, Git, memory or another source. Another Host can supply a different Workspace without changing Frontends, package declarations, Source Closure identity or Core.

The Workspace session owns a separate Source Asset capability. A Frontend or package declaration compiler may request an asset and assign its exact media type, but it never receives a path, filesystem handle or ambient read authority. The Workspace returns a BlobRef, the compiler binds that reference into the requesting SourceUnit, and the session exposes defensive generic BlobAttachments whose blob field names that exact reference on the Node compilation result. check and plan perform no ResourceStore write. build passes the attachments to the selected Runtime for size-checked staging.

SourceUnit recursion and Source Asset resolution are intentionally different capabilities: an asset cannot import syntax, and a source import does not silently make arbitrary neighboring bytes available to package code.

Compiler runs a discovery pass first because imports must be known before source decoding, while the exact Module Closure must be known before typed Records can be verified. It then invokes the Source Closure compiler and parser-independent Author linker.

The embedding Host supplies SourceCompilationLimits for one finite compilation. Source count, import edges and depth are accepted during discovery; Record and Component counts are accepted after decode; bytes requested through the readable author-asset capability are counted when read. Defaults are provided for ordinary Hosts, and a Host may choose stricter or larger limits. These are execution limits only: they are never copied into Source Closure, AuthorGraph, BuildDefinition, Programme or Result values, and they do not form a central complexity score.

BuildCompiler compiles an Author Source together with one explicit transient Target selection from CLI or Studio arguments. Durable Records, operations and consumer references remain in the Author Source. The compiler follows each demanded output through its one fixed AuthorGraph producer, then asks Core for the finite BuildPlan. CompiledBuild owns that Author compilation; it does not repeat its Programme or attachment bundle as sibling fields.

Normal compilation does not return source-range provenance. An authoring consumer that actually joins graph values back to source elements requests authorProjection: true; the resulting ProjectedCompiledAuthorSource carries that disposable projection. Check, plan and build do not precompute or transport it for a hypothetical interface.

prepareBuild turns that completed structural selection into a PreparedBuild: it derives one immutable ResultIntent and seals the BuildDefinition. An interactive authoring consumer may request executionView: true to receive resolved outputs and the Kernel's disposable BuildView; ordinary Build preparation does not expose either projection. The prepared targets describe the execution goals; the intent separately contains only reachable package-owned retained outputs and carries their Result name and current Record without leaking Logical Output identities into Result storage. CLI catalogs, Runtime submission and Result writing consume this intent; they do not repeat structural selection or interpret Result history as author input.

The package contains no Script, video, Provider, queue, credentials or rendering knowledge. A non-video application can use it with only its own manifests, Frontends, declarations and chosen Workspace implementation.

Package installation, third-party code loading and sandbox execution remain Host features above this registry; treating an import string as permission to execute npm code would violate the trust boundary.