Source snapshot bcc79fcc · Declared package version 2.0.4. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
Provider-neutral operational controls for PersonalOS:
executable performance budgets backed by target/run/artifact-scoped evidence;
steady, burst, dependency-failure, and recovery capacity qualification;
staged canary promotion with plan-owned approver allowlists and quorum;
observed, time-bounded, no-data-loss rollback bound to the restored artifact;
dual-host-verified, content-addressed, expiring, minimized, audited, and revocable support access.
subject-owned support incidents with distinct person/support-agent transitions, opaque evidence references, accessible contact preferences, minimized status, appeal, reopen, and closure.
The module contains strict contracts and pure evaluators. It does not deploy services, collect telemetry, store evidence, authenticate support operators, or execute rollback. Support approval evidence is addressed by a canonical domain-separated request digest, activation evidence by a chained grant digest, and hosts must verify both references at every effects boundary. Hosts must also supply replayable, exactly scoped CI, canary, and restore evidence before production qualification.
Support incident V1 never accepts narrative, password, token, provider payload, or contact-detail fields. An incident carries only strict taxonomy plus opaque SHA-256 evidence references. Commands recompute their payload digest, prepare exact before/proposed state digests, and finalize only against an externally verified authority receipt bound to that transition. Exact subject/actor/revision/idempotency/time checks keep person-owned open/provide/appeal/reopen/close transitions separate from service-agent acknowledge/request/escalate/resolve transitions. The minimized projection omits summary, evidence, consent, receipt, and support-operator identifiers. Durable case custody, authenticated support staffing, notification delivery, accessible channel operations, incident drills, manual acceptance, and production canaries remain host qualification gates.
Comandos
sh
bun run lint:check
bun run typecheck
bun run test
bun run build
Declared capabilities.
Module Personal Operations
Fail-closed PersonalOS performance, capacity, release, rollback, and support controls.
Use it to
Adopt fail-closed personalos performance, capacity, release, rollback, and support controls
Requires
TypeScript
Choose another boundary when
The @lssm-tech/module.personal-operations package constraints do not match the target runtime or platform.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.
