Optional Reports and Markdown

Optional Reports And Markdown

Some commands can produce Markdown reports for humans.

JSON remains the machine-readable contract. Markdown is for reading, review, and handoff.

Adoption Reports

npx pic-ts adoption request --format markdown --language en --output adoption-request.md
npx pic-ts adoption request --format markdown --language ja --output adoption-request-ja.md

Adoption reports do not approve work, install packages, or make the result settled.

Phase Reports

npx pic-ts phase dashboard --format markdown --output phase-dashboard.md
npx pic-ts phase observe --format markdown --output phase-observe.md

These reports describe workflow state and bottlenecks. They do not prove real ASI or execute phase actions.

CCR JSONL Reports

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

These are machine-readable handoff records, not Markdown summaries. They remain candidate-only until a downstream runtime checks them.

Autonomy Audit

npx pic-ts agent autonomy-audit --profile development --format markdown --language en

The audit explains what the agent can inspect locally and what remains outside the package's authority.

Safe Reading Rule

Markdown reports are explanations. JSON and JSONL remain the machine-readable contracts. Always preserve blockers, residuals, and missing obligations.