@lssm-tech/module.agent-fleet
Agent fleet, tool-registry, and governed execution surfaces. The package also exports two distinct installable Feature Hub profiles:
./agent-system for local fleet, tool, memory, lease, and audit adapters../agent-network for cross-system delegation and federation.
Federation verification uses RFC 8785 canonical UTF-8 bytes with the signature omitted, intersects every signed/requested/current/exposed scope and ceiling, and fails closed through injected trust, key, replay, revocation, target-local policy, and audit ports. Replay is consumed before target-local authorization; over-scoped requests do not reach local policy. A local allow carrying unresolved obligations remains denied, so a verification result cannot silently discard target controls.
External Markdown migration preview
previewAgentMarkdownMigration validates the restricted archive and exact agent scope, then projects explicit target mappings as new, identical or conflicting. Memory requires review by its owning PersonalOS/CompanyOS service; skill content requires independent evaluation. The projection contains hashes and references, not imported text. It neither writes files nor installs or activates content. Product import UI, durable owner proposals, schedule/channel translation and live vendor migration qualification remain separate work.
proposeAgentMarkdownMemory translates an explicitly selected memory file into the existing AgentMemoryProposalArtifactV1. It binds source/archive/content digests, exact scope, host-selected owner and policy references, and an optional correction target/revision. Imported contents are not embedded in the proposal or interpreted as authority. The host must resolve contentRef in restricted storage; PersonalOS or CompanyOS must verify consent, retention and authority before persistence.
submitAgentMemoryImportProposal composes the existing agent protocol artifact store with host-provided submission authorization and restricted-content verification. It appends at revision zero, verifies exact readback, and reconciles lost acknowledgements without repeating the append in the same call. Unverified writes remain indeterminate. This persists review candidates only; memory-owner promotion, consent and runtime activation stay separate. Production hosts must provide the durable scoped adapter and current principal authorization.
AgentMigrationReviewPanel is a controlled reusable presentation for console or embedded hosts. Pass a validated preview, localized labels, selected target refs, pending/error state and host permission projection. It allows selection only for new mappings and sends the archive digest plus selected target refs to the host. The host must revalidate all input and call the authorized submission service; client-side canSubmit never grants permission. Conflicts require mapping resolution outside this panel. Product-route wiring and browser/visual qualification are pending.
Migration submission has one monotonic I/O budget (default ten seconds, configurable from one millisecond to sixty seconds). All authorization, content verification, artifact reads/writes and record validation share it. Preflight timeout starts no write; an unsettled append remains indeterminate. The generic store interface cannot forcibly cancel a provider request, so explicit retries must reconcile the same immutable proposal identity rather than creating another proposal.
Submission authorizes the actor before restricted-content lookup and rechecks current authority immediately before a new artifact append. Revocation during lookup therefore blocks the write; it does not rely solely on an earlier decision.
executeMemoryImportOperation is the handler adapter for
agent.memory.import.submit. A host-provided Runtime Node verifier must return current signed-operation bindings matching the exact request, actor, scope, work-order, archive/proposal digests and idempotency key. Restricted artifacts are loaded only after that check; authority is rechecked before submission. The adapter never creates a signature, claim, fence or promotion decision. Production verifier composition, handler registration and HTTP/UI route wiring remain required.
createMemoryImportRuntimeVerifier composes the canonical V3 order validator, Connect dispatch verifier and durable operation reader. The signed payload binds the actor, agent scope and complete request; the operation must retain the same running claim/attempt/fence and request digest after verification. Trusted time is rechecked for expiry. Production key verification still belongs to Connect; this adapter neither implements a signing authority nor accepts bare digest equality as signature proof. Hosts must provide the real trusted readers and verifier.
createMemoryImportOperationRegistry returns a canonical operation registry with the import command and handler bound. Normal registry input/output and permission checks apply. The handler additionally binds the authenticated context user and tenant to the verified Runtime Node actor/scope, preventing a transport caller from selecting another identity. Hosts still supply the production verifier and store adapters and must register the registry with their authenticated transport.
Memory import registry callers must supply a server-authenticated workspaceId
alongside actor and physical tenant. Both the request and verified Runtime Node operation must match that workspace; a tenant-wide session alone cannot import.
Founder operations workflows (./core)
These additive surfaces are headless and provider-neutral. Hosts inject durable stores, provider control, notification, authority and Work-creation ports. Nothing here executes consequential effects on its own.
coding-supervision-v1 — SupervisedCodingSessionService binds a coding agent run to a canonical Work item (UUIDv7), repository/worktree/branch, path leases and an exact task digest. Questions, reviews and CI waits are persisted before notification; answers must match the wait id, expected revision and current owner epoch and pass current authority. Delivery is pending →
dispatching → delivered; after a restart sweep() dispatches never-sent answers once and reconciles in-flight ones by provider lookup. Uncertain provider, delivery and cancellation outcomes stay explicit and are escalated, never retried blindly. Wait deadlines, wall-clock/compute/cost budgets and stalls escalate once per trigger as a FounderProposalV1 (proposed Work item); onExhausted: 'cancel_and_escalate' additionally requests cancellation. Completion needs every declared artifact; acceptance needs the required verification receipts. External sessions are unqualified until an identity proof is supplied.- Proactive proposals (FW-013) —
ProactiveProposalService accepts explained candidates (trigger, evidence, expected value, affected scope, next action), suppresses duplicates and repeatedly dismissed rules, keeps paused or archived scopes quiet unless an obligation remains, and defers routine items, quiet hours and rate-limited items to the digest. Critical blockers may bypass quiet hours and the rate limit per policy. Accepting returns a Work draft only.
workflow-improvement-v1 — WorkflowImprovementService and
createWorkflowImprovementAdapter route knowledge corrections to Company Intelligence and send procedure feedback through
GovernedAiImprovementRuntimeV2 (@lssm-tech/lib.ai-agent/improvement-loop) with a frozen success criterion, replay plus independent held-out evaluation, canary observation and rollback. Failed evaluations are rejected; promotion requires an explicit human approval; self-granted authority and model-route drift fail closed.usecase-proposal-v1 — reviewUseCaseProposals turns recurring observed work into at most maxProposals proposals with past examples, frequency, benefit, needed access (granted: false), operating cost, smallest trial, stop condition and acceptance hypothesis, at the agreed cadence. Nothing is activated.
Reference stores (InMemorySupervisedCodingSessionStore,
InMemoryProactiveProposalLedger, InMemoryWorkflowImprovementBriefStore) are deterministic fixtures, not production persistence. For production, pass
supervisedCodingSessionCodecV1, proactiveLedgerRecordCodecV1 and
workflowImprovementBriefCodecV1 to the matching Postgres stores in
@lssm-tech/integration.agent-durable-store/postgres. The codecs validate every persisted payload. One shared contract suite (src/core/store-contracts/) runs against both the in-memory and the PGlite-backed Postgres implementations.
createCommunicationQuietHoursInterruptionPort binds proactive quiet hours to CommunicationOS isWithinCommunicationQuietHoursV1. A missing preference means there is no quiet window. A preference that cannot be read fails toward quiet.
