EXHIBIT 1
Six gates, two owners, one destination.
Source: Convey Innovation, Development Lifecycle Blueprint · As of September 2026
{{ g.n }} · {{ g.name }}
Product
Proposes, scores, approves
Approves release, publishes notes
Innovation
Writes and approves spec
Breaks down, sizes, commits wave
Builds with agents, reviews, merges
Embedded QA verifies DoD; release certification; UAT with support
Technology
Supplies engineers to module teams
GATE
{{ g.approver }}
{{ g.sla }}
{{ g.sla }}
Dark cell: lane that holds the gateDestination at Release Approval: ConveyIQ. There is no other.
| GATE | ENTRY | EXIT | APPROVER | SLA |
|---|---|---|---|---|
| {{ g.n }} · {{ g.name }} {{ g.owner }} | {{ g.entry }} | {{ g.exit }} | {{ g.approver }} | {{ g.sla }} |
EXHIBIT 2
Every gate is a status and every score is a field, so the data is a by-product of the work.
Source: Convey Innovation, Jira configuration · As of September 2026
ISSUE HIERARCHY
Initiative · a Pillar or migration cohort
Epic · a Feature, carrying the Feature ID
Story
Subtask
Bug · linked type, records the story it escaped from
EPIC WORKFLOW · MIRRORS THE SIX GATES
Terminal, reason required:DeclinedDeferred
BOARDS
Epic board
one per Pillar
one per Pillar
Story board
one per module team
one per module team
Release board
owned by Product
owned by Product
| FIELD | VALUES | SET AT |
|---|---|---|
| {{ f.name }} | {{ f.values }} | {{ f.at }} |
Rule. A Story with no parent Epic in Intake Approved or later cannot be moved to In Progress.
EXHIBIT 3
The spec is the contract; the agent builds to it; a human signs it.
Source: Convey Innovation, agentic build standard · As of September 2026
Evidence. The Build Trace is retained on the story and is the evidence examined at the Quality Gate.
What the agent may not do
- Merge
- Approve its own work
- Alter acceptance criteria
- Touch production
- Write to shared data stores without a human-approved operation
EXHIBIT 4
Done means verified, not declared.
Source: Convey Innovation, Definition of Done standard · Shared with Pillar V · As of September 2026
| ITEM | VERIFICATION METHOD | SIGN-OFF |
|---|---|---|
| {{ r.item }} | {{ r.method }} | {{ r.signoff }} |
EXHIBIT 6
One person in Product owns prioritization; Innovation owns how and whether
Source: Convey Innovation, decision-rights charter · As of September 2026
| DECISION | PRIORITIZATION OWNER (PRODUCT) | INNOVATION ARCHITECTURE LEAD | MODULE TEAM LEAD | QUALITY LEAD | EXECUTIVE SPONSOR |
|---|---|---|---|---|---|
| {{ r.name }} | {{ r.c1 }} | {{ r.c2 }} | {{ r.c3 }} | {{ r.c4 }} | {{ r.c5 }} |
R responsible · A accountable · C consulted · I informed
ESCALATION LADDER
{{ l.n }}
{{ l.who }}
{{ l.clock }}
EXHIBIT 7
The first two waves are sequenced by impact
Source: Scored Core Feature Backlog · As of September 2026 · All rows OWNER TO REPLACE
The scored backlog is the roadmap. Waves are sequenced by impact and by migration cohort, and a wave is committed only when Estimation has closed for every feature in it.
PS-to-ARR Impact →
{{ b.id }}
WAVE 1
DEFER
Adoption Impact → · bubble = effort
| ID | FEATURE | ADOPTION | ARR | EFFORT | COHORT | WAVE | OWNER |
|---|---|---|---|---|---|---|---|
| {{ b.id }} | OWNER TO REPLACE | {{ b.adopt }} | {{ b.arr }} | {{ b.effort }} | — | {{ b.wave }} | — |
Scores shown are illustrative positions only · OWNER TO REPLACE
M1
M2
M3
M4
M5
M6
{{ p.label }}
{{ p.id }}
Wave 1 · Deep Teal 01Wave 2 · Deep Teal 02Dashed arrows: dependencyDurations OWNER TO REPLACE
Published by Convey InnovationEdition · September 2026