@lssm-tech/lib.orchestration-spec
The existing ./ai-improvement family also owns the complete validation and
validation-v2 supplied-model schemas through explicit leaves. These preserve the original shapes, error paths and timeout refinement. They validate supplied evidence, decisions and receipt envelopes; an approval or auto-merge boolean in a model does not verify current human authority or authorize execution.
./execution-lanes owns the canonical lane, plan, evidence and identifier declarations; its core, plan, evidence and identifiers leaves preserve the existing complete models and deterministic alias normalizers. Historical execution-lanes imports forward to these same declarations. Quality references use the pure assurance model owner. Execution, registry, readiness, storage, evidence gating and live authorization remain in their runtime owners.
The collaboration, roles, team and program leaves own the complete pure coordination records and CoordinatedProgramSpecV1 envelope. Existing task, lease, mailbox, worker, preservation, freeze and exact integration evidence semantics are preserved; these declarations do not create a coordination runner.
Cross-domain orchestration semantics for autonomous-company workflows.
This package does not define a new generic workflow engine. It binds existing @lssm-tech/lib.contracts-spec/workflow workflow IDs, step IDs, and transition IDs to domain refs, evidence links, policy gates, dispatch/receipt/outcome obligations, replay checkpoints, and saga/compensation requirements.
Public entrypoints
@lssm-tech/lib.orchestration-spec — root barrel@lssm-tech/lib.orchestration-spec/ai-improvement — canonical AI evidence, envelope, operational signal, observation, automation-risk, patch-receipt, and work-order declarations. Legacy ContractSpec AI-improvement imports forward to these same declarations and V2 values. Policy evaluation, validators and effectful improvement execution retain their existing owners.@lssm-tech/lib.orchestration-spec/ai-improvement/evidence — required AI improvement evidence capability ids and the pure completeness/fine-tuning trace checks (also re-exported by ./ai-improvement). Legacy
@lssm-tech/lib.contracts-spec/ai-improvement/evidence imports forward here.@lssm-tech/lib.orchestration-spec/durable-queue-v2 — provider-neutral queue envelope, workload, capability and lifecycle declarations with deterministic digest validators. Supported @lssm-tech/lib.contracts-spec/jobs/durable-queue-v2 imports forward to these same definitions.
Límite
The canonical build compiles all 33 model entry files while preserving the 29 public entrypoints and the explicit blocked workflow/step-config subpath. Export exclusions keep ai-improvement/contracts-v2,
ai-improvement/types, and immutable-artifact-ref behind their existing family or root entrypoints; they remain compilation inputs. The committed export maps are explicit; the build configuration disables export rewriting so repeated prebuilds preserve the manifest bytes and blocked subpaths.
- Provider-neutral contracts only.
- No module imports.
- No provider SDKs, I/O, runner, queue, state store, retry runner, or compensation executor.
- Phase 2 infra-ops workflows are deferred and may only appear as deferred refs.
The additive ./durable-queue-primitives leaf owns the existing pure queue scope, digest-reference, version-binding and trace declarations plus deterministic secret-material and canonical-order predicates. Historical ContractSpec queue imports forward to the same schema instances and functions. These models do not implement a queue executor, grant authority, access secrets or call a provider.
The root exports the complete ImmutableArtifactRefV1 declaration: required id, digest and version strings. Legacy self-improving-system types forward to this same canonical supplied-reference model; this declaration does not verify a digest or authorize execution.
The ./workflow/spec and ./workflow/workflow-devkit leaves own the complete existing workflow graph, retry, compensation, adapter and devkit declarations,
defineWorkflow identity factory and same-file documentation. The
./shared-entities/task leaf retains the full cross-context SharedTask, status constants and TaskEntity registration. Historical imports forward to these same values. The nominal workflow registry remains in WorkflowComposer; these model leaves do not execute workflows.
Canonical compatibility leaves: ./feature-hubs/federation, ./feature-hubs/policy, ./feature-hubs/ports. Historical ContractSpec imports forward to these exact declarations and implementations.
