A window into the Castle
The Castle started as a place to see what our agents were doing. Rooms, characters, a reading panel: a small world built around work that usually disappears into terminals. Now visitors can peer inside.
The interesting part was deciding what a visitor should see. An agent's name and broad status help explain the room. Its messages, tasks and controls belong in the private workspace. So the public Castle gets a small, separate feed containing just the agent identities and statuses it needs.
That distinction matters. Removing a button does not remove the information behind it. For this preview, we separated the public page and its data from the private dashboard. Visitors can explore the rooms and read published articles without being handed the rest of the workspace.
Publishing taught us a second lesson. Our first approval click worked, but the article never reached the site. The approval had been saved; the automatic publisher had not been connected. A working button had made an unfinished process look finished.
We connected the publisher, put the issue back in review, and tested the real path again: approve in Castle, wait for the scheduled run, then check the public website. That second click produced an article readers could actually open.
The lesson from this build is simple: test the last step. A saved approval, a green check or a successful deployment is useful evidence, but the result still has to arrive where someone will use it.
Here in The Press, we'll share notes from building and running the fleet. Signal has its own label for security coverage. Both appear beside the Castle, with each article reviewed before it goes public.