PropFlo · Phase 1 (minimum viable product)
The plan is anchored at 15 August 2026. Three things about that anchor change how every band below reads, so they come first.
One. The first band is already spent. 15 August is seven days in the past, and it was a Saturday, so that band held five working days, Monday 17 to Friday 21 August. What those days produced is on the record: the product specification shelf was cleared on the 15th, twenty-two decisions tracked across five file formats were reconciled into one series on the 19th and 20th, a requirements workshop ran on the 21st, and this planning shelf was written on the 22nd. None of the twenty-five work items started in that band, and no product change has ever merged. That is not a slip — nothing had been committed, so nothing could be missed — and it is not on track either. It is seven days of the anchor consumed with the product build at zero.
Two. The anchor starts the plan on the day its own basis was withdrawn. 15 August is the date the product specification shelf was deliberately cleared. Day one of the waterfall is the day the specification underneath it was deleted on purpose, which is why seven of the twenty-five tickets have nothing to build against.
Three. Two delivery models are in play and neither is adopted. One is a single-developer commercial shape; the other is a parallel band of five or more workstreams. They have never been reconciled, and once the estimate landed on 22 August the arithmetic showed the first of them cannot be done by anybody at any level of skill. So the reconciliation that is needed is not a preference between two plans, it is the retirement of one. Until that happens, no end date exists and none may be quoted from this page.
Reading a row. A solid left bar and a dated tag mean an owner has a due date. A dotted left bar, a hatched background and an unscheduled tag mean the row has no date and is not available at any price today. A dated row is a row whose owner has a due date, not a row that has started.
| Date | What actually happened |
|---|---|
| Sat 15 Aug | Product specification shelf cleared — the decisions register, the screen frame set, the work breakdown and the product architecture records. The event engine moved from the later phase into Phase 1 in full, and the fixed commercial envelope was not re-cut. |
| Wed 19 – Thu 20 Aug | Decision reconciliation. The deal lifecycle specification reached version 2.1 and the event engine specification version 2.2. |
| Fri 21 Aug | The requirements workshop ran. Twelve rulings, each with a citation, none yet carrying a decision number — and four of them contradict what is currently on the shelf. |
| Sat 22 Aug | This planning shelf: requirements, architecture, estimates, the structural skeleton, the infrastructure plan and this board. |
Product work started in band 0: none. No exit criterion had been set for it.
Every row here is a due date on a named owner, not a duration. A due date is a commitment on a person rather than an estimate of work, which is why these rows can be dated while the build cannot. Nineteen rows, seven owners, five working days, and not one of them is engineering. This band is the reason the rest of the board is undatable, so it is the band to hit.
| Due | Ticket | What | Owner role |
|---|---|---|---|
| Mon 24 Aug | T-107 | Correct the repository orientation map and clear the documentation gate that is currently failing | the build-system workstream |
| Tue 25 Aug | T-112 | Allocate decision numbers to the twelve rulings from the 21 August workshop | build sequencing |
| Tue 25 Aug | T-120 | Allocate decision numbers to the four answers given in session on 22 August | build sequencing |
| Wed 26 Aug | T-118 | Amend the project rulebook so an agent may belong to several agencies. The rulebook currently says the opposite and it outranks a ruling made in session, so the requirement is answered and unbuildable until the paragraph changes | the project sponsor |
| Wed 26 Aug | T-113 | Rule on the four unresolved questions about what Phase 1 contains | the project sponsor |
| Wed 26 Aug | T-102 | Decide where the API contract is kept. Explicitly a human call, not something a build agent settles by copying a file | the project sponsor |
| Wed 26 Aug | T-119a | Settle whether the transferring attorney rename reaches two published role names in the API contract | the project sponsor, with the platform API workstream and solution architecture |
| Wed 26 Aug | T-100 | Apply the development environment, create the content-management database user, seed the stored connection secret — three documented steps, in that order | the infrastructure and deployment workstream, with the project sponsor |
| Wed 26 Aug | T-103 | Bring the published deal-lifecycle definition file up to the current version | the platform API workstream |
| Wed 26 Aug | T-104 | Retire the four duplicate aliases carried by four recent decisions | the specification author |
| Thu 27 Aug | T-119b | Execute the conveyancer to transferring attorney rename across the specification library | the specification author |
| Fri 28 Aug | T-114 | Reconcile the two delivery models — retire one | the project sponsor |
| Fri 28 Aug | T-115 | Reissue the API contract's state list against the current lifecycle machine — about 12 hours, and it must happen before the freeze, not after | the specification author, routed by build sequencing |
| Fri 28 Aug | T-101 | Rebuild the product decisions register, with an owner and a due date filled in on every row | build sequencing |
| Fri 28 Aug | T-116 | Rule the directory convention for control-point code, then change the human-review routing rule so it actually reaches that code | build sequencing, then the build-system workstream |
| Fri 28 Aug | T-111 | Issue the ownership row for the two unowned engine projects — promote them, do not rewrite them | build sequencing |
| Fri 28 Aug | T-121 | Accept the Phase 1 structural skeleton (milestone MS1, the acceptance half only) | solution architecture, accepted by the project sponsor |
| Fri 28 Aug | T-105 | Re-approve two subscription register rows under the maker and checker roles — both currently carry no approval | the operations team |
| Fri 28 Aug | T-106 | Retire or rekey the nine communication templates pointing at dead triggers and delete the three that contradict a standing decision — before the conformance run, not after | the communications-template owner |
| Fri 28 Aug | T-108a | Raise the two uncosted commercial decisions with the commercial partner, and name the absorption source for a third | the project sponsor |
| Fri 28 Aug | M1 | Development environment current and the marketing site live — its deployment passes a real smoke check | the infrastructure and deployment workstream |
Band 1 exit criterion, and it is testable. Every one of the four Phase 1 content questions has a written ruling; the API contract has an agreed address; the twelve workshop rulings and the four in-session answers carry decision numbers; the rulebook permits an agent to belong to several agencies; the documentation gate is green; and the marketing site's deployment passes its smoke check against a live development environment.
What is not in band 1 and looks as though it should be. The ticket that makes the build pipeline compile and test the code (T-110) is Ready, is blocked by nothing but sequencing, sits under the whole board — and has no estimate, so it has no date. It is the single most damaging missing number on this plan.
| Due | Milestone | Work | Hours | Workstream |
|---|---|---|---|---|
| Fri 4 Sep | M5 | Azure foundation, infrastructure as code, build-and-release pipelines, monitoring | 18 | the infrastructure and deployment workstream |
| Fri 4 Sep | M20 | Marketing website, templating and content model | 24 | the marketing-site workstream |
| Fri 4 Sep | T-117 | Get the volumes — expected users, leads, deals, documents and peak loads. A decision, not work | — | the project sponsor or the pricing owner |
| Fri 4 Sep | MI1 | Agree observability, service objectives, backup and the data-retention posture, consistent with the retention clocks the rulebook makes database columns. A decision, not work | — | platform operations, accepted by the project sponsor |
Why exactly these two pieces of build work. Three reasons, and all three have to hold. No open decision stands in front of either — the infrastructure item's blocker column names no decision, and the marketing site's reads none on the build. Both carry an estimate, at the second-highest confidence in the estimate file. And both fit inside a single week whichever delivery model is chosen, so their dates do not wait on the delivery model being settled. That is the entire dated build content of Phase 1. Everything else is gated, unestimated, or both.
Two riders, both material. The infrastructure item's 18 hours must also absorb the fix for the build break that stops the solution compiling on the standard build machine — a number sized for infrastructure is being asked to pay for two jobs. And the marketing site's deployment half depends on the 28 August environment milestone landing; its content-model and templating work does not.
One sequence disagreement, openly recorded. These two milestones are dated ahead of the bring-up checklist that the dependency map puts in front of them. The checklist's remaining items are commercial, and none of them physically gates applying infrastructure or creating a content type. If build sequencing holds the arrow as drawn, these dates go and the dated waterfall is band 1 alone — nineteen governance rows and no build work.
Work gated by an unanswered question does not get a date, because a date on unanswered scope makes people build the wrong thing quickly.
The keystone is the API contract freeze. It is roughly two days of work — sixteen hours, at the highest confidence in the estimate file — sitting behind zero other work items and four unanswered questions. Clearing them makes eleven later milestones datable, and five workstreams start the day the freeze lands. The four are: where the API contract is kept; its state list being one version behind the lifecycle machine, which would ship fourteen wrong states into every generated client if frozen as it stands; whether the transferring-attorney rename reaches two published role names, which is a contract change rather than a documentation edit; and whether a moot outcome is a seventeenth deal state against a declared set of sixteen that the API refuses to go outside. Three of the four are band 1 rows. The fourth is being checked and is unsized.
Behind the keystone, in order and without dates: the parallel band of endpoints, engines and screens (M7–M21), the control-point band (M22–M25), and quality and acceptance (M26, M27). M27 — user acceptance complete — is the Phase 1 boundary; production go-live sits outside it.
What has to arrive before band 3 can carry a date at all: the delivery model, the ruling on what Phase 1 contains, an estimate for the bring-up work, and the answer to whether the largest line in the phase still contains the accrual mechanism the lifecycle specification retired — that one alone moves the critical path by up to eighty hours and decides which path is critical.
| Category | Rows |
|---|---|
| dated 22 rows | 19 governance due dates in band 1, milestone M1, and 2 build milestones plus 2 posture decisions in band 2 |
| unscheduled gated by an open decision, finding or action | M0, M3, M4, M6, M9, M10, M11, M12, M13, M17, M19, M21, M22, M24, M25, M26, M27 |
| unscheduled no specification exists to build against | M14, M15, M18, M23 |
| unscheduled no estimate has ever arrived | T-110, M2, the conformance check half of MS1, and the second environment and promotion pipeline half of MI1 |
| unscheduled inside the contested Phase 1 edge | M9, M12, M25, M27 |
Twenty-five product tickets, in the groups the plan uses, plus twenty-two bring-up and governance tickets that sit outside the twenty-five and inside Phase 1. Hours are the engineering lead's estimates as at 22 August 2026; every one of them is marked provisional, because the requirements pass has settled nothing yet.
| Status | Meaning |
|---|---|
| Ready | Specified, unblocked, estimable. Waiting only on sequencing |
| Blocked | A named decision, finding or action stands in front of it |
| Unspecified | Nothing to build against. The shelf is silent |
| Contested | Two live documents disagree about it, or about whether it is Phase 1 at all |
| Deferred | Recommended out of Phase 1, not yet formally out |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-001 dated | Azure foundation, infrastructure as code, build-and-release pipelines, monitoring | 18 | — | The furthest advanced platform work: 35 resources with their infrastructure invariants already written as real unit tests. The second environment has never been applied, and this line must also pay for fixing the build break that stops the solution compiling on the standard build machine. | Blocked |
| T-002 | Database schema, ledger foundation, migrations | 56 | T-001, T-110 | No frame set and no work breakdown exist to build against. The retention rules contradict themselves in their own text — leads purge on a fixed clock and the purge destroys a reason code a report needs. The schema also waits on the rulebook amendment that turns a single membership into a join. | Unspecified |
| T-003 | Identity and role-based access control | 30 | T-001 | One sign-up decision was clarified rather than decided, and the one-time-passcode delivery channel appears in neither the work breakdown nor the marketing plan. Building the passcode path without deciding the channel risks building it twice. | Blocked |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-004 | API contract freeze and mock server — the keystone | 16 | T-121, the structural skeleton, only. Corrected 22 August: it does not wait on the schema or on identity | Four decisions and no upstream work item. Where the contract is kept. Its state list being one lifecycle version behind, which ships fourteen wrong states into every generated client if frozen as it stands. Whether the rename reaches two published role names. Whether a moot outcome is a seventeenth deal state against a closed set of sixteen. The surface is 69 paths, 78 operations and 88 schemas, not the older figure two documents still quote. | Blocked |
| T-005 | Core domain endpoints | 72 | T-004 | The contract freeze. The API today is 41 lines and serves a template weather forecast. | Blocked |
| T-006 | Control points, permissions, audit, ledger writes | 64 | T-004, T-002 | The contract freeze; the delegated-approval register has names but no value limits and no above-limit rule; the highest control point needs three distinct people to exist at all; and the human-review routing rule does not reach the files that enforce the control points, the authority tiers, the maker-and-checker comparison or any of the thirteen refusal codes. | Blocked |
| T-007 | Configuration-plane minimum | 0–40 | T-004 | May not be a Phase 1 line at all. An earlier decision closed the standalone configuration area, so this is either real and unbudgeted, or a double count of something already closed. One of the four unresolved Phase 1 content questions. | Contested |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-008 dated | Marketing website, templating, content model | 24 | T-001 | Nothing on the build. One content type and one template exist today. Deployment waits on the three documented human steps that put the site onto the development environment. | Ready |
| T-009 | Calculator and lead-capture forms | 24 | T-008, T-010, T-005 | The pricing engine and the API are both blocked. Every form must post to the platform API and never to the website, so that actor stamping, consent versioning and the lead-retention clock stay on platform tables. What separates a visitor from a lead from a deal was raised in the workshop and deliberately not settled, and that decides what the retention clock attaches to. | Blocked |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-010 | Versioned pricing and calculator engine | 56 | T-004 | Six open pricing decisions: the early-settlement basis and its floor; whether quotes persist; whether the priced term is the shorter or the longer one, where the input schema caps at the shorter and a validated specification refuses the longer quote; seven vocabulary forks, and the test harness will not bind until one is chosen; one fee recorded two ways with a tenfold difference between them, which is not a rounding question; and three live documents taking three positions on whether a manual override ships at all. Two pricing models with different shapes sit in the repository, so there is no single pricing source to build from. | Blocked |
| T-011 | Deal state machine, componentised, refusals first-class | 48 | T-004, T-002, T-110 | Eleven of the thirty-two transition routes are drawn by no diagram, so every route out of a hold is currently one-way. The claim acquisition has no state boundary and no audit line, and it is the moment the money is at risk. The reference implementation does not compile, so the invariant that proves the lifecycle cannot reach a dead end has never once executed. | Blocked |
| T-012 | Event engine — email, Teams and webhook delivery | 88 | T-011 | Six template and seed-data decisions plus two register actions, one of which must run before the other. Of 123 templates, 111 name channels that belong to a later phase, leaving twelve — and nine of those twelve fire on trigger events the current design no longer produces. Three requirement rows still carry later-phase markings after the 15 August scope change, and one of them does not name Teams, which is one of the three Phase 1 channels. The scope change was never re-cut into the envelope. | Contested |
| T-013 | In-life financial engine — certificate of balance, settlement, in-life events | 60–140 | T-010, T-014 | The largest line in the phase, priced for a mechanism the current lifecycle specification retired. Nothing accrues any more. The certificate of balance, settlement (early, partial and full), suspense and the two bracket clocks survive; the daily accrual machinery and the day-count engine, which is where the bulk of the hours sat, do not. Nobody has asked the question, and it moves the critical path by up to eighty hours. | Contested |
| T-014 | Purchase-model ledger rework | 44 | T-002 | No specification on the shelf. The invariants are fixed by the rulebook: the ledger is append-only and corrections post as reversals, never as edits. | Unspecified |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-015 | Component library | 48 | T-004 | No specification exists on the shelf. The shared library has to be built host-agnostic and before the mobile head, or the external web head's estimate reverts from about 52 hours toward 144. The device seam — file pick, camera, token store — is undesigned. | Unspecified |
| T-016 | Staff back-office screens — parties, deals, workflow, documents | 60 | T-015, T-005 | No specification exists on the shelf. | Unspecified |
| T-017 | Review, approval and reporting screens | 30 | T-015, T-006 | Per-field verification against the source region, and the three-person approval floor. The review screen is Phase 1 while the document extraction it reviews belongs to a later phase, so it is built once against manual keying and revisited when extraction arrives — and that second visit is in nobody's plan, in either phase. | Blocked |
| T-018 | External web host head, for agents and agencies | 52 | T-015 | No specification exists on the shelf. The surface is confirmed in scope at about 52 incremental hours, absorbed rather than quoted, and where the absorption comes from has never been recorded. The render-mode contract between the shared library and the host does not exist. | Unspecified |
| T-019 | Practice portal surface — notices, acknowledgements, matters | 40 | T-011 | The 21 August workshop replaced the design and the replacement is unregistered, so it cannot be built from. Verification is a status on the deal across four parties, not a cycle on three separate party records, which is what the currently scheduled release builds. A lapsed certificate has no cure: the deal is re-originated and the lead survives. | Unspecified |
| T-020 | Deal timeline | 20 | T-011, T-012 | It renders the state-machine transition rows and the event-engine timeline records and nothing it invents, so both engines being blocked blocks it. | Blocked |
Every change in this group requires a named human reviewer. No agent may build a path that skips, defaults or auto-completes a control point, including for testing. The routing rule that enforces the human reviewer does not currently reach this code, which is band 1's T-116.
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-021 | Verification callbacks and registries | 50 | T-006 | An uncosted commercial decision that appears in nine screens and has no line in the hour table. Whether a verified, locked bank account carries to the next deal or is re-verified — it touches a control point, so it is a control decision, not a convenience. And how the platform learns that a property registered, because that date anchors the event engine and starts the chase cadence. | Blocked |
| T-022 | Bank-account locking and the high-risk change workflow | 20 | T-006 | The specification is silent. The invariants are fixed by the rulebook regardless: locked once verified, a change requires a fresh verification callback, a maker and a separate checker, a cool-off period, and never a direct update on the record. | Unspecified |
| T-023 | Cession and basic electronic signature | 88 | T-006, T-015 | Uncosted, and re-scoped on 21 August before it was ever costed: the cession is not a standalone instrument, the document set is three rather than four, and terms are agreed at application, before the offer. Whether the general cession over future commission remains withdrawn was queried and has had no written answer. | Contested |
| T-024 | Practice super-user surface for attorney firms | 52 | T-019 | Inside the twenty-five and simultaneously recommended out of them — one of the four unresolved Phase 1 content questions. Uncosted and undesigned. No agent may invent this surface; it is storyboarded first or it is deferred. | Deferred |
| Ticket | Work | Hours | Depends on | What is blocking it | Status |
|---|---|---|---|---|---|
| T-025 | Test pack, request collection, user-acceptance support | 18 contracted / 80+ real | T-110 first | There is no pipeline job that compiles the code, so there is nothing for a test suite to be green in. The event-engine conformance run has never executed against the whole subscription register and is expected to fail loudly — that is the intended outcome, and the size of the resulting defect list is unknown until it runs. The subscription register itself is not in this repository. The line buys a request collection rather than a test suite, and the two plans disagree about who authors the suites. And without volumes, the non-functional targets cannot be tested at all. | Blocked |
Not product scope. These are what the build rules ask for before the product build starts, and every one of them is still open. Twenty-two rows; the great majority are Ready and most are decisions rather than work.
| Ticket | Work | Owner role | What is blocking it | Status |
|---|---|---|---|---|
| T-110 | Make the build pipeline compile and test the code — build and test as required checks, a migration dry-run, and an extraction evaluation. The solution does not build on the standard build machine because the mobile project targets a platform the machine has no toolkit for: provision it or split the target. Also fix or remove the quality gate that passes without checking anything | the infrastructure and deployment workstream owns the pipelines; build sequencing places the ticket | Nothing but sequencing. The build rules already require it, and it has no estimate, so it has no date. | Ready — and it sits under the whole board |
| T-100 dated | Apply the development environment, create the content-management database user, seed the stored connection secret — three documented steps, in that order | the infrastructure and deployment workstream, with the project sponsor | Nothing. It needs a performer and an hour, and it puts the first application code into an environment. | Ready |
| T-111 dated | Fix the one missing property that stops the lifecycle engine compiling, bring both engine projects into the solution and into the pipeline, retarget them to the house platform version and restore the strict-warning setting | the platform API workstream, once build sequencing assigns ownership | Build sequencing owes an ownership row: neither project is named in any ownership table. Promote the code, do not rewrite it — it encodes about a month of design that has already been paid for. | Blocked on the ownership row |
| T-118 dated | Amend the rulebook so an agent may belong to several agencies. The rulebook says memberships are exclusive; the sponsor ruled the opposite on 22 August. The rulebook wins, so the requirement is unbuildable until this lands | the project sponsor — his to make, not a build agent's | Nothing. One paragraph. It blocks the database schema, which heads the whole build sequence, and it makes a membership deal-scoped, which reaches the verification work. | Ready |
| T-119 dated | Execute the conveyancer to transferring attorney rename across the library — and settle first whether it reaches two published role names, because renaming a published value is a contract change, not a documentation edit | the specification author; the project sponsor with the platform API workstream and solution architecture on the published-value question | Nothing. The only item on this board whose cost rises with delay rather than merely arriving later: cheap today, 516 template edits once the template pack is drafted, and a breaking change across five workstreams once the contract freezes. Do it now. | Ready |
| T-120 dated | Allocate decision numbers to the four answers given in session on 22 August | build sequencing | Nothing. An answer cited to a conversation is a weaker citation than a register row and cannot be built from. | Ready |
| T-121 dated | Agree the Phase 1 structural skeleton and land its conformance check — the check must fail when a module references another the wrong way round | solution architecture, accepted by the project sponsor | Nothing on the acceptance half, which is dated. It gates seven milestones including the contract freeze and the component library: nothing in the build starts before the shape it lands in is agreed. The conformance-check half has no estimate and no date. | Ready |
| T-122 | Environment readiness — the second environment applied from the same program, the promotion path built as a pipeline rather than designed on paper, and a data-retention posture consistent with the retention clocks the rulebook makes database columns | platform operations, with the project sponsor for anything needing a human step | Code cannot land in an environment that does not exist. The retention half is dated in band 2 as a decision; the second environment and the promotion pipeline have no estimate and no date. | Ready |
| T-101 dated | Rebuild the product decisions register, with an owner and a due date on every row | build sequencing | Asked for at week zero and never delivered. Ten of the blocking rows currently have no owner or no due date, and on this project the decisions with a person's name on them close inside a day. | Ready |
| T-112 dated | Allocate decision numbers to the twelve rulings from the 21 August workshop | build sequencing | Nothing — the extraction and the citations are already done. Highest value on this board: one sitting settles origination outright, changes the shape of the verification design, re-scopes the cession work and settles part of the rename. | Ready |
| T-102 dated | Decide where the API contract is kept | the project sponsor | A human decision, explicitly not a build agent's to settle by copying a file. The keystone cannot have an exit criterion until the artefact has an address. | Ready |
| T-113 dated | Rule on the four unresolved questions about what Phase 1 contains — the two service clocks; the three requirement rows still marked for a later phase; whether the configuration plane is a real line or a double count; whether the practice super-user surface is in or out | the project sponsor | Nothing. Where two documents disagree the rule is to stop and report, never pick a side, so no side has been picked. Nothing inside Phase 1 can be committed until this lands. | Ready |
| T-114 dated | Reconcile the two delivery models — retire one | the project sponsor | Commercial, not technical. Every date this plan will ever carry sits behind it. | Ready |
| T-115 dated | Reissue the API contract's state list against the current lifecycle machine, before the freeze | the specification author, routed by build sequencing | Nothing. Freezing as it stands ships fourteen wrong states into every generated client, and honouring them later is a breaking change on the most consequential artefact in the repository. | Ready |
| T-116 dated | Make the human-review routing rule reach the control-point code — rule the directory convention, then change the file | build sequencing, then the build-system workstream | The convention nobody has committed to. Today the transition authority, the authority tiers, the maker-and-checker comparison, the delegation check and all thirteen refusal codes sit at paths no rule matches, so those files need no human reviewer at all. | Blocked on the ruling |
| T-103 dated | Bring the published deal-lifecycle definition file up to the current version | the platform API workstream | Nothing. Its two neighbours were mirrored on 20 August and this one was missed. | Ready |
| T-104 dated | Retire the four duplicate aliases carried by four recent decisions | the specification author | Nothing. A find-and-replace across four files, and cheaper before the register grows further. | Ready |
| T-105 dated | Re-approve two subscription register rows under the maker and checker roles | the operations team | Both rows carry no approval: a channel change voided the approvals their earlier versions were published under, so neither can publish. | Ready |
| T-106 dated | Retire or rekey the nine communication templates pointing at dead triggers, and delete the three that contradict a standing decision | the communications-template owner | Nothing, except ordering: it must run before the conformance run, not after. Deleting templates does not fix a lifecycle machine that cannot represent an expired certificate. | Ready |
| T-107 dated | Correct the repository orientation map — twelve of the paths it draws do not exist, the shelf map points at the wrong place, the API surface figure is stale, and the documentation gate now fails because two new planning roles have no row in its table | the build-system workstream | Nothing. The gate is red now, and this is the one document a new contributor is told to read before touching anything. | Ready |
| T-108 dated | Name the absorption source for the external web portal's incremental hours, and raise the two uncosted commercial decisions with the commercial partner | the project sponsor | Outstanding since week zero. Roughly 52 hours are being absorbed from somewhere unnamed, and whoever eventually pays for them has not agreed to. | Ready |
| T-117 dated | Get the volumes — expected users, leads, deals, documents and peak loads | the project sponsor or the pricing owner | Nothing. Four non-functional targets have read to be advised since the specification was first issued, and Phase 1 ends at user acceptance. Cheapest item on the list and the last one anyone will remember. | Ready |
| Band | Dates | Tickets | Kind |
|---|---|---|---|
| 0 | Sat 15 – Fri 21 Aug 2026 | none | Consumed. Shelf clear-out, decision reconciliation, the workshop. No product ticket started |
| 1 | Sat 22 – Fri 28 Aug 2026 | T-107 (24 Aug) · T-112, T-120 (25 Aug) · T-118, T-113, T-102, T-119a, T-100, T-103, T-104 (26 Aug) · T-119b (27 Aug) · T-114, T-115, T-101, T-116, T-111, T-121, T-105, T-106, T-108a (28 Aug) | Dated. Nineteen due dates on named owners. Decisions and governance, no engineering |
| 2 | Sat 29 Aug – Fri 4 Sep 2026 | T-001 (18 h) · T-008 (24 h) · T-117 · the retention posture half of MI1 | Dated. The only product build work with a date, and the only two rows that survive all three blocking rules |
| 3 | — | T-004 — 16 hours behind zero work items and four decisions | Unscheduled. Datable the day the contract's home, its state list, the published-name question and the seventeenth-state question all close |
| 4 | — | T-002, T-003, T-005, T-006, T-007, T-009, T-010, T-011, T-012, T-013, T-014, T-015, T-016, T-017, T-018, T-019, T-020 | Unscheduled. The parallel band, all of it behind the contract freeze |
| 5 | — | T-021, T-022, T-023, T-024 | Unscheduled. Control points and high-risk flows |
| 6 | — | T-025 | Unscheduled, and behind T-110 — there is no pipeline for a test suite to be green in |
| none | — | T-110 · the build half of T-111 · M2 · the conformance-check half of MS1 | Unscheduled for want of an estimate, not for want of an answer. These sit under the whole board |
The inversion worth reading twice. The dated rows are the ones nobody is waiting on, and the undated rows are the ones everything waits behind. The ticket that makes the pipeline compile the code is ready, blocked by nothing but sequencing, required by the build rules — and it has no number, so it has no date. It is the cheapest thing on this board to fix.
| Measure | Count |
|---|---|
| Phase 1 product tickets | 25 |
| Ready — T-008, and its deployment waits on the three human steps | 1 |
| Blocked by a named decision, finding or action | 12 |
| Unspecified — nothing to build against | 7 |
| Contested — two live documents disagree, or the Phase 1 edge does | 4 |
| Deferred | 1 |
| Carrying an estimate, as at 22 August | 25 of 25 |
| Bring-up, structural and governance tickets outside the twenty-five | 22 |
| Estimated hours in front of the contract freeze, and no other ticket | 16 |
Six planning roles run continuously. The build workstreams are assigned band by band. Which workstream builds what within a band is set by build sequencing and is not fixed by this page.
| Role | Owns | Load in band 1 |
|---|---|---|
| Delivery management | The schedule, the risk log, the status report and the ticket board | The board, and getting it published |
| Requirements | The requirements pass and the open-questions log | Whether a moot outcome is a seventeenth deal state. It gates the keystone |
| Engineering lead | The architecture read, the estimates and the product architecture records | The bring-up estimate that nobody has, and the re-estimate of the largest line once the accrual question is answered |
| Solution architecture | The structural skeleton and its conformance check | Skeleton accepted (T-121). The conformance check itself is unscheduled |
| Platform operations | The infrastructure plan and the operations posture | Retention posture agreed in band 2. The second environment is unscheduled |
| Client account management | External wording and the client relationship | How the consumed first week and the two delivery models are described outside the build |
| Band | Workstream | Milestones and tickets |
|---|---|---|
| 1 | Build sequencing | T-112, T-120, T-101, T-116, T-111, and routing T-115 — five of the nineteen band-1 rows |
| 1 | The build-system workstream | T-107, and the human-review routing change once the convention is ruled |
| 1 | The platform API workstream | T-103 |
| 1 | The infrastructure and deployment workstream | T-100, and milestone M1 |
| 2 | The infrastructure and deployment workstream | M5 — Azure foundation, 18 hours |
| 2 | The marketing-site workstream | M20 — marketing website, 24 hours |
| 3 | The platform API workstream | M6 the contract freeze — unscheduled, four decisions in front of it |
| 4 | The infrastructure and deployment workstream | M3 schema, M4 identity — unscheduled |
| 4 | The platform API workstream | M7 to M13 — endpoints, control points, configuration, pricing, lifecycle, events, in-life finance — unscheduled |
| 4 | The staff back-office workstream | M14 component library, M15 back office, M16 review, M17 timeline — unscheduled |
| 4 | The external-screens workstream | Every external screen, including those the web host shows, and M19 — unscheduled |
| 4 | The external web host | M18 hosting only — no screen is defined here |
| 4 | The marketing-site workstream | M21 calculator and lead-capture forms — unscheduled |
| 4 | The mobile app workstream | Not a Phase 1 milestone on this board. An iOS build needs a build machine that does not yet exist |
| 5 | Platform API writes, external screens render | M22 to M25 — all unscheduled |
| 6 | The test and acceptance workstream | M26 integration and end-to-end suites, the pipeline gate, and the request collection — unscheduled behind the pipeline that compiles the code |
| all | Craft review, compliance review and merge | Continuous, on every change |
| Owner role | Band-1 rows | Note |
|---|---|---|
| The project sponsor | T-118, T-113, T-102, T-119a, T-114, T-108a, the human steps in T-100, accepting T-121, and T-117 in band 2 | Nine of the twenty-two dated rows are one person's. Every decision carrying his name has closed inside a day, and that record is the basis for putting them all in one week |
| Build sequencing | T-112, T-120, T-101, T-116, T-111, and routing T-115 | Also owes the ownership row for the two unowned engine projects, and the directory convention behind the human-review rule |
| The specification author | T-104, T-119b, T-115 | Not a build workstream. The rename is the one item whose cost rises with delay |
| The build-system workstream | T-107 | The documentation gate is red today |
| The infrastructure and deployment workstream | T-100, milestone M1 | Then the Azure foundation in band 2 |
| The operations team | T-105 | Two register rows cannot publish until they are re-approved |
| The communications-template owner | T-106 | Must run before the conformance run, not after |
| Solution architecture | T-121 | Accepted by the project sponsor. Gates seven milestones |
| The pricing owner | — in band 1; T-117 with the project sponsor in band 2 | The early-settlement basis and floor sit behind this role and carry no date |
| The legal adviser | — | A tax opinion is outstanding and bears on the pricing basis |
| The commercial partner | — | Two uncosted decisions are raised on 28 August. Their answer is external and carries no date |
Capacity, stated plainly. Band 1 is nineteen decisions across seven owners in five working days, nine of them one person's. It is achievable — the evidence is seven decisions raised and closed by the same person inside 48 hours on 15 and 16 August — but it is the tightest thing on this plan, and there is no capacity model behind it.
On 15 August 2026 the product specification shelf was deliberately cleared — the decisions register, the screen frame set, the work breakdown and the product architecture records — and it is being written again. The Phase 1 scope document states the consequence plainly: a work item now says what to build but not to what specification. That is why seven of the twenty-five tickets are marked Unspecified.
It was the right call, and it should be read as a deliberate reset, which is what it was. The alternative was building quickly against a specification nobody trusted, on a platform that pays out money under South African financial-services and privacy law. That was judged the more expensive option and it was declined on purpose. The honest way to state the position is that Phase 1 restarted its specification seven days ago.
Two things moved the other way on the same day, and both add scope. The event engine moved from the later phase into Phase 1 in full and the fixed commercial envelope was never re-cut, so it arrives already blocked, with 111 of its 123 templates written for channels that belong to a later phase. And the external web portal was confirmed in scope at roughly 52 incremental hours, absorbed rather than quoted, with the absorption source never recorded. Set against a genuine head start of about 65 hours on infrastructure, the lifecycle machine and the marketing site, Phase 1 is slightly larger than the plan it is being measured against, not smaller.
Seven things, in the order that releases the most. None is a week's work, and none of it is engineering.
Until the first four of those land, this page is a dependency map rather than a plan. It carries no end date, no duration and no commitment, and it must not be quoted as one. With the delivery model settled and the Phase 1 edge agreed, it produces dates the same day.