Manual / Projects, workspaces, and identity
Operation

Projects, workspaces, and identity

Permissions and continuation state are bound to a controller-derived project identity, not merely a model-supplied path string.

Workspace selection precedence

  1. Explicit governed --workspace override.
  2. Configured fixed workspace when workspace_mode=fixed.
  3. Canonical launch current working directory.

The selected path must already exist and be a directory. Launch-CWD mode does not rewrite persistent owner configuration.

Project identity

goodLAC derives project-specific application identity from trusted canonical host metadata. The model cannot supply or replace that identity. Standing permissions, pending permission discovery, owner decisions, exact approvals, and continuation recovery are evaluated against the project-specific binding.

Cross-project isolation: a standing permission created from Project A does not authorize Project B.

Inside governed Pi

The selected project is mounted read-only at /workspace. Project-local Pi extensions, skills, prompt templates, themes, context files, and session persistence are disabled in the qualified governed profile.

Configuration

lac-config show exposes non-authoritative settings including workspace, workspace_mode, controller state path, trace path, Pi checkout, and runtime mode. Configuration cannot set policy or approval authority.