Skip to content

P.O.W.E.R. Control Plane

P.O.W.E.R. is a local-first control plane for verifiable AI-assisted software engineering and Linux operations. It combines an authoritative execution runtime, broker-mediated tool governance, proof-carrying handoffs, and a structured knowledge substrate (Second Brain with P.A.R.A., validated OKF frontmatter, hierarchical indexing, and hybrid retrieval).

Release Status: Current stable release is v3.7.13 (maintained on release/3.7). Active development line on main is targeted toward POWER 3.8. See ADR-0007: North-Star Control Plane Architecture.

Start here

These guides define the supported release artifact contracts, use an isolated virtual environment, and include acceptance checks. Publication is complete only when the signed tag, wheel, source archive, SBOM, and release receipts can be read back from GitHub. The migration guides keep the source immutable, reconcile every file by manifest and hash, and make cutover reversible.

Executable contract

  • Python 3.13 or 3.14.
  • 27 top-level CLI commands; see the CLI reference.
  • 21 MCP tools; see the MCP server reference.
  • auto is the default search profile: verified dense when ready, otherwise labelled FTS; semantic and reranked are explicit opt-ins.
  • The generated root index and MCP sub-index operations cover the canonical P.A.R.A. directories. Arbitrary source layouts must be mapped during migration.
  • The canonical dense backend is BAAI/bge-m3; model-backed checks download large artifacts. FTS5 works without model downloads.

Minimal quick start

Follow the clean-install guide. It downloads the exact wheel and power-native-requirements.txt, installs dependencies with --require-hashes, and installs the framework artifact with --no-deps before running the vault lifecycle commands. Do not install the wheel alone with floating dependency resolution.

On Windows, use the dedicated PowerShell guide rather than translating these POSIX commands.

Claims and evidence

Historical vault measurements and synthetic benchmarks are useful diagnostics, not universal performance guarantees. The POWER 3.1 trust-release baseline defines the evidence boundary. The hierarchical-index reports are explicitly preserved as v1.6 historical snapshots.

More documentation

GPLv3 — Built in Ukraine ⚡