Every Friday afternoon, the week becomes a short video for the whole team: what shipped for clients, what each team finished, and what went live, with the names of the people who did it. It's built from routines that already run and sent out with one approval.
The routines that run Edge8 read the boards, the client repos and the content calendar every day. They already know what shipped. What gets lost is the telling. A written recap gets skimmed, and good work goes by without anyone seeing it.
So this workflow turns the week into a short video every Friday. Nobody writes it by hand. Claude storyboards it from the week's records, the video pipeline renders it, and one person in ops approves it before the team sees it.
Four of the five steps run on their own. The only human step is the approval, and nothing reaches the team without it.
| Step | Who | When | What happens |
|---|---|---|---|
| Work gets done | The team | All week | Cards move, pull requests merge, posts go live. Nobody does anything extra for the recap. |
| The week is read | System | Fri 13:00 | Reads the weekly recap, customer status, merged pull requests, completed cards and live posts. |
| Storyboard and render | Claude and system | Same run | Claude writes one scene per thing that shipped, grouped by client and then by team, with the names of the people on it. The pipeline renders a 16:9 MP4 and a watch page, then checks reading time, cuts on the beat and sound levels. |
| Approve | Ops channel | Fri afternoon | Approve it, or send it back with a note. A note re-runs the storyboard and render. |
| Post | System | On approval | The team Lark channel gets the watch link and everyone who appears in it. |
If fewer than five things shipped, the run stops after reading and sends nothing. The week carries into next Friday's recap.
The video is built from segments. Each one has its own sources and its own rules, so a new one can be added without touching the rest. A segment with nothing to say drops out that week. At launch, the video is one segment.
The weekly recap routine, Customer status, PR and effort sync, the team boards and Blog publish.
Needs at least five items to run. Every scene names the people on it.
What the team sees: one scene per thing that shipped, grouped by client and then by team, with the names of the people who did it.
Innovation weekly and the Ideas backlog.
Learnings only, not plans. Every claim links to its reading.
What the team sees: one animated scene per lesson, the same format as the standalone Ideas recap we already made.
Key result sync and the marketing pulse.
Revenue stays out unless leadership opts in.
What the team sees: the few numbers that moved, each with its owner.
The planning cards that Weekly sprints opens.
Only what a team has committed to, not the whole backlog.
What the team sees: a closing scene on what's coming next week.
| When (+07) | The run does | The team sees |
|---|---|---|
| All week | Nothing extra. The existing routines keep reading the boards, repos and calendar. | Work as usual |
| 13:00 | Reads Monday to Friday. Stops here if fewer than five things shipped. | Nothing yet |
| 13:00 to 14:00 | Writes the storyboard, renders the video and runs the checks. | Nothing yet |
| About 14:00 | Posts the draft to the ops channel with the watch link and the list of sources. | Ops can review it |
| Before 15:00 | Re-renders on any note. Posts to the team channel on approval. | The video in the team channel |
| 15:00 | Marks any unapproved draft as held. Its items roll into next Friday. | Nothing posts late |
The finish line: by the weekend, everyone on the team knows what shipped that week without anyone writing it up, and the people who shipped it got named for it.
Every workflow we document has the same seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
| Element | Assigned to | In this workflow |
|---|---|---|
| Trigger | Machine | Friday, 13:00 (+07). The calendar starts it, so nobody has to remember to. |
| Inputs | Machine | The weekly recap, customer status, merged pull requests, completed cards and live posts. Nothing gets typed up for the video. |
| Decision | Human | Ops approves the draft or sends it back with a note. Claude writes the story, and a person decides it goes out. |
| Routing | Machine | Drafts go to the ops channel, notes go back to the storyboard, and the approved cut goes to the team channel. |
| Output | Both | A storyboard that Claude writes and a person signs off, rendered as a 16:9 MP4 and a watch page. |
| Delivery | Machine | The team Lark channel on Friday afternoon, with the watch link and everyone who appears in it. |
| Measurement | Machine | The run log on Settings → Agents, plus views per recap. See Keeping score below. |
All in, that's one routine to schedule, one data read to expose and one person to own the approval.
A recap that nobody watches is just a more expensive status report. So every run is logged, and after four Fridays we look at the numbers and decide whether it earns a place as a Built routine.
| Measure | Where it lives | What it tells us |
|---|---|---|
| Items read, scenes made, checks passed | Run log on Settings → Agents | The pipeline is healthy |
| Time to approval | Run log | Whether the gate slows things down |
| Views per recap | The watch page and the Lark post | Whether people actually watch |
| Weeks held or skipped | Run log | Whether five items is the right bar |
It ships through the same three stage gates as every workflow we run.
Numbers that moved and Next week follow once the first two segments have run for a month. See the agents we run Edge8 on for the routines it reads from.