Market timing reports: world-class rewrite with editable Markdown source

Background

• Spun out of Market-timing-refined-analysis at its close (round 14, 2026-09-28). Talbot chose “Red Team first, then rewrite”, so the rewrite reflects the corrected findings and the exit-rule decision, and isn’t done twice.
• Reports: ~/artifacts/investing-market-timing.html (Extreme Market Valuations: Investor Risks, Costs, and a Practical Solution) and ~/artifacts/investing-timing-solution.html (A Practical Behavioural Solution for High Markets). Online: https://claude.ai/artifact/BfA8jRojdFHtLArKBj3U8w · https://claude.ai/artifact/4xd4oHHcwSEwCiJ6PqhrKB. Built by ~/projects/cape-timing (scripts/build_report.py, scripts/build_vt_report.py; README: /home/ta/projects/cape-timing/README.md · \\wsl$\Ubuntu-24.04\home\ta\projects\cape-timing\README.md).
• Talbot’s brief for this rewrite (round 14, verbatim):

  “This artifact started out as an internal document that progressed through many iterations to get closer to the truth, and refined the real value that is relevant to high stock market valuations and a possible solution. Then I wanted it to become available to a few others externally, for feedback.” “Hypothesis is not even stated. The context, flow, clarity needed for others to understand it from start to finish is not there.” “Review both artifacts from this perspective and upgrade them to be world-class documents reflecting everything that we have addressed so far, including the approach of leading with key points, bolded” “Then I will give it a careful review and apply my own edits. What is the most efficient way for me to do this? Perhaps you separate the text into a markdown format and I can update that as the source of text to be used.”

• Rules that already apply: the bold key-point lead-ins (Core/Processes/Design/Voice.md, cross-brand rule); Brief under 5 minutes, always; “Updated” date; relative links; the reading bar; “show every period, not one” (all in Core/Processes/Design/Targets/Design-Reports.md).
• Labels (Talbot, round 14): “Practical solution” = halve stocks when the Valuation + Trend rule fires. The all-to-cash version is the “full-exit version” (Claude’s suggested label for Talbot’s “All in or out solution”; confirm).

Tasks

1. Move all prose into one Markdown source file per report (~/projects/cape-timing/content/main.md and content/companion.md). This is the single source of text that Talbot edits.
   • Numbers stay generated. Use placeholders like {{iy_bh100}} that map to the existing data-k keys, so no figure is typed by hand.
   • Mark Full-only text with a block marker (e.g. :::full … :::) and an inline one for parts of paragraphs.
   • The build converts Markdown to HTML (a small, pinned uv dependency such as markdown-it-py) and fails loudly on an unknown placeholder.
2. Rewrite for outside readers: state the hypothesis up front; a clear start-to-finish flow (question → hypothesis → evidence → risk-adjusted view → every period → Practical solution → limits → what to do); bold key-point lead-ins everywhere.
3. Viewing bar upgrade
   • Currently: Contents, Details: Brief/Full
   • Change Details > Length [X]m/[Y]m (only show reading time estimates, not the Brief/Full values)
   • Add “Detail: Basic/Advanced”
     • I want a separate version of all briefings to include two different Detail levels or Views. Per my F.A.S.T.T. principle, we want to use provide the appropriate language to match the knowledge level of the reader. My initial label for this property was “Detail level”. It is the most semantic. However I believe that the label of View is Is effective and shorter, when the values clarify the semantic meaning which is the case with the values “Basic / Advanced”. Agreed, or can you suggest better?
       • Alternates
         • Detail: Basic/Advanced (current favourite)
         • View: Basic/Advanced
         • Details: Basic/Advanced
   • Add this upgraded “Viewing bar” functionality to the artifacts skill and guidelines that create them, and apply to the two artifacts involved here.
     • Upgraded “Viewing bar”: Contents Length: [X]m/[Y]m Detail: Basic/Advanced
       • Contents: shown in left sidebar for desktop viewports, popup for smaller
       • Viewing defaults: Length: briefest, Detail: Basic/simplest
   • Add Tooltip to the Detail label to clarify?
     • Basic Detail view is best for most people. Advanced is for those with deeper knowledge and/or wanting the more technical language.
4. Apply the Red Team results and Talbot’s exit-rule decision (from Market-timing-Red-Team) to the text and to the figures’ labels.
   • That covers the presentation decision (Talbot rejected a returns-led headline; the lens is behavioural and emotional), MT-1 at risk level 1, and the suitability exclusions.
   • It also covers the new “I have enough: is it wrong to wait?” analysis (L11, results/enough_wealth.json) and the CAPE-drift analysis (L12, results/cape_drift.json), with both Red Team reviews’ verdicts. 4b. More artifact upgrades (Talbot, to add here; moved from the Red Team task, 2026-09-29):
5. Hand Talbot the two .md files to edit. Then rebuild, test (render, 0 console errors, no horizontal scroll, Brief under 5 min on both), republish, and commit.

Success Criteria

• Both reports read clearly to an outsider from start to finish, with the hypothesis stated and every point led by a bold key phrase.
• All prose lives in content/*.md; no report text remains hard-coded in the templates; every number is a generated placeholder.
• Brief is under 5 minutes on both; tests pass; both are republished.
• Talbot has edited the Markdown and his edits are live.