module.organization-planning

@lssm-tech/module.organization-planning

Organization planning composition module with typed adapter ports for cross-module integration.

The root exports resolveOpaAutomationPolicy for deterministic default/ceiling resolution and evaluateOpaProductionAcceptance for exact-target release receipts. Neither grants effects or verifies signatures by default. Hosts supply fresh authority and a trusted receipt verifier. The legacy three-product meeting qualification evaluator remains unchanged.

Composes planning packets into provider-neutral cross-module adapter-port obligations and readiness results. This module provides the bridge between organization-planning-spec contracts and actual cross-module execution through typed adapter ports.

Public entrypoints

• @lssm-tech/module.organization-planning — root barrel
• @lssm-tech/module.organization-planning/adapter-ports — typed adapter port interfaces and receipts
• @lssm-tech/module.organization-planning/composition — composition function and core logic
• @lssm-tech/module.organization-planning/fake-adapters — deterministic fake adapters for tests
• @lssm-tech/module.organization-planning/flagship-fixture — three flagship cross-module proof fixtures
• @lssm-tech/module.organization-planning/opa-runtime — side-effect-free OPA manual loop runtime
• @lssm-tech/module.organization-planning/domain-command-persistence — immutable OPA domain-command persistence events
• @lssm-tech/module.organization-planning/execution-authorization — fail-closed OPA execution authorization verdict

Ownership: adapter-ports, fake-adapters, domain-command-persistence and opa-runtime re-export the canonical implementations in @lssm-tech/lib.organization-planning-runtime/execution/*; execution-authorization re-exports @lssm-tech/lib.organization-planning-spec/opa-execution-authorization. The subpaths and names are unchanged and resolve to the same objects.

The root export also provides meetingIntelligenceCapabilityMatrix, the canonical delivery and qualification ledger for Meeting Intelligence across CompanyOS, Pactena, hCircle, calendar and recorder providers, knowledge sources, human/AI collaboration, post-meeting effects, rollout, and production evidence. Generate its synchronized documentation with bun scripts/generate-meeting-intelligence-matrix.ts. Rollout rows describe provider-neutral control readiness only; they do not activate a product cohort or constitute production qualification. The exported evaluateMeetingProductionQualification helper fail-closes a three-product exact-SHA packet across E2E, accessibility, security, privacy, performance, resilience, migration, production canary, and manual acceptance. It validates evidence only and performs no deployment or provider I/O. Callers must supply a host-owned receipt-attestation verifier; there is no default path that trusts structural receipt data. The evaluator also receives the expected packet, release, commit SHA, and a host-owned clock; its versioned policy caps receipt age at 24 hours and binds those identities into every attestation request and result. The same surface is available through the focused @lssm-tech/module.organization-planning/meeting-intelligence/capability-matrix entrypoint.

Adapter Ports

The module defines typed adapter ports for:

• companyos_work / companyos_commitment — CompanyOS work and commitment operations
• communication_send — CommunicationOS confirmation, reminder, and follow-up operations
• jobs_schedule — Jobs scheduler operations
• orchestration_workflow — Orchestration workflow triggers
• growth_qualification — Growth qualification recording
• finance_approval — Finance approval requests
• assurance_evidence — Assurance evidence recording
• integration_capability — Integration capability checks
• builder_delivery — Builder delivery processing
• rolemorph_surface — RoleMorph surface rendering
• calendar_execution — real calendar event execution (listEvents / createEvent / updateEvent / deleteEvent). Bound to a real provider by @lssm-tech/integration.opa-calendar-bridge; invoked only on the authorized + approval-satisfied confirm path.

Composition

import { composeOrganizationPlanningCore } from '@lssm-tech/module.organization-planning/composition';
import { createAllFakeAdapters } from '@lssm-tech/module.organization-planning/fake-adapters';

const adapters = createAllFakeAdapters();
const result = await composeOrganizationPlanningCore(packet, adapters);

OPA Manual Runtime

import { runOpaManualLoop } from '@lssm-tech/module.organization-planning/opa-runtime';

const result = runOpaManualLoop({
	runId: 'mission-relay-ready',
	workspaceId: 'workspace_hackathon_paris_ai',
	generatedAt: '2026-05-16T08:00:00.000Z',
	tasks,
	primaryPolicy,
	agenda,
	booking,
	externalMarkdown: true,
});

The runtime composes the @lssm-tech/lib.organization-planning-spec/opa availability/planner/agenda/booking/markdown primitives into the first manual loop: plan proposal, agenda proposal, booking proposal, Notion-ready markdown, audit payloads, required approvals, risk summary, and an immutable persisted OPA domain-command event. It is intentionally side-effect free: external calendar writes and client messages remain blocked until a host supplies reviewed production adapters.

OPA Domain Command Persistence

import { persistOpaDomainCommand } from '@lssm-tech/module.organization-planning/domain-command-persistence';

const workflow = persistOpaDomainCommand({
	command: {
		id: 'cmd-opa-booking-1',
		actionKind: 'propose_booking_slots',
		actorKind: 'agent',
		targetType: 'booking_proposal',
		targetId: 'booking-1',
		mode: 'draft',
		workspaceId: 'workspace_hackathon_paris_ai',
	},
	log: { events: [], version: 0 },
	occurredAt: '2026-05-16T08:00:00.000Z',
});

OPA command persistence records the domain command, target, runtime action contract, approval status, violations, and immutable event-log version. It does not write to a database or provider: managed/BYOK storage remains a host concern, and high-impact external-facing agenda, booking, markdown, and manual-loop commands persist approval packets instead of executing.

Flagship Fixtures

Three deterministic cross-module fixtures demonstrate end-to-end flows:

1. Revenue Booking to Delivery Kickoff — Sales booking through to CompanyOS work
2. Capacity-Aware Project Reschedule — Rescheduling with approval gates
3. Builder Customer Delivery Agenda — Builder delivery with customer communication

import { organizationPlanningFlagshipFixtures } from '@lssm-tech/module.organization-planning/flagship-fixture';

const result = await organizationPlanningFlagshipFixtures.revenueBookingToDeliveryKickoff();

Limite

• Imports from @lssm-tech/lib.organization-planning-spec only
• No provider SDKs, credentials, network calls, filesystem access, or queue operations
• No side effects by default — production execution requires caller-provided adapters
• Preserves policy gates and approval requirements

Compatibility note (manual-loop result): externalEffectsBlocked on the manual-loop result type widened from the literal true to boolean. It is now computed from isOpaExecutionAllowed(...), so on the authorized + approval-satisfied path it can report false (effects executed) while every unauthorized/unapproved path still reports true. This is behaviour-compatible for runtime consumers but a type-narrowing break for any code that relied on the literal true.

The meeting capability matrix now records CompanyOS mobile meeting-to-Work implementation evidence separately from signed-native acceptance. CompanyOS release qualification is independent of Pactena/hCircle parity; each other host retains its own gates. The matrix has 30 capabilities and zero qualified capabilities. Local tests and bundle exports do not substitute for provider/client/deployment acceptance, model evaluation, pilots or fresh onboarding.

Published browser conditions select the emitted browser artifacts alongside existing Node/Bun/type targets. Export keys and source behavior are preserved; this packaging metadata does not activate providers or grant execution authority.

Automation policy compatibility

resolveOpaAutomationPolicy remains available from the module root and ./resolve-automation-policy. Both forward to the canonical existing @lssm-tech/lib.organization-planning-spec/opa-automation-policy leaf. The deterministic rules and canonical-policy digest are unchanged. This module does not own a second evaluator or grant execution authority.