# Founder Brief Curation

Use this workflow pack when the task matches `founder-brief-curation`.

## Goal

Draft and polish a founder-facing technical brief that reads like a shared paper, stays grounded in checked-in repo truth, and survives PDF export cleanly.

## Steps

1. Start with `docs-governance`, then narrow to `founder-brief-curation`.
2. Read the architecture references that actually support the brief before writing any shared claims.
3. Build the narrative in founder cadence: thesis, architecture shape, trust boundary, current truth, closing statement.
4. Expand shortforms on first use and remove internal drafting commentary from the shared artifact.
5. Keep references hyperlinked with shareable GitHub `blob/main` URLs and move low-signal source inventory out of the main narrative.
6. Use a compact figure system and verify the actual rendered PDF pages before calling the work done.
7. If the figures feel asymmetric, fix spacing and geometry before shrinking type.
8. Hand off to subsystem skills when the artifact reveals source-truth gaps rather than compensating in the brief.

## Common Drift Risks

1. writing an explainer brochure instead of a paper-style technical brief
2. treating route maps as architecture narrative
3. leaving unexpanded acronyms in a first-read document
4. trusting source HTML instead of verifying the rendered PDF
5. letting captions, arrows, or labels become denser than the surrounding document
