Governed Pi usage

The installed pi command enters the goodLAC-governed Pi profile by default.

First launch

Change into the project directory you want to govern, then launch:

cd /path/to/your/project
pi

With the default workspace_mode=launch-cwd, the canonical launch directory becomes the session project. A fixed workspace can be configured explicitly by the owner.

Model-facing effect surface

• lac_fs_read
• lac_fs_create
• lac_fs_replace
• lac_shell_exec

Stock Pi built-in tools are disabled in the governed profile. The selected project is mounted read-only at /workspace in the Pi sandbox; consequential writes and shell effects still go through controller-backed tools.

Sandbox boundary

The qualified native Pi path runs inside Bubblewrap with host network unavailable to the governed Pi process. Owner administration sockets, service credentials, project-local extensions/resources, and general host filesystem/process authority are not exposed to the model process.

Dangerous bypass

pi --dangerously-bypass-lac ...

Continuation commands

The trusted goodLAC Pi extension adds owner-visible commands for durable blocked-workflow recovery:

/lac-continuations
/lac-resume <continuation_id>

Startup may report recoverable continuation state, but restart never auto-dispatches an effect.