Pi integration · alpha

Pi Operator Extension

Operator workflows inside Pi, with the control plane kept separate.

A Pi front end for a separately installed Operator control plane. The extension is one integration, not the whole product.

How the integration works

Pi is the interaction surface. The extension routes supported commands to the separate Operator control plane, then shows the result in Pi.

01 · Pi session

Choose a workflow

/op:tasks /op:use /op:claim /op:evidence
02 · Pi extension

Route and confirm

  • Calls the supported Operator workflow
  • Requests confirmation before writes
  • Returns a readable result to Pi
03 · Operator

Record the work

The separate control plane manages task, claim, evidence, and verification records in its local ledger.

Read-only inspection is distinct from confirmed, state-changing actions.

Conceptual workflow diagram, not a screenshot of a live Pi session.

What it is

The Pi Operator extension adds slash-command workflows for working with Operator from Pi. It connects to a separate Operator checkout and local ledger; it does not bundle the Python control plane or ledger data.

Operator remains usable independently of Pi. The extension is optional, and installing it does not make Operator a Bulkhead τ dependency.

View the interactive Pi extension project board for its tracked tasks, issues, and project map.

Core workflows

Inspect

Use /op:doctor, /op:status, and /op:tasks to inspect local ledger state and consistency.

Work with a task

Select a task, then use confirmed shortcuts for claims, evidence, and handoffs. Writes are shown for confirmation before they are recorded.

Optional workflows

Delegation, supervisor review, PBC authoring, and crystal workflows are optional. Several are experimental and need additional local configuration or tools.

Requirements and status

  • The control plane is a separate checkout with a local Operator ledger.
  • Core workflows require Python 3.12 or later and PyYAML.
  • The extension documentation names Pi 0.87.1 as a compatibility target observed during static preparation. It is not a validated support matrix.
  • The public source repository contains the v0.1.0-alpha.1 Git tag. GitHub lists the associated prerelease as a draft, not a published release. Some preparation docs still describe tag approval as pending, so check the source tag and GitHub Releases page for current status before installation.

Single-user Operator verification is advisory, not an independent identity-isolated review. Additional identity enforcement requires separate configuration.

Public source and documentation