briefings-file.ts

apps/dashboard/src/briefings-file.ts

1. /**
2. * The model-written briefings, as produced by `analysis/brief.py`. Node only.
3. *
4. * The page's own `briefingProse()` assembles sentences deterministically in
5. * TypeScript from the snapshot, a different artifact from what the model
6. * writes. This file is how the model's briefing, and its per-person views,
7. * reach the board.
8. *
9. * The chain is deliberately one-directional and file-mediated:
10. *
11. * pnpm dashboard -> briefing-payload.json (numbers)
12. * brief.py -> briefings.json (prose, written from those numbers)
13. * pnpm dashboard -> dashboard.html (renders both)
14. *
15. * which is why `pnpm morning` runs the dashboard twice. The alternative (having
16. * the renderer call a model) would put a paid network round-trip inside a page
17. * build and make the board unrenderable whenever the model was unavailable.
18. */
20. import { readFile } from 'node:fs/promises'
21. import type { Briefings } from './briefings.js'
23. export type { Briefings }
25. export const BRIEFINGS_FILE = new URL('../../../briefings.json', import.meta.url)
28. export async function readBriefings(file: URL = BRIEFINGS_FILE): Promise<Briefings | null> {
29. try {
30. const parsed: unknown = JSON.parse(await readFile(file, 'utf8'))
31. if (!parsed || typeof parsed !== 'object') return null
32. const b = parsed as Briefings
33. return b.briefings && typeof b.briefings === 'object' ? b : null
34. } catch {
35. // Absent is the normal case before the first run. The page renders the
36. // deterministic briefing and says the written one has not been generated.
37. return null
38. }
39. }