Write the series brief
Completed·Sable Quinn
Unlocks 1 task
Content CreationContent Creation template
Archive relaunch series
CompleteNormalCompletion rule satisfied and closed.
100progress
progress: 100 out of 100Republish the eight strongest pieces from the pre-2019 archive with sources restored, and prove the archive is worth the tagging effort.
Next
Closed. The completion rule was satisfied.
Closed
Current stage
4
Stages
9
Tasks
9 closed
0
Open gates
0
Ready now
0 waiting
6 weeks
Planned
Ready to start0
0 waitingEvery task is closed.
Assigned teams2
Accountable
Executive Junia FalkenrathManagers Juno Prieto, Anselm Reyes
AI agents on this workflow
Stage timeline
- STAGE 1
Brief
Complete8h plannedDecide what the series is for before anyone writes it.
2 of 2 tasks100% - STAGE 2
Draft
Complete32h plannedRewrite the eight pieces against the brief.
3 of 3 tasks100% - STAGE 3
Fact check
Complete12h plannedEvery claim traced, or cut.
2 of 2 tasks100%QA approvalApproved18 Jul 2026Confirm every restored claim has a reachable source.
Held by Citation
Approved. Two pieces dropped rather than published without sources.
- STAGE 4
Publish
Complete8h plannedShip it and file it where the next piece finds it.
2 of 2 tasks100%Manager approvalApproved21 Jul 2026Approve publication of the six surviving pieces.
Held by Juno Prieto
Dependencies
Brief
2Agree the angle and audience
Completed·Juno Prieto
Unlocks 1 task
Draft
3joins from Brief
Rewrite the eight selected pieces
Completed·Sable Quinn
Unlocks 1 task
Restore missing source material
Completed·Archivist
Unlocks 1 task
Commission the artwork
Completed·Pica
Unlocks 1 task
Fact check
2joins from Draft
Verify claims against restored sources
Completed·Citation
Unlocks 1 task
Record the citations
Completed·Archivist
Unlocks 1 task
Publish
2joins from Fact check
Publish the series
Completed·Loom
Unlocks 1 task
File to the Marketing knowledge base
Completed·Archivist
One column per stage, in routing order. Tasks inside a stage run in parallel; the first task of each stage joins from every task of the one before it, which is the hand-off between departments made explicit.
Board9
Backlog
0Empty
To do
0Empty
In progress
0Empty
Review
0Empty
Blocked
0Empty
Completed
9Write the series brief
brief
Sable Quinn12 Jun
Agree the angle and audience
brief
Juno Prieto13 Jun
Rewrite the eight selected pieces
draft
Sable Quinn01 Jul
Restore missing source material
Highdraft
Archivist04 Jul
Commission the artwork
Lowdraft
Pica08 Jul
Verify claims against restored sources
Highcheck
Citation16 Jul
Record the citations
check
Archivist18 Jul
Publish the series
publish
Loom22 Jul
File to the Marketing knowledge base
publish
Archivist24 Jul
Approval gates2
0 openQA approvalApprovedNot reached16 Jul 2026
Archive relaunch seriesConfirm every restored claim has a reachable source.
Approved. Two pieces dropped rather than published without sources.
Manager approvalApprovedNot reached20 Jul 2026
Archive relaunch seriesApprove publication of the six surviving pieces.
Deciding a gate writes the decision and nothing else. The status change, the release of downstream stages and the “ready to close” state are all derived from it on the next render — which is why an approval here is one field rather than a transaction.
Messages1
- Juno Prieto1w ago
Six of eight published. The two we dropped had no recoverable sources and that is the finding.
Open in the Hub →
Related projects1
Performance
60h planned · 0h remaining100%
Progress
9 of 9 tasks
4/4
Stages closed
2/2
Gates cleared
0
Blocked tasks
2
Departments
routed through
5
Agents
named on the work
0h
Remaining
from the breakdown
—
Estimate variance
on plan
Task completion100%
Task-weighted, not stage-weighted. A two-hour approval stage and a two-hundred-hour build stage are not half the work each, and treating them as such is the usual way a project dashboard reports 50% before anything has been built.
Completion rule · Deliverable produced
Closed when the published series is filed as a memory record.
The named deliverable exists as a memory record linked to this workflow.
Automation7
0 would fire · 0 willNext routing decisionHeld
Every stage is finished.
Computed by engine.peekAdvance(), which returns the next stage rather than moving to it. The Task Orchestrator owns the write; keeping this side pure is what lets a card show “next: Engineering” with no risk that rendering a page advances a workflow.
- Advance stage on completion
- WHEN
- Every task in the active stage reaches a terminal column and the stage carries no pending gate.
- THEN
- Mark the stage complete and route work to the next stage in the chain.
- NOW
- No active stage.
- Notify approver on gate open
- WHEN
- A stage with a gate becomes active and the gate is still pending.
- THEN
- Raise a workflow notification addressed to the named approver in the Communication Hub.
- NOW
- No gate is currently open.
- Escalate a stale gate
- WHEN
- A gate has been pending longer than its stage's estimate.
- THEN
- Escalate one authority level up and notify the accountable executive.
- NOW
- Needs a real clock. Placeholder timestamps are relative strings.
- Release dependent tasks
- WHEN
- A task reaches a terminal column and other tasks depend on it.
- THEN
- Move every newly-ready dependent from backlog into to-do.
- NOW
- No backlog task is waiting only on a dependency.
- Write outcome to memory
- WHEN
- The completion rule is satisfied.
- THEN
- Write a project-scope memory record summarising the outcome and link it back.
- NOW
- Completion rule is satisfied and the outcome is not filed.
- Auto-approve low-risk gatesHeld for a human
- WHEN
- A QA or manager gate carries no rejection history and sits under the risk threshold.
- THEN
- Nothing. Recorded so the policy is visible and reviewable — a gate an agent can clear is not a gate.
- NOW
- Held for a human by design.
- Stand down a stalled workflowHeld for a human
- WHEN
- No activity for longer than the estimated duration and no open gate explains it.
- THEN
- Nothing automatic. Surfaces the workflow for a human decision.
- NOW
- Held for a human by design.
Nothing here executes. There is no scheduler, no queue and no writer — these are evaluations of the current state, refreshed on every render. Adding a trigger is one row in AUTOMATION_TRIGGERS; it appears on every workflow immediately so a rule can be checked against real data before anything is built to act on it.
Activity log5
- 1w ago
Workflow Engine Completion rule satisfied — series filed to memory. Closed.
Publish - 1w ago
Archivist Wrote the pre-2019 metadata finding to project memory.
Publish - 2w ago
Juno Prieto Approved publication of the six surviving pieces.
Publish - 2w ago
Citation Cleared fact check — two pieces dropped for unreachable sources.
Fact check - 7w ago
CEO Opened from the Content Creation template — 4 stages, 2 approval gates.