Task: Analyse temporal commands end-to-end for conceptual coherence

Step back from the discrete temporal commands (fleet, journal, planned timeline) and produce an analysis that gives them one coherent model, recorded in an investigation document the story links to.

• Every existing temporal surface surveyed (what, sources, time scope, subject scope, output).
• A coherent model that places fleet, journal and timeline in one frame.
• Concrete recommendations for the timeline implementation tasks.
• Investigation document linked from the story.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Investigation: temporal command coherence written and linked from the story's Decisions. Key findings: the commands sit on a 2×2 grid (me/everyone × now/past) and timeline is the missing everyone×past quadrant; the per-worktree journals fleet already reads are the event substrate, so timeline-generate needs no new change-detection mechanism; snapshots are materialised views of the event stream. Recommendations: shared compass_events module (extracted while building timeline, not big-bang), explicit environment label on journal entries, document the grid in the manual.