Pi extension: documented feature inventory

Supplementary technical notes · frozen source snapshot · not a status dashboard

Supplementary, document-based inventory. These 17 rows summarize what the pinned PBC says about planned Pi extension features. They do not show live task status. “Implemented” labels describe documentation and do not establish independent acceptance; use the main page for the dated board snapshot.

Frozen source commit: 85379b888a57bf99e3c37c62d8dfc4a0d8be636d. The source files are read directly from that commit, not from the working tree.

Inventory source: owners-manual/pbc/appendix-pi-operator-extension.pbc.md, Candidate Reconciliation. PBC SHA-256: 78a31947001d5bab2e456de41490f619200ffb5d34796b826fd637ad907c6941.

Board snapshot

The main project board shows the September 16, 2026 snapshot. Its task statuses and counts are historical, not current status. A separate archive copy is retained for reference.

Documented implementation and acceptance

Status and basis below are copied from source documentation. “Implemented”, “local task verified”, and owner-confirmed behavior do not imply independent acceptance. Missing acceptance information is unknown. Historical feature IDs are not an active-work queue. No runtime tests were run to establish the statements below.

IDDocumented statusDocumented basis / remaining scope
POE-FUT-001–002Implemented; not independently accepted`/pbc:define` and `/pbc:feature` edit structured drafts, validate a temporary candidate, preview and confirm an append-only `pbc:grounding` proposal. Existing rules are unchanged; no ratification.
POE-FUT-003Not implementedNo lifecycle wizard.
POE-FUT-004Not implementedSupervisor review remains scoped to one named claim.
POE-FUT-005Partially implemented`client.ts` exports `CarrierNeutralOperatorClient`; `selftest.ts` tests argv and lifecycle retries. `adapters/opencode/` adds a core TUI consumer with mock-API and disposable-ledger tests and a live 1.18.22 check of all 13 core commands; optional workflows and Claude/MCP consumers remain.
POE-FUT-006Implemented; not independently accepted`/op:targets` lists/adds/edits/removes target configuration with field prompts and confirmed preview. New/edited targets require a registered harness and resolved model; task routing and reviewer authority are untouched.
POE-FUT-007Prompt implemented; owner-confirmed popup successThe owner confirms the GUI popup worked; reviewer execution then failed on provider authentication. The popup itself does not set status, but launched code has verifier permissions. Its authorization dialog now shows the complete shell-quoted argv; only compact transcript reports abbreviate it. Read-only inspection of `.operator/tasks/review-delegate-gui-auth-popup.yaml` during release preparation still shows `assigned` with empty claims/evidence; this historical task is not closed by that observation.
POE-FUT-008Implemented`/op:roadmap` reports ladder, current task, issues and futures; loader/handler selftests cover it. No new enhancement scope inferred.
POE-FUT-009Implemented; live privileged acceptance pending`/op:verify-run` (labeled `[experimental]`; its dialog discloses that author-writable code runs under the verifier account) reuses GUI askpass, invokes a distinct-UID helper with confirmed input hashes (a freshness check, not code signing), retains private logs, and the helper itself attaches only after a reviewer decision file approves. The helper, `operator` and the verification command come from the author-writable checkout and run with the verifier's permissions and credentials, so author-controlled code can still write verifier evidence without a decision; a resulting `uid_isolated` status shows a distinct UID launched the run, not independence from author code. No live sudo/model review is established by automated tests; see `docs/specs/VERIFY_RUN_SPEC.md`.
POE-FUT-010Implemented; local task verified`/op:next-steps` exists; local `pi-operator-extension-next-steps` records verified status and claim-0157.
POE-FUT-011Implemented`/op:project` and `/op:roadmap --project`.
POE-FUT-012ImplementedCross-project installer and explicit ledger contract; consumer project trust remains a human step.
POE-FUT-013Closed as guidance-onlyOptional `/op:next-steps` modes; do not add `/op:mode` or a new gate.
POE-FUT-014Implemented; not independently accepted`/pbc:validate [path]` uses the pinned Route C wrapper with fixed argv; no upstream `--profile`.
POE-FUT-015Implemented; not independently accepted`/op:crystal` captures reviewed current-session notes via installed crystallize 0.1.16; `/op:crystal-attach [path]` and `/op:crystal-import [path]` wrap draft-only backends. Chooser only when attach/import omit a path. No automatic download or attachment.
POE-FUT-016Not implemented; idea recorded 2026-09-23Opt-in crystal prompt near a context threshold (suggested 90%) before compaction. Depends on post-release crystal validation and a Pi compaction/threshold hook.
POE-FUT-017Minimal slice implemented 2026-09-28 (freeze, reviewed attempt log, crystal, direction handback); supervisor launch not implemented`/op:life-boat` doom-loop escape. Charter in `appendix-op-life-boat.pbc.md`; needs crystal capture validation and a supervisor-role decision first.
POE-FUT-018Not implemented; idea recorded 2026-09-23Generalize the static boards beyond `pi-operator-extension`; optionally an `./operator` board command reading through `doctor`-level checks (Operator core change). Hub excluded.

This is supporting documentation, not a replacement for the board or a live project-status feed.