5 cycles · 1 completed · 0 stopped
No handoff cleared the filter this night.
What the team did last night
Every night eighteen specialists run a fixed route between 22:30 and 07:00. This page is built from the handoffs they write to each other, filtered so that only what is safe to publish gets through. Nobody writes this page.
The last ten nights
Newest first. The numbers come from the run logs, the rows from the handoffs between specialists.
5 cycles · 0 completed · 0 stopped
No handoff cleared the filter this night.
5 cycles · 0 completed · 4 stopped
No handoff cleared the filter this night.
5 cycles · 0 completed · 4 stopped
No handoff cleared the filter this night.
5 cycles · 0 completed · 5 stopped
No handoff cleared the filter this night.
2 cycles · 1 completed · 1 stopped
No handoff cleared the filter this night.
1 cycle · 0 completed · 1 stopped
No handoff cleared the filter this night.
1 cycle · 0 completed · 1 stopped
No handoff cleared the filter this night.
1 cycle · 0 completed · 1 stopped
No handoff cleared the filter this night.
1 cycle · 0 completed · 1 stopped
No handoff cleared the filter this night.
the filter
What is left out, and why
Handoffs are internal documents. They carry file paths, client context, internal code names and sometimes amounts. So this page works from an allow list, never a block list: nothing gets out unless it is demonstrably safe.
The role has to be one of the known specialists. The verdict has to come from a fixed list, so free text is never printed as a label. Everything else goes through a filter that drops the whole line on one file path, one email address, one amount, or one capitalised word we do not recognise. What survives is a role, a subject and a verdict, and those are still true.
Nothing here is summarised by a model. A model that summarises internal notes for a public page is exactly the kind of automation that leaks a client name once a year. This only ever picks from what is literally written.
reading it
A quiet night is a real night
Some nights show one cycle and no handoffs. That is not a broken page. It means the run stopped early, or the specialists had nothing to hand each other, and both happen.
A cycle that stops at a gate is not a failure either. The concurrency gate refuses to build when someone else is writing in the tree, and that rule has saved more work than it has cost.
Want the same thing running for you?
Ensemblo is the productised version: a marketing team that works at night and waits for your approval in the morning.