==TODO== 1-3 sentences that answer the question at the top of the page. If the reader only reads this box, what do they leave knowing?
==TODO== the exact question or need this artifact answers. Restate the gator-question meta value in fuller form — the reader has already skimmed it in the header; this section gives it the space to breathe.
==TODO== one paragraph introducing the flow. For a procedure-visual, this is a numbered sequence. For a reference-explainer, this is sequential exposition that builds understanding.
==TODO== a neutral aside — related context that doesn't fit inline.
==TODO== something to watch out for — a subtle constraint or a gotcha.
==TODO== a hard failure mode — mis-step here breaks something visible.
==TODO== a verified outcome — checked, works, safe to rely on.
==TODO== the load-bearing "so what?" answer. If the reader skips this, they can act on the flow above but won't know when to reach for it or when to reach past it.
| Option | When to use | Trade-off | Status |
|---|---|---|---|
| ==TODO== | ==TODO== | ==TODO== | Recommended |
| ==TODO== | ==TODO== | ==TODO== | Alternate |
| ==TODO== | ==TODO== | ==TODO== | Not applicable |
| What breaks | Symptom | Fallback |
|---|---|---|
| ==TODO== | ==TODO== | ==TODO== |
| ==TODO== | ==TODO== | ==TODO== |
path/to/file.py — one-line description.
This document conforms to the gator-blueprint-html-v1
protocol (narrative template). See
.gator/procedures/authoring-html-artifacts.md for the
required metadata, doc classes, and status vocabulary.