The Broadcast
This site: a portfolio that reports its own state. Every card says what exists and what is only planned; three live signals show what the machine behind the work is doing; and the things only Luke can do flow from here to his Semantica desk.
IN BUILD
What it is
The Broadcast is Luke Spooner’s portfolio and the proof index for his projects. One Node server with no dependencies serves the project catalogue, a story, the papers and a live feed. Every project card is generated from a private knowledge file, so a public claim exists only where somebody approved it, and a release hash records every change to the public copy.
The live layer has three independent signals, each with its own clock: the host’s own report, posted by the machine that runs the agents; GitHub’s record of pushes across the fleet of repositories; and the face each repository publishes about itself from its CI. A signal nobody measured reads dark, never zero, and every reading carries its age. Nothing on the live panel is typed by hand.
It is also a station of Semantica. The things only Luke can do are filed as asks in Semantica’s own dialect and served from this site’s desk feed so his desk can pull them; the lifecycle rules Semantica enforces are checked by a Python referee in this repository’s CI; and the site’s own status file is computed from the desk, never typed.
A funnel counts requests without tracking anyone. A Frame marks every number current, stale or dark. The release flow is one branch for integration and one for deployment, moved only by a workflow that gates on green tests and leaves an annotated tag as the receipt.
What is on it
- Project cards with what exists, what is not done, what is next, the stack, evidence rows with file hashes, and figures.
- A story in dated waypoints, a CV that links every line to its evidence, and a glossary of the site’s own words.
- The live panel: host report, work on GitHub, project faces; an engine room with the funnel; the public feed at /api/state.
- Doors for employers, clients, collaborators and backers.
What exists today
Live on Railway. Tested in CI with a Node suite (151 tests on 21 October 2026) and a Python referee for the lifecycle rules; a spine check refuses an unrecorded change to the public copy. The source repository is private; the lifecycle protocol and the design papers inside it are the parts most worth reading.
The host report is stale: the machine that posted it last reported on 26 August 2026, and every page that shows it says so.
Not done
Production serves the live branch (measured 30 October 2026).
Private repositories read dark on the fleet instrument until a read-only token is set.
No custom domain yet.
Next
Serve it from a real domain once DNS is set. Reconnect the machine feed so the host report reads live again. Keep the words plain enough for a first-time visitor.
Built with
Node 22 no dependencies Railway GitHub Actions