Target — Reports

[!warning] Mostly open questions. Decisions so far are under Decided at the end. Per the NEVER GUESS rule, every other line below is a question only Talbot can answer, not a placeholder for an agent to fill in. Q4 and Q5 were answered on 2026-09-24. For everything else, Design-Principles is the authority for this target.

Shared questions (also in Print and Decks)

Print/export color authority. The brand anchors are OKLCH and screen-gamut; no CMYK or spot mapping exists. What governs a report printed or exported to PDF?
Fixed-page type scale. The shipped scale is fluid clamp() keyed to viewport width. A report page is a fixed measure. Is there a fixed-page scale?

Report-specific questions

Who is the audience — client, internal, advisor, or regulator? Each implies a different claims discipline (see Voice).
What is the target length, and does F.A.S.T.’s Fast imply a summary-first structure with detail behind it — the print analogue of “See all”?
Delivery form. Is a report a published HTML artifact, a PDF, or an Astro route? This decides whether tokens apply and whether it can be interactive.
Does the Highest Impact Analysis (Design-Principles §4) have a canonical report form — a table, a tornado chart, or a ranked list?
What disclaimer and data-source attribution is mandatory on a report carrying investment figures?
Is there a standard cover, header/footer, and pagination convention?
Does an existing artifact serve as the reference — the investment-analysis dashboard is the closest thing that ships today.

When these get filled in

Borrow before building (Talbot, 2026-08-29). Other artifacts get design guidelines when a real deliverable needs them, and the first move is to find an existing framework, template, or skill that already does this well — not to author one from scratch. Answer the questions above against a borrowed baseline rather than in the abstract.

Decided (Talbot, 2026-09-24)

Answers to Q4 and Q5 above, from the Market-timing-refined-analysis task. The other questions stay open.

Q4, summary-first: yes, as a Brief / Full toggle.

A “Details: Brief / Full” pill sits at the top and bottom of the page. Brief is the default and hides 70%+ of the content, keeping only the BIGGEST Rocks.
Show a reading-time estimate for each mode next to the pill. Show the times only; the method belongs in the project README, not the page.
Open with 4–8 bullet findings: the conclusions, with numbers.
Follow with a minimal Context section (80/20) that includes any analogy the report relies on. A “More…” link reveals less critical background and the terminology definitions.
Write for outsiders: no references to private notes or personal circumstances.

Q5, delivery form: a self-contained HTML artifact.

Save it to ~/artifacts/ (\\wsl$\Ubuntu-24.04\home\ta\artifacts\).
Register it in Core/IT/Utils/Custom/DASHBOARD.md.
Public deployment is opt-in only: see web-deploy-artifacts-publish.

Added later in the same task:

Keep Brief to about 4 minutes (Talbot, 2026-09-25). When new content goes into Brief, move lower-value material to Full to hold the time.
Show an “Updated YYYY-MM-DD” date, restamped on every rebuild (Talbot, 2026-09-28: “when modified, dates should be updated”). Use the build date, not the date the underlying data was generated.
Link sibling reports with relative links (e.g. investing-timing-solution.html), so they work locally and when uploaded to one folder on the site (Talbot, 2026-09-28).
Reading bar (Talbot, 2026-09-28, “Tailored UX tool”): the top Details bar is sticky and carries a Contents button (popover on phones and tablets; a persistent left sidebar at 1400 px and wider, highlighting the section in view). Labels are each section’s short eyebrow, or data-toc when that is too long. Contents lists only what the current Brief/Full mode shows. The reading-time estimate counts SVG graphics as charts.
Show every period, not one (Talbot, 2026-09-28): any strategy result from a single start date must sit next to its distribution over every start date: Benefit frequency (ahead / identical / behind, as a gauge with counts) and Benefit amount (best, 90th pct, typical, 10th pct, worst; $ on the left in 2 significant figures, % on the right), plus a start-year strip in Full. Pattern from Talbot’s SD Visualizer design (iteration 24).

Reference implementation: ~/projects/cape-timing/report/base.js (Brief/Full plus the chart period view) and report/base.css.