0.3.7

May 25, 2026 · 2 packages · 10 unique changes · 5 release entries

libsmodules

This release affects the sharedLibs, solutions familyies.

Run contractspec connect adoption resolve --family sharedLibs to see how it impacts your project.

Release summaries

opa-os-ready-runtime-module-examples
Make OPA OS ready with a module runtime and buildable example package.
maintainer
Maintainers get an additive OPA module runtime that composes local planning, agendas, booking proposals, markdown exports, approvals, and audit payloads without side effects.
integrator
Integrators get a buildable OPA example package showing Mission Relay, NDconsulting, and Axoperf-style inputs through the reusable module runtime.
agent
Agents can use the module runtime to propose OPA artifacts with approval gates, source refs, risk summaries, markdown, and audit events before host approval.
opa-os-static-safety
Add a static safety gate and documentation for OPA OS provider-neutral release verification.
maintainer
Maintainers can run a repo-level OPA OS static safety check before release to prove the planning surfaces remain provider-neutral and credential-free.
integrator
Integrators get documented verification that OPA examples do not perform live calendar writes, client sends, provider calls, or production credential reads.
agent
Agents have a deterministic command for checking OPA approval-packet and external-effects-blocked invariants before claiming readiness.
opa-os-v0-1-implementation
Implement OPA OS v0.1 local/manual planning, agenda, and booking proposal primitives.
maintainer
Maintainers get an additive OPA v0 entrypoint with provider-neutral schemas, action contract manifest, deterministic local functions with caller-supplied audit timestamps, fixture scenarios, markdown export, and audit payloads.
integrator
Integrators can generate local/manual day plans, agendas, and booking proposals while preserving human approval boundaries for external calendar or client-facing effects.
agent
Agents can propose OPA artifacts with confidence, assumptions, required approvals, source refs, risk summaries, and audit event payloads.
organization-planning-agenda-core
Add Organization / Planning / Agenda core contracts for autonomous-company scheduling and planning.
maintainer
Maintainers get a provider-neutral contract package for availability, booking/routing, capacity, agenda blocks, schedule decisions, and orchestration handoff evidence.
integrator
Hosts can model booking, focus planning, habits, and project auto-plans without calendar provider writes or optimizer runtime coupling.
agent
Agents can produce reviewable schedule decisions with authority, policy, conflict, capacity, idempotency, replay, and approval evidence refs.
organization-planning-cross-module-core
Organization/Planning/Agenda Phase 7 - Full Core Cross-Module Integration
maintainer
Cross-module contracts with PlanningModuleRef, PlanningModuleHandoff, PlanningAdapterPortObligation, OrganizationPlanningCrossModulePlan, PlanningCoreReadiness for developers, architects, contract-authors, module-authors, integration-authors, and ai-agents.
integrator
Pure projection helpers projectToCrossModulePlan and cross-module validation, async composition with adapter port execution composeOrganizationPlanningCore, typed adapter port interfaces for all 12 modules, and deterministic fake adapters for testing.

Upgrade steps

Use the side-effect-free OPA runtime
assisted
Import runOpaManualLoop from @lssm-tech/module.organization-planning/opa-runtime to compose the first local/manual OPA loop.
Packages: @lssm-tech/module.organization-planning, @lssm-tech/example.organization-planning-agenda
1. Keep customer-facing bookings and external agenda sharing behind human approval.
2. Use the example package as a copyable fixture before adding provider integrations.
3. Do not wire calendar writes, client messages, or provider SDKs into the module runtime.
Use the OPA v0 local/manual entrypoint
assisted
Import from @lssm-tech/lib.organization-planning-spec/opa for availability, day planning, agenda, booking proposal, markdown export, and audit payload helpers.
Packages: @lssm-tech/lib.organization-planning-spec
1. Keep external booking and agenda sharing behind human approval.
2. Use local fixture objects first; do not wire provider calendar writes through this package.
3. Export markdown for Notion/manual review before adding integrations.
Run the OPA OS static safety gate before release promotion
assisted
Use `bun run opa-os:safety` with the existing OPA tests/typechecks when touching OPA spec, runtime, examples, or release capsules.
Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/module.organization-planning, @lssm-tech/example.organization-planning-agenda
1. Keep live provider adapters, raw credentials, production writes, and client-message sends out of the deterministic OPA surfaces.
2. Keep future provider integrations in separate approval-gated lanes with redacted credential references.
3. Preserve `externalEffectsBlocked: true` and approval-packet persistence until a reviewed adapter lane explicitly changes the boundary.
Model scheduling and planning through provider-neutral refs
assisted
Use organization-planning packets for availability, booking/routing, focus capacity, agenda blocks, and auto-plan decisions before provider adapters execute.
Packages: @lssm-tech/lib.organization-planning-spec
1. Reference CompanyOS authority and policy gates rather than copying work ownership into calendar records.
2. Reference orchestration workflow, step, idempotency, checkpoint, and replay evidence for cross-domain handoffs.
3. Keep live calendar writes, notification delivery, payments, credentials, and optimizer runtimes outside this package.
Explore cross-module planning features
auto
New subpaths available for cross-module features including projections, fixtures, composition, adapter ports, and fake adapters.
Packages: @lssm-tech/lib.organization-planning-spec, @lssm-tech/module.organization-planning
1. Review the new cross-module contracts in lib.organization-planning-spec.
2. Explore the three flagship cross-module fixtures (revenue booking, capacity reschedule, builder delivery).
3. Use the async composition helpers for adapter port execution.
4. Leverage deterministic fake adapters for testing without provider SDKs.

Unique release changes

- Add a static safety gate and documentation for OPA OS provider-neutral release verification.
2 packages · 2 occurrences
- New subpaths available for cross-module features including projections, fixtures, composition, adapter ports, and fake adapters.
2 packages · 2 occurrences
- Organization/Planning/Agenda Phase 7 - Full Core Cross-Module Integration
2 packages · 2 occurrences
- Use `bun run opa-os:safety` with the existing OPA tests/typechecks when touching OPA spec, runtime, examples, or release capsules.
2 packages · 2 occurrences
- Add Organization / Planning / Agenda core contracts for autonomous-company scheduling and planning.
1 packages · 1 occurrences
- Implement OPA OS v0.1 local/manual planning, agenda, and booking proposal primitives.
1 packages · 1 occurrences
- Import from @lssm-tech/lib.organization-planning-spec/opa for availability, day planning, agenda, booking proposal, markdown export, and audit payload helpers.
1 packages · 1 occurrences
- Import runOpaManualLoop from @lssm-tech/module.organization-planning/opa-runtime to compose the first local/manual OPA loop.
1 packages · 1 occurrences
- Make OPA OS ready with a module runtime and buildable example package.
1 packages · 1 occurrences
- Use organization-planning packets for availability, booking/routing, focus capacity, agenda blocks, and auto-plan decisions before provider adapters execute.
1 packages · 1 occurrences

Impacted packages

@lssm-tech/lib.organization-planning-spec
Layer: libs · 2 changes
@lssm-tech/module.organization-planning
Layer: modules · 2 changes