Optional Sidecars and Agent Autonomy

Diagnostics And Agent Autonomy

PIC includes optional diagnostic reports that make agent work easier to exchange, inspect, and explain. A diagnostic report is not a gate and not an approval system.

The main rule is simple:

core agent checks first
diagnostic reports second
no hidden approval state
no automatic execution

Core Path Stays First

These commands are the normal first path for agents, CI jobs, and local users:

pic agent check --compact --text "Candidate packet: preserve residuals." --profile development
pic phase plan --compact --text "Candidate packet: preserve residuals." --profile development
pic agent accelerate --compact --text "Candidate packet: preserve residuals." --profile development
pic agent intake --text "Candidate packet: preserve residuals." --profile development

They do not require:

• operator adoption state;
• separate approval state;
• sidecar files;
• local TeX sources;
• a source checkout.

Autonomy Audit

Use this command to check whether the core agent workflow is blocked by adoption state, approval state, shell execution, or missing compact mode:

pic agent autonomy-audit --profile development --format json
pic agent autonomy-audit --profile development --format markdown --language ja

The report is diagnostic-only.

Canonical Readiness

Use this command to inspect the installed package's implementation surface:

pic audit canonical-readiness --profile development --format json

The readiness boundary keeps external paper-level obligations visible as residual future work. It does not convert those obligations into settlement.

Phase Ecology Lab Diagnostics

Use Phase Lab when the question is about a window of reports rather than one output:

pic demo bootstrap --output-dir pic-demo
pic phase lab init --output-dir pic-demo/phase-lab
pic phase lab ingest --store pic-demo/phase-lab --report pic-demo/phase_lab_runtime_report.json
pic phase lab graph --store pic-demo/phase-lab
pic phase lab closure --store pic-demo/phase-lab
pic phase lab executable-paths --store pic-demo/phase-lab

These reports do not execute embedded command text or approve action.

CCR And TRC Diagnostics

Use v0.7.0 CCR interop when a runtime needs data-only handoff records:

pic phase plan --compact --emit ccr-tasks --output tasks.jsonl
pic phase gap --compact --emit ccr-residuals --output residuals.jsonl

Use TRC operation-readiness checks when an operation candidate must stay explicit before review:

pic trc trace-normalize --input trace.json --output trace_nf.json
pic trc trace-check --trace trace_nf.json --output trace_check.json
pic trc operation-gate --trace trace_nf.json --output operation_gate.json

These commands emit diagnostics and handoff data. They do not authorize provider calls or real-world effects.

Sidecars Still Exist

Some older workflows use the word sidecar for extra reports such as adoption handoff, packet exchange, dashboards, and benchmark reports.

In v0.7.0, the interpretation is the same:

• sidecars are inert reports;
• they help inspection;
• they do not grant authority;
• they do not make settled=true;
• they do not promote candidates by themselves.

Agent Autonomy Boundary

PIC can help an agent decide what should be checked next. It cannot decide that the host runtime should run a tool, mutate a repository, install a package, send a message, use a credential, or call the network.

The host environment's permissions remain authoritative.