visual-brief

# Visual Brief ## Start with a Visible Acknowledgment Before a long setup or implementation block, send the human a short visible acknowledgment in the current conversation. Say what you are starting and where you will publish the result. Do this before creating files or running lengthy commands. The same rule applies to a substantial request sent through the page. Answer the thread first with one short confirmation. Publish the completed work later. If the request takes only a moment, answer it directly without a separate acknowledgment. ## Use the Page as the Report The human reads the page. The chat only points to it. Put the complete report on the page, including conclusions, limits, reasoning, and evidence. Do not repeat the report in the terminal response. A visual brief is useful for substantial implementation results, design reports, investigations, reviews, and decision sets. Trivial progress and small fixes belong in ordinary conversation. An explicit request for a visual brief overrides this threshold. The page supports layers: - `glance` states one plain claim. - `explanation` gives the reasoning in full. - `forensics` holds raw evidence, file paths, output, errors, and numbers. - `tables` hold repeated or comparable values. Keep each prose field as a flowing thought. Several distinct facts should be separate items, table rows, or forensic notes. Do not cram numbered lists into `glance`, `explanation`, or a conversation turn. ## Publish One Complete Brie...