formal-report-openaccp

Formal Report OpenACCP

Report current state, completed work, unverified claims, blockers, next actions, authority limits, and basis references.

Use owner-readable language. Do not call validator pass semantic approval or reviewer recommendation final acceptance.

Every formal report must carry a Response ID, not Report ID. It must also include a Response log path: line. If there is no persisted log file, write Response log path: chat reply or the project-local status artifact path.

Use the user's preferred language when it is known. If the language is not known, keep the language consistent with the user's current conversation.

When the preferred language is Chinese, use Chinese as the main language for headings, summaries, table cells, evidence explanations, and next actions. Keep English only for stable technical terms and exact names such as Primary, Frontier, worker, reviewer, handoff, validator, source pack, Prompt ID, Response ID, CARD, task-card, B0/B1/B2/B3, CI, CLI, JSON, schema, exact file names, or project-specific product terms. Do not write long English sentences or paragraphs in a Chinese report.

Chat Table Fit Rule

Formal reports are often rendered in narrow chat panes. Keep the table readable:

• Use short first-column labels. Generic reports may use Changed, Progress, Gate, Area, Goal, Gaps, Next.
• Chinese post-install and generic startup reports should use 做了什么, 总体进度, 验证, 范围, 目标, 缺口, 下一步.
• Primary Chinese reports should use 做了什么, 总体进度, Frontier, 目标, 缺口, 下一步.
• Frontier Chinese reports should use 做了什么, 总体进度, Lane, 目标, 缺口, 下一步.
• Use 类型和状态 as the Chinese first-column header. It avoids the / line-break point and keeps the table pure Markdown.
• Keep each table cell to a short summary.
• Do not use free-form row labels such as 安装, Skill, CLI, 项目, 状态, What changed, Lane or area, Next step, Validation, or Checkpoint.
• Do not put long paths, URLs, commit hashes, full commands, validation logs, executable paths, local install paths, or long inline-code snippets inside table cells.
• Do not include PowerShell blocks, bash blocks, shell command blocks, command lists, or command dumps anywhere in a chat formal report. Validation evidence should be a short status only, such as 验证通过 or Validation passed.
• Put only short evidence notes after the table. Chinese reports use 依据与验证; English reports use Evidence and Validation.
• Always use the exact table header | 类型和状态 | 内容 | for Chinese reports or | Item/Status | Content | for English reports. Legacy slash headers, short Chinese headers, mixed status headers, field/content headers, and custom headers are invalid.
• Do not use <nobr>, HTML wrappers, invisible characters, or spacing tricks in formal-report tables.
• Keep validation, gate, or checkpoint-like information in the 验证 / Gate row for generic reports or in the evidence section outside the table. The table row set excludes Checkpoint.