v2 payload contract rollout · Software Development

Routing5

at Build

RSH3/3
Discovery
Anselm Reyes
Complete
✓
ENG3/3
Specification
Aris Vandel
Complete
ENG2/4
Build
Aris Vandel
Active
◇
ENG0/3
Quality assurance
Aris Vandel
Pending
⬡
OPS0/3
Release
Mira Halvorsen
Pending

Ready to start6

2 waiting

Instrument per-consumer contract versionHalo Rune
Migration test suite across both contractsBuild Runner
Load test at 3x peak with mixed versionsProbe
Partial-failure rehearsalCipher Vale
Rehearse the rollbackKestrel
Publish the consumer noticeOperations

Held behind a dependency

Regression across every named consumer×4
Stage the tiered rollout plan×3

Assigned teams3

Departments, in routing order

Accountable

Executive Rhea KastellanManagers Anselm Reyes, Aris Vandel, Mira Halvorsen

AI agents on this workflow

Stage timeline

STAGE 1
Discovery
Complete40h planned
Establish which consumers break and how loudly.
ResearchManager Anselm Reyes1 agent: Archivist
3 of 3 tasks100%
STAGE 2
Specification
Complete56h planned
The contract, the shim strategy and the notice period, in writing.
EngineeringManager Aris Vandel2 agents: Schema Guard, Tessa Kord
3 of 3 tasks100%
Manager approvalApproved10 Jul 2026
Approve the v2 contract and the two-week consumer notice.
Held by Aris Vandel
Approved. Notice period held at two weeks per the standing department rule.
STAGE 3
Build
Active200h planned
Implement v2, the shims, and the instrumentation that proves migration.
EngineeringManager Aris Vandel3 agents: Tessa Kord, Halo Rune, Build Runner
2 of 4 tasks50%
STAGE 4
Quality assurance
Pending64h planned
Prove both contracts hold under load and under partial failure.
EngineeringManager Aris Vandel1 agent: Probe
0 of 3 tasks0%
QA approvalPending12 Aug 2026
Sign off that both contracts hold under load and partial failure.
Held by Probe
Not reached yet — Build is still open.
STAGE 5
Release
Pending32h planned
Staged rollout with a rehearsed way back.
OperationsManager Mira Halvorsen1 agent: Kestrel
0 of 3 tasks0%
Executive approvalPending16 Aug 2026
Authorise the staged production rollout.
Held by Rhea Kastellan

Dependencies

Discovery

3

Inventory every consumer of the v1 payload

Completed·Archivist

Unlocks 1 task

Classify breakage by consumer criticality

Completed·Archivist

Unlocks 1 task

Recommend a notice period

Completed·Anselm Reyes

Unlocks 1 task

Specification

3

joins from Discovery

Draft the v2 contract

Completed·Schema Guard

Unlocks 1 task

Specify the v1 compatibility shim

Completed·Tessa Kord

Unlocks 1 task

Sequence the migration by consumer tier

Completed·Aris Vandel

Unlocks 1 task

Build

4

joins from Specification

Implement the v2 serializer

Completed·Tessa Kord

Unlocks 2 tasks

Implement the v1 shim layer

Completed·Halo Rune

Unlocks 2 tasks

Instrument per-consumer contract version

In progress·Halo Rune

Ready — every dependency closed

Unlocks 1 task

Migration test suite across both contracts

To do·Build Runner

Ready — every dependency closed

Unlocks 1 task

Quality assurance

3

joins from Build

Regression across every named consumer

Backlog·Probe

Waiting on 2: Instrument per-consumer contract version; Migration test suite across both contracts

Unlocks 1 task

Load test at 3x peak with mixed versions

Backlog·Probe

Ready — every dependency closed

Unlocks 1 task

Partial-failure rehearsal

Backlog·Cipher Vale

Ready — every dependency closed

Unlocks 1 task

Release

3

joins from Quality assurance

Stage the tiered rollout plan

Backlog·Operations

Waiting on 3: Regression across every named consumer; Load test at 3x peak with mixed versions; Partial-failure rehearsal

Rehearse the rollback

Backlog·Kestrel

Ready — every dependency closed

Publish the consumer notice

Backlog·Operations

Ready — every dependency closed

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.

Board16

Backlog

6

Regression across every named consumer

Highqawaiting ×4

Probe12 Aug

Load test at 3x peak with mixed versions

Highqa

Probe13 Aug

Partial-failure rehearsal

qa

Cipher Vale14 Aug

Stage the tiered rollout plan

releasewaiting ×3

Operations16 Aug

Rehearse the rollback

Highrelease

Kestrel17 Aug

Publish the consumer notice

release

Operations18 Aug

To do

1

Migration test suite across both contracts

buildready

Build Runner08 Aug

In progress

1

Instrument per-consumer contract version

Highbuild

Halo Rune05 Aug

Review

0

Empty

Blocked

0

Empty

Completed

8

Inventory every consumer of the v1 payload

Highresearch

Archivist19 Jun

Classify breakage by consumer criticality

research

Archivist24 Jun

Recommend a notice period

research

Anselm Reyes26 Jun

Draft the v2 contract

Highspec

Schema Guard03 Jul

Specify the v1 compatibility shim

Highspec

Tessa Kord07 Jul

Sequence the migration by consumer tier

spec

Aris Vandel09 Jul

Implement the v2 serializer

Highbuild

Tessa Kord24 Jul

Implement the v1 shim layer

Highbuild

Halo Rune29 Jul

Approval gates3

2 open

Manager approvalApprovedNot reached09 Jul 2026

v2 payload contract rollout

Approve the v2 contract and the two-week consumer notice.

Stage SpecificationEngineeringHeld by Aris Vandel

Approved. Notice period held at two weeks per the standing department rule.

QA approvalPendingNot reached12 Aug 2026

v2 payload contract rollout

Sign off that both contracts hold under load and partial failure.

Stage Quality assuranceEngineeringHeld by Probe

Not reached yet — Build is still open.

Executive approvalPendingNot reached16 Aug 2026

v2 payload contract rollout

Authorise the staged production rollout.

Stage ReleaseOperationsHeld by Rhea Kastellan

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.

Memory links2

Messages3

Aris Vandel2d ago
Shim layer is in. Instrumentation is the last thing between us and QA.
Open in the Hub →
Schema Guard4d ago
Contract frozen. Any further change restarts the notice clock.
Open in the Hub →
Anselm Reyes3w ago
Four consumers break silently rather than loudly. Those are the dangerous ones.
Open in the Hub →

Related projects2

Performance

392h planned · 192h remaining

50%

Progress

8 of 16 tasks

2/5

Stages closed

1/3

Gates cleared

0

Blocked tasks

3

Departments

routed through

8

Agents

named on the work

192h

Remaining

from the breakdown

-6h

Estimate variance

6h under

Task completion50%

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 · All stages complete

Closed when the release stage completes and the rollback path is on file.

Every stage reaches complete or skipped.

Automation7

1 would fire · 0 will

Next routing decisionHeld

2 open tasks in Build.

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
2 tasks still open in Build.
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 tasksWould fire
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
4 backlog tasks have all dependencies closed.
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 not satisfied yet.
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 log6

Halo Rune Moved instrumentation into progress.
Build
6h ago
Halo Rune Closed the v1 shim layer.
Build
2d ago
Aris Vandel Approved the specification gate — notice period held at two weeks.
Specification
3w ago
Workflow Engine Routed from Specification to Build.
Build
3w ago
Anselm Reyes Closed Discovery — 34 consumers inventoried, 4 breaking silently.
Discovery
5w ago
CEO Opened from the Software Development template — 5 stages, 3 approval gates.
7w ago