brse-client-reportlisted

# BrSE Client Report ## Overview Draft or polish concise Japanese customer-facing reports that are accurate, business-style, and action-oriented. **Core principle:** Conclusion first. Every sentence must support the conclusion, customer impact, risk, decision needed, or next action — otherwise delete it. ## When To Use - Daily or weekly status update to a Japanese customer. - Investigation result, impact report, or risk note for stakeholder review. - Customer question reply that must be ready for direct forwarding. - A developer report has been reviewed (`brse-report-reviewer`) and the BrSE must convert it into customer-facing JP. ## When NOT To Use - Internal team standup notes — use `brse-offshore-sync` instead. - Developer-to-developer technical writeup — keep working language. - Report substance is still weak — run `brse-report-reviewer` first; do not polish a bad report into a more convincing bad report. ## Workflow 1. Decide the report type: - daily status - investigation result - impact report - QA result - customer question reply - release risk note 2. Put the conclusion first. 3. State evidence only at the level useful to the customer. 4. Filter the content by customer value: decision needed, user/business impact, current status, remaining risk, or next action. Remove dev-internal process detail that does not change customer understanding. 5. Separate: - confirmed facts - current action - remaining risk - customer decision/reque