Skip to main content

The jobs teams hand over first

Hand over the work, keep the record.

Each use case is a governed workflow you turn on, not a prompt you maintain. Every run leaves a cost, an outcome and a document you can reread.

The library, by the work it does.

A use case says what starts it, what it produces and what it records. Pages ship as their workflows do, and one whose workflow is still in build says so.

Example — fictional team and data. Not a live run or customer result.

Use cases

document

Go / no-go — R7 · Billing v2

Starts: PROJ-41 · milestone R7 · Billing v2 · 14 tickets · demo data

Verdict
NO-GO — 3 blockers, 2 risks. Migration 0299 shipped in a merged pull request and has no record of being applied to production. The verdict is computed from the eight results below, not written by the model: one failed blocking check is a NO-GO however the rest of the document reads.
Blockers
1. Migration 0299 has not been applied to production — evidence PR #812, AES-1841 — filed as AES-1902, owner Lior Heber. 2. AES-1846 was reviewed and rejected and has not been reworked — evidence AES-1846, AES-RUN-4479 — filed as AES-1903, owner Dana Katz. 3. AES-1850 is blocked by AES-1799, which is outside this release — evidence AES-1850, AES-1799 — filed as AES-1904, unassigned.
Risks
Two pull requests merged in the window are linked to no ticket, so nobody owns them and no acceptance was recorded against them (PR #803, PR #818). Four tickets carry no acceptance criteria, so "done" was never written down and review had nothing to check against (AES-1837, AES-1844, AES-1848, AES-1850).
Readiness by check
tickets_terminal fail 11/14 · pull_request_merged fail 12/14 · pull_request_linked fail 15/17 · review_accepted fail 13/14 · acceptance_criteria_present fail 10/14 · migrations_applied unknown · dependencies_clear fail 13/14 · runs_clean pass 14/14. Every count was computed by the server before the model was called; an answer echoing a number the facts do not state is refused.
Not checked
Staging soak and load test results. Customer and support communications for this release. Feature-flag state in production. On-call cover for the release window. Aestus holds no record of any of these, and says so every time rather than letting their absence read as a pass.
Sources
Board: PROJ-41, milestone R7 · Billing v2, 14 tickets. Pull requests: 17 merged in the last 21 days. Runs: 14 across those tickets, 13 with an accepted verdict. Anchor ticket AES-1841, read for a "MIGRATIONS APPLIED" attestation and finding none.

The library, by the work it does.

A use case says what starts it, what it produces and what it records. Pages ship as their workflows do, and one whose workflow is still in build says so.

Everyday productivity

Marketing

Sales

Customer support

Operations

Finance

Product

Engineering

Aestus-native

Start with one job.

Tell us which of these you would hand over first and we will set it up with you.

Talk to us