LPOS v4.8.1

LPOS v4 is a single, integrated agent operating-system distribution. The operating specification, deterministic control plane, capability registry, executable schemas, Standing Operation workflows, adapters, database migrations, tests, installer, and CLI ship together under one version.

The packaged v4 specification is loaded by the engine automatically and is the specification the v4 runtime enforces.

LPOS v4.8.0 adds bounded specialist-led managed execution while preserving the frozen 4.7 expert capability corpus: 103 specialists across 20 guilds, 122 craft standards, and 103 behavioral admission suites. Product Studio is not included and remains deferred.

• A small always-loaded Chip kernel and lazy component retrieval.
• One-Principal authority and explicit materiality policy.
• Typed TaskEnvelope, InterpretationContract, ArtifactSpecification, ReviewEnvelope, ActionPlan, ApprovalGrant, EvidenceRecord, DecisionRecord, and CompletionReport objects.
• Deterministic task and action state machines.
• Capability-first routing across all 103 LPOS specialists by their canonical IDs.
• Bounded managed execution with exact worktree/head preflight, risk-tier tool allowlists, deterministic checks, strict receipts, and hash-bound independent review.
• Five-gate material-artifact review with a fresh isolated review context.
• Exact-action approval bound to the canonical SHA-256 action payload.
• Verified Principal identities, expiry, replay protection, and one-time approval consumption.
• Transactional SQLite state, append-only events, optimistic concurrency, checksummed migrations, idempotency, and operation leases.
• Machine-readable workflows for SO-001 through SO-029.
• Seventy fixed benchmark fixtures covering every specialist and Standing Operation.
• A provider-neutral JSON subprocess protocol for model hosts.
• A record-only consequential-action adapter and sandboxed local-file adapter for safe installation tests.
• Cross-platform offline installation and a no-side-effect end-to-end verification flow.
• Nine command-backed Continuous Operational Excellence gates, a complete immutable application verifier, tamper-evident SQLite evidence, daily audits, private APIs, verified report delivery, and an authenticated operational-health dashboard.

Requirements: Python 3.11 or later.

Extract the release ZIP into a new directory, then run one installer from that directory.

bash INSTALL.sh

.\INSTALL.ps1

python install.py

The installer verifies the release manifest, creates .venv, installs the bundled wheel offline, initializes ~/.local/state/lpos/lpos.db by default, validates the packaged schemas, runs lpos doctor, and executes the record-only local verification flow. Use --state-root or LPOS_STATE_ROOT to select another approved mutable state directory.

macOS or Linux:

.venv/bin/lpos version
.venv/bin/lpos doctor --db ~/.local/state/lpos/lpos.db
.venv/bin/lpos list-specialists
.venv/bin/lpos list-workflows
.venv/bin/lpos list-benchmarks
.venv/bin/lpos evals
.venv/bin/lpos coe stage --repo . --release-root /tmp/lpos-4.8.1-stage
.venv/bin/lpos coe release-gate --repo . --release-root /tmp/lpos-4.8.1-stage --state-root ~/.hermes/state/chip-service
COE_OPERATOR_TOKEN=<secure-value> .venv/bin/lpos coe serve --state-root ~/.hermes/state/chip-service

Windows:

.\.venv\Scripts\lpos.exe version
.\.venv\Scripts\lpos.exe doctor --db state\lpos.db

The direct module form also works:

.venv/bin/python -m lpos_engine --help

The bundled deterministic model adapters exist for verification and development. Connect a real model host through SubprocessModelAdapter, which exchanges one JSON object on standard input and one JSON object on standard output without invoking a shell. See docs/ADAPTER-PROTOCOL.md and examples/example_model_host.py.

Live email, publishing, deployment, purchase, deletion, and other consequential adapters are not silently enabled. A deployment must provide authenticated adapters with least privilege, idempotency, reconciliation, and deployment-specific tests. Until then, the bundled consequential-action adapter records an approved action without performing it.

  src/lpos_engine/spec/          Canonical v4 operating specification
  schemas/       Executable JSON Schemas
  workflows/     SO-001 through SO-029 workflow definitions
  evals/         70 fixed benchmark fixtures and evaluator
  config/        103-specialist capability registry
  sql/           Checksummed database migrations
  adapters/      Model and action adapter boundaries
  coe*.py        COE contracts, verifier, evidence store, gates, controller, APIs, and reports
  *.py           Deterministic control-plane implementation
schemas/         Human-visible synchronized schema set
config/          Human-visible synchronized capability registry
tests/           Runtime, policy, security, packaging, and integration tests
docs/            Architecture, security, adapter, and operating documentation
examples/        Model-host and workflow examples

python -m venv .venv
. .venv/bin/activate
python -m pip install -e '.[dev]'
python -m pytest
lpos validate-schemas
lpos doctor

The authoritative product release identity is release/release.json. RELEASE.json, pyproject.toml, the installed package, the specification kernel, workflow catalog, capability registry, and release manifests are verified mirrors.