Empire Teas CRM — Features
Live index of all features in the engagement.
Regenerated by
/forge-decomposefull mode — Gate 3 Run 1, 2026-09-17 (verdictpass, Tharinda). Two dry-runs preceded it (2026-09-17): the first proposed 58 features; the second, on the lead’s finer-cut instruction, 89. The audit, the FR-5 sizing table and the checklist walk are inengagement-gate-runs.md § Gate 3 Run 1.Source-of-truth model:
- This file = human/agent-readable index. Easy to scan, link from conversation, and pick up at the start of a feature session.
tracker.yamlfeatures:block = structured state. Drives gate logic and leadership visibility.- Per-feature spec at
.forge/specs/<id>-<name>-spec.md= full description, requirements, acceptance criteria (stubs created at Gate 3; a stub isStatus: draftuntil/forge-deliverauthors and reviews it).The PRD’s §In Scope is a Gate-1-approved snapshot — do not edit it to reflect live state; reflect live state here instead. The PRD’s F-numbers survive as the parent of each sibling id here (
F5-a…F5-hare all PRD F5); the FR-5 table records which cut produced each sibling.Foundation slices (the backlog in
architecture.md § Foundation Backlog) live undersetup.foundationintracker.yaml— scaffolding, not user-visible features; they do not appear here. The trade-show capture app is F36 (six siblings at Gate 3; F36-e and F36-f were dropped on 2026-10-11, and the four that remain moved from Phase 2 to Phase 1 on 2026-11-11): a companion application at full scope (Option C, decided 2026-08-18), with F36-a (capture-and-feed) as the client-side descope lever.
Slicing Principle
By capability, cut vertically, phased by the lead’s instruction — and cut to the size one developer can build and one reviewer can verify end to end in a short cycle. Each feature is one user-verifiable capability with its backend and frontend. Where a PRD row carried several such capabilities, each became its own feature. Substrate pieces (-a siblings with no screen: F1-a, F2-a, F11-a, F20-a, F26-a) are kept where they unblock the other two lanes; they are verified through API tests and by the first screen that consumes them.
Rejected alternatives: by module (a backend/frontend split contradicts the vertical-slice rule); by user journey (journeys A–E each cross six or more features and would become epics); one feature per PRD row (F5, F11, F20 and F26 each carry eight to twelve capabilities and would stall the other two developers on their substrate); and the first dry-run’s own leaning — cut only where a cut buys parallelism or phase placement — rejected because the lead wants small deliverables (CLAUDE.md § Active Context, Gate-3 standing instruction).
Eleven splits were marked ◐ at Gate 3: the team accepted all of them (Gate 3, Q16-A) but they are the ones to merge back first if the per-feature overhead (spec, spec review, wave plan, plan review) bites. Three pairs were merged back on 2026-10-11 (lead): F15-b into F15-a, F17-b into F17-a and F18-b into F18-a; F7-e, F23-c and F36-e were dropped the same day. The rest still carry the mark. Merging every one gave 78 at Gate 3 (F5-i, F5-j, F5-k and F39, added afterwards, are not splits; F38-a … F38-i, split from the F38 spec on 2026-09-27, are not marked ◐ either).
Source: PRD §Scope and Boundaries + §Functional Surface (Rev 32); the lead’s Phase 1 / Phase 2 instruction (2026-09-13, clarified 2026-09-16); the two dry-run reports (gate3-dry-run-2026-09-17.md, -rev2.md, held outside the repo).
Delivery Plan
Two delivery phases, matching the client’s two UAT rounds (client/project-timeline.md). The split follows the lead’s instruction rather than the proposal’s P0/P1a grouping — deals, Kanban and dashboards sit in Phase 2 (global search with them, until it was dropped on 2026-10-11) — a divergence recorded as a post-issue note on the proposal header and a project-timeline.md §2 revision (Gate 3 finding 2, confirmed by the team 2026-09-17). Dates are set separately by /forge-set-dates.
| Phase | Title | Theme | Features |
|---|---|---|---|
| 1 | Users, accounts, leads, email, weekly prices and the capture app | Sign in with Microsoft; run users, roles and the reporting hierarchy; work accounts, contacts and leads migrated from Pipedrive with AI research, ranking, summaries and drafted follow-ups; follow-up tasks on leads and accounts; email and templates inside the CRM, linked to the matching accounts, contacts and leads, with open and click tracking, scheduled send and a follow-up for a customer email nobody has replied to; keep each account’s buying standards, publish the weekly prices and send each customer theirs, one at a time or all at once; share records with colleagues; list views with saved filters, file attachments and custom fields on accounts, contacts and leads; plan a trade show and capture its contacts on a phone with the capture app, read, researched and ranked by AI and fed into the leads; an audit trail of every change; the dev and UAT environments on AWS. Started early, and part of Phase 1 only once done: export of the account, lead and contact lists, bulk email to a saved contact list, email block lists, contact sync, and the production environment (by its own rule) | 80 in scope as of 2026-11-20 — F5-a…l, F1-a/b/c/d/e/f, F13, F11-a/b/c/d/f/g/h/i/j, F12, F3-a, F20-a/b/c/d/f/h/i/j/l, F4-a/b/d, F32-c, F26-a/b/c/d/f/g, F38-a…j, F39, F40, F41, F42, F43, F44, F45, F46, F36-a/b/c/d (the capture app), F34-c (accepted with Phase 1 since 2026-11-11), F33-a (accepted with Phase 1 since 2026-11-12), F20-g, F32-d and F37-a (accepted with Phase 1 since 2026-11-18), and, started early (each moves to Phase 2 if it is not done by the end of Empire’s Phase 1 UAT round — the lead, 2026-11-19), F23-d, F37-b, F20-k and F22; plus F20-e, F4-c, F31, F7-e, F16, F26-e, F23-c, F36-f and F36-e, dropped, and F15-b, F17-b and F18-b, merged into their -a items; and F27, F28, F29, F30 and F35, out of V1 since 2026-08-20 and dropped on 2026-10-11 (PRD Rev 66); all recorded here (37 at Gate 3; F5-i and F38 added 2026-09-23, F5-j, F5-k and F39 2026-09-24, F38-a…h, F40 and F5-l 2026-09-27, F32-c and F41 2026-09-30, F38-j 2026-10-02, F1-f 2026-10-08, F20-h 2026-10-12, F20-i, F20-j and F20-k 2026-10-17, F20-l 2026-10-26, F42 2026-10-27, F43 2026-11-02; F38-i moved in from Phase 2 on 2026-11-02 while its code waves are worked; F20-g, F22 and F37-a moved in from Phase 2 on 2026-11-06, and F32-d, F23-d, F33-a and F34-c were split that day from F32-a, F23-a, F33 and F34-a as the parts that need no deals (lead: Tharinda, to start them in Phase 1’s time); F36-a, F36-b, F36-c and F36-d, the capture app, moved in from Phase 2 on 2026-11-11 as firm Phase 1 scope (lead: Tharinda; agreed with Empire at the 10 November progress meeting); F44 added 2026-11-12 from Empire’s ask at the same meeting (lead: Tharinda); F45 added 2026-11-12 from the code review of 2026-11-08 (lead: Tharinda); F46 added 2026-11-14 from the file-size check (lead: Tharinda); F11-i added 2026-11-17 from Empire’s answer at the 10 November progress meeting (Dinil); F11-j added 2026-11-19 from the lead’s decision of the same day on criterion E8 (Tharinda); F20-g, F22 and F23-d moved back to Phase 2 on 2026-11-11, not done, and F20-k with them (lead: Tharinda); F20-g was taken back into Phase 1 the same day by Dinil, its owner, to finish it; F37-a moved back the same day, not started; F37-a and F23-d were taken back into Phase 1 on 2026-11-15 by Tharinda (lead), to start them, on the same terms; F37-b was taken into Phase 1 on 2026-11-19 by Tharinda (lead), to start it, on the same terms; F20-k and F22 were taken back into Phase 1 on 2026-11-20 by Tharinda (lead), to start them, on the same terms; F20-e, F4-c, F31, F7-e, F16, F26-e, F23-c, F36-f and F36-e moved in from Phase 2 when dropped, and F15-b, F17-b and F18-b when merged; F38’s own row removed 2026-10-11 — its spec stays as the requirements its sibling items narrow, as the PRD does for the other split features) |
| 2 | Deals, tea workflows and parity | Pipelines and deals, activities on deals, samples, product briefs, quotes and the tea-export workflow, dashboards, alerts and AI briefings, outreach sequences, the activity calendar and two-way calendar sync, list views, attachments and custom fields on deals, quotes, buying standards and samples, bulk actions, spreadsheet import and the export of those lists, the ERP handoff | 34 in scope as of 2026-11-20 (52 at Gate 3; F20-e dropped 2026-09-24, F4-c 2026-09-30, and F31, F7-e, F16, F26-e, F23-c, F36-f and F36-e 2026-10-11, and F15-b, F17-b and F18-b merged into their -a items 2026-10-11, all now recorded in Phase 1; F38-i added 2026-09-27 and moved to Phase 1 on 2026-11-02; F37-a and F37-b added 2026-10-09; F20-g, F22 and F37-a moved to Phase 1 on 2026-11-06; the same day F33 was split into F33-a (Phase 1) and F33-b, and F32-a, F23-a and F34-a were narrowed to deals, their other parts split to Phase 1 as F32-d, F23-d and F34-c; F36-a, F36-b, F36-c and F36-d, the capture app, moved to Phase 1 on 2026-11-11; F20-g, F22 and F23-d moved back from Phase 1 on 2026-11-11, not done, and F20-k with them (lead: Tharinda); F20-g returned to Phase 1 the same day; F37-a moved back the same day, not started; F37-a and F23-d returned to Phase 1 on 2026-11-15 (lead: Tharinda); F37-b moved to Phase 1 on 2026-11-19 (lead: Tharinda); F20-k and F22 returned to Phase 1 on 2026-11-20 (lead: Tharinda)) — F2-a/b/c/d, F11-e, F3-b, F17-a, F24, F18-a, F6-a/b/c, F7-a/b/c/d, F8-a/b, F9, F10, F14, F15-a, F19, F21-a/b, F32-a/b, F23-a/b, F33-b, F34-a/b, F25-a/b |
Two Phase 1 placements go against the lead’s rule and were taken by team decision with the lead’s confirmation (Gate 3, Q7-B and Q8-B, 2026-09-17): F3-a (follow-up tasks on leads and accounts — the parallel run would otherwise have leads without reminders, the stated number-one Pipedrive pain) and F20-d (email templates — with a predefined weekly-prices template, so the price send does not hand-roll its body). F37 (bulk email), a stretch row at Gate 3, was committed to Phase 2 on 2026-10-09 as F37-a and F37-b (PRD Rev 57), against a Phase 2 descope still to be agreed with Empire. Started early, 2026-11-06 (lead: Tharinda): because Phase 2 does not fit its date on its own (R-ARCH-001), the Phase 2 work that needs neither deals nor the capture app is tracked in Phase 1 — F20-g, F22 and F37-a as they are, and the account, lead and contact parts of list views, export, attachments and custom fields as F32-d, F23-d, F33-a and F34-c (split from F32-a, F23-a, F33 and F34-a, which keep the parts for deals and the other Phase 2 records — quotes, samples, buying standards, product briefs; F33 became F33-a and F33-b). Phase 1’s own work, fixes and release still come first (R-ARCH-001); each of the seven moves back to Phase 2 before Phase 1 seals unless done, as F38-i does, and none is in the Phase 1 acceptance criteria unless it is done by then. Moved back, 2026-11-11: F20-g, F22 and F23-d, none of them done, are back in Phase 2 (F20-g released by Dinil, its spec and wave-1 PRs left open for whoever takes it), and F20-k, a Phase 1 item since 2026-10-17, moved to Phase 2 with them (lead: Tharinda). F37-a, the weekly price broadcast, moved back the same day, not started (released by Dinil), and returned to Phase 1 on 2026-11-15, started early on the same terms (lead: Tharinda). Taken back, 2026-11-15 (lead: Tharinda): F23-d, the export of the account, lead and contact lists, returned to Phase 1 the same day, claimed by Tharinda to start it now that its blocker F32-d is done. Started early, 2026-11-19 (lead: Tharinda): F37-b, bulk email to a saved contact list, moved to Phase 1 to start it now that F37-a, F32-d and F20-g are done; the delivery team decides OQ-62 in its spec. When an unfinished started-early feature moves back, 2026-11-19 (lead: Tharinda): F23-d and F37-b stay in Phase 1 through Empire’s Phase 1 UAT round (drop 1 about Mon 30 Nov, drop 2 during the testing); each one not done by the end of that round moves to Phase 2. This replaces “before Phase 1 seals” in the notes above for these two; F38-i keeps its own rule. Taken back, 2026-11-20 (lead: Tharinda): F20-k (email block lists, after F20-f) and F22 (contact sync, after F20-i) returned to Phase 1 to start early on the same terms: each finished one goes out in a later Phase 1 UAT drop and joins the Phase 1 acceptance criteria, and each one not done by the end of the round moves to Phase 2. The capture app in Phase 1, 2026-11-11 (lead: Tharinda): at the 10 November progress meeting Empire asked for the capture app in Phase 1, for its January 2027 trade fairs (discovery/meeting-notes/2026-11-10-kavindu-crm-progress-update-demo.md), and the delivery team and Empire agreed it. F36-a, F36-b, F36-c and F36-d are firm Phase 1 scope, due with the rest of Phase 1 (tracker.yaml phases); unlike the started-early items they do not move back to Phase 2. The Phase 1 acceptance criteria, the client-facing documents, the PRD, AD #20’s row and the capture app’s UAT hosting still describe it in Phase 2 and are updated as follow-ups (owed.md). Owners are not assigned at Gate 3 (Q14-B); the lanes under the dependency graph are the division plan.
Dependency Graph
graph TD
subgraph P1["Phase 1 — users, accounts, leads, email, weekly prices, capture app"]
F5a["F5-a Sign in / out"] --> F5b["F5-b App frame"]
F5b --> F5c["F5-c Users + manager"]
F5b --> F5d["F5-d Roles editor"]
F5c --> F5e["F5-e Permissions viewer"]
F5d --> F5e
F1a["F1-a Account/contact substrate"] --> F1b["F1-b Account list + create/edit"]
F5b --> F1b
F1b --> F1d["F1-d Account detail + contacts"] --> F1e["F1-e Notes + tags"] --> F1c["F1-c Timeline + dormancy"]
F1d --> F1f["F1-f Contacts page"]
F1c --> F13["F13 AI account briefing"]
F1a --> F11a["F11-a Lead substrate + intake"] --> F11b["F11-b Lead inbox list"] --> F11f["F11-f Lead detail"]
F5b --> F11b
F11b --> F12["F12 AI extraction (AIProvider)"]
F12 --> F13
F12 --> F11c["F11-c Research job (SearchProvider)"] --> F11g["F11-g AI ranking + hot/cold"]
F11f --> F11c
F12 --> F11d["F11-d Summary + spam/dup"]
F12 --> F11h["F11-h Drafted follow-up"]
F12 --> F42["F42 Bedrock call pacing"] --> F4b
F42 --> F43["F43 AI load under the quota"]
F20c --> F11h
F1d --> F3a["F3-a Tasks on leads + accounts"]
F11f --> F3a
F5b --> F20a["F20-a Mailbox connection (MailboxProvider)"] --> F20b["F20-b Inbound sync + inbox"] --> F20i["F20-i Live inbox"] --> F20f["F20-f Auto-link + timeline"]
F1c --> F20f
F11f --> F20f
F20f --> F20j["F20-j Past-mail linking"]
F20f --> F11j["F11-j Migrated-lead summaries"]
F20f --> F44["F44 Unreplied email follow-up"]
F3a --> F44
F4d --> F20l["F20-l Contact email addresses"] --> F20f
F20a --> F20c["F20-c Compose, reply, send"] --> F20d["F20-d Templates + merge fields"]
F1d --> F20c
F1a --> F4a["F4-a Import engine (dry-run)"] --> F4d["F4-d Migrate orgs + people"] --> F4b["F4-b Migrate leads"]
F11a --> F4b
F1a --> F26a["F26-a Standards + price substrate"] --> F26b["F26-b Standards book"]
F26a --> F26c["F26-c Workbook upload"] --> F26f["F26-f Review + publish"] --> F26g["F26-g Expiry + override"]
F26f --> F26d["F26-d Send this week's prices"]
F20d --> F26d
F26b --> F26d
F5k["F5-k Access-model realignment"] --> F5c
F39["F39 Audit trail"] --> F5c
F5k -.->|wave 1 only, on main| F5l["F5-l Reach from the reporting line"]
F5l --> F5f["F5-f Ownership + sharing substrate"]
F5l --> F5d
F5f --> F1b
F5f --> F11b
F5f --> F5g["F5-g Record sharing screens"]
F5c --> F5h["F5-h Offboarding (bulk reassign)"]
F5f --> F5h
F20a --> F5h
F20c --> F20h["F20-h Email attachments"]
F1b --> F32d["F32-d List views: accounts, leads, contacts"]
F11b --> F32d
F1f --> F32d
F32d --> F23d["F23-d Export: accounts, leads, contacts"]
F26d --> F37a["F37-a Weekly price broadcast"]
F37a --> F37b["F37-b Bulk email to a saved list"]
F32d --> F37b
F20g --> F37b
F20f --> F20k["F20-k Block lists"]
F20i --> F22["F22 Contact sync"]
F1d --> F33a["F33-a Attachments: accounts, contacts, leads"]
F1d --> F34c["F34-c Custom fields: accounts, contacts, leads"]
F11a --> F36a["F36-a Capture + upload"]
F36a --> F36b["F36-b Card reading"] --> F36c["F36-c Research + notify"]
F43 --> F36b
F43 --> F36c
F36a --> F36d["F36-d Existing-client check"]
end
subgraph P2["Phase 2 — deals, tea workflows, parity"]
F1a --> F2a["F2-a Deal + pipeline substrate"] --> F2b["F2-b Kanban"]
F2a --> F2c["F2-c Deal detail + create"] --> F2d["F2-d Line items"]
F26b --> F2d
F2c --> F11e["F11-e Convert lead"]
F3a --> F3b["F3-b Activities on deals + custom types"]
F2c --> F3b
F3b --> F17a["F17-a Dashboard: KPIs, funnel, forecast, sources"]
F2a --> F24["F24 Configurable pipelines"] --> F18a["F18-a Stale, aging + dormant alerts"]
F24 --> F17a
F2c --> F6a["F6-a Sample rounds + board"] --> F6b["F6-b Sample table"] --> F6c["F6-c AI feedback chase"]
F2d --> F7a["F7-a Quote records"] --> F7b["F7-b Readiness checklist"] --> F7d["F7-d GP floor + MD approval"]
F7a --> F7c["F7-c Revisions + aging"]
F2c --> F8a["F8-a Brief form"] --> F8b["F8-b Brief questions gate"]
F26b --> F9["F9 Cert mismatch"]
F2d --> F10["F10 Export-doc checklist"]
F7b --> F14["F14 AI quote assistant"]
F17a --> F15a["F15-a Morning briefing, stuck + ranked leads"]
F7d --> F19["F19 ERP handoff (ErpHandoffService)"]
F9 --> F19
F3b --> F21a["F21-a Calendar view"] --> F21b["F21-b Calendar sync"]
F20c --> F20g["F20-g Tracking + scheduled send"]
F32d --> F32a["F32-a List views: deals, quotes, samples, standards"] --> F32b["F32-b Bulk actions"]
F2c --> F32a
F23d --> F23a["F23-a Export: F32-a's lists"]
F32a --> F23a
F4a --> F23b["F23-b Import tool"]
F33a --> F33b["F33-b Attachments: deals, quotes, samples, briefs"]
F2c --> F33b
F34c --> F34a["F34-a Custom fields: deals, quotes, standards, samples"] --> F34b["F34-b Custom fields in lists"]
F2c --> F34a
F20d --> F25a["F25-a Sequence builder"] --> F25b["F25-b Sequence execution"]
F43 --> F23b
F43 --> F25b
F43 --> F32b
F43 --> F6c
F43 --> F14
F43 --> F15a
end
The graph draws each feature’s primary inbound edges only — the Blocked By column in the table below is the authoritative dependency record. No cycles (walked both phases at Gate 3); no Phase 1 feature depends on a Phase 2 feature. Added after Gate 3 and not drawn: F5-i and F38 (2026-09-23), F5-j (2026-09-24) — none has a feature blocker; F38 is blocked externally until dev is usable (register §A-5; the AWS account exists since 2026-09-29). Split 2026-09-27 into F38-a … F38-h (Phase 1) and F38-i (Phase 2), not drawn either; their edges are in the table, and F38-d needs F5-f and F5-j on main before the first dev deploy (F5-k’s seeded admin, which it also needs, has been on main since 2026-09-28). Re-drawn 2026-09-24 (AD #34–#36): F5-k and F39 are added and both block F5-c (and F5-d, whose row its own session updates); F5-f is re-scoped to the ownership and sharing substrate and now comes before the account and lead lists (it blocks F1-b, F11-b, F5-g and F5-h, and F2-a in Phase 2), reversing its Gate 3 edges; F20-e is dropped from V1. Re-drawn 2026-09-27 (AD #37): F5-l is added after F5-k; it blocks F5-d, F5-e and F5-f (so, through F5-f, the account and lead lists). 2026-09-30: the F5-k → F5-l edge is dotted — F5-l needs only F5-k’s wave 1, which is on main, so F5-l has no feature blocker and runs beside F5-k’s waves 2–3. 2026-10-02: F5-l is done, and F5-k’s wave 2 (the admin guards) is on main, so F5-k no longer blocks F5-c, F5-d or F38-d; F5-f has no blocker left and heads Phase 1’s critical path. F4-c is dropped (lead, 2026-09-30) and no longer drawn; its row, like F20-e’s, sits in the Phase 1 table, where the drop was decided. Added 2026-09-30 and not drawn: F32-c (split from F32-b, Phase 1) — after F1-b, F11-b, F4-d and F4-b; its edges are in the table. Added 2026-10-02 and not drawn: F38-j (Phase 1, a follow-up of F38-c) — no feature blocker. Added 2026-10-08 and drawn: F1-f, the contacts page (Phase 1, lead decision, PRD Rev 56) — after F1-d. 2026-10-11: F38’s own row is removed (lead); it had no plan or code and was done only when F38-a … F38-h were, and its spec stays as their requirements. 2026-10-11: F31, global search, is dropped (lead, PRD Rev 60) and no longer drawn; its row sits in the Phase 1 table, where the drop was decided. F7-e, F16 and F26-e are dropped the same day (PRD Rev 61) and no longer drawn; their rows sit in the Phase 1 table too. Also that day, F15-b, F17-b and F18-b are merged into F15-a, F17-a and F18-a (each -a node is relabelled and takes its pair’s edges, so F17-a now follows F24), and F1-c’s label drops LTV. F23-c and F36-f are dropped later that day (PRD Rev 63), and F36-e after them (PRD Rev 64); none is drawn, and their rows sit in the Phase 1 table. Re-drawn 2026-11-06 (reslice, lead: Tharinda): F20-g, F22 and F37-a move into the Phase 1 subgraph (F22 now drawn after F20-i, its real blocker), and F20-h, a Phase 1 item since 2026-10-12, moves there with them; F32-d, F23-d, F33-a and F34-c are added in Phase 1 as the parts of F32-a, F23-a, F33 and F34-a that need no deals, and those Phase 2 nodes keep the parts for deals and the other Phase 2 records, each after its Phase 1 part and F2-c (F33’s node becomes F33-b); F37-b is drawn for the first time, after F37-a, F32-d and F20-g. Every new edge runs from Phase 1 to Phase 2 or within Phase 1, so no Phase 1 feature depends on a Phase 2 feature. Re-drawn 2026-11-11: F20-g, F22 and F23-d move back into the Phase 2 subgraph, and F20-k with them; no Phase 1 feature depends on any of the four. Re-drawn 2026-11-11 (lead: Tharinda): F36-a moves into the Phase 1 subgraph, after F11-a; F36-b and F36-d stay in Phase 2 after it, so its new edges also run from Phase 1 to Phase 2. Re-drawn 2026-11-15 (lead: Tharinda): F23-d and F37-a move back into the Phase 1 subgraph, after F32-d and F26-d; F23-a and F37-b stay in Phase 2 after them, so their edges run from Phase 1 to Phase 2. Re-drawn 2026-11-19 (lead: Tharinda): F37-b moves into the Phase 1 subgraph, after F37-a, F32-d and F20-g, all three in Phase 1 and done. Re-drawn 2026-11-20 (lead: Tharinda): F20-k and F22 move back into the Phase 1 subgraph, after F20-f and F20-i, both Phase 1; no Phase 2 feature depends on either.
Critical path, Phase 1 (depth 7): F5-a → F5-b → F1-b → F1-d → F20-c → F20-d → F26-d, tied with F5-a → F5-b → F1-b → F1-d → F1-e → F1-c → F13 / F20-f. (Since the F20-f split of 2026-10-17 the email chain F1-c → F20-f → F20-j is one longer, depth 8; F20-k, its other end, moved to Phase 2 on 2026-11-11 and back into Phase 1, started early, on 2026-11-20.) The pricing spine F26-a → F26-c → F26-f → F26-g/F26-d runs beside it. Phase 2 (depth 6): F2-a → F2-c → F2-d → F7-a → F7-b → F7-d → F19. (This is the Gate 3 feature graph. Since F5-f was done on 2026-10-04, the path to the Foundation milestone is the cloud bring-up, F38-a → F38-b → F38-d — .claude/CLAUDE.md § Active Context.)
Parallel lanes — the work-division plan as drawn at Gate 3 for three developers (unnamed; assign per feature). The team is four from 2026-09-29, each taking the next unblocked feature, with the chains regrouped in .forge/team-guide.md § Working in Parallel — Four Developers:
| Lane | Phase 1 sequence | Phase 2 sequence |
|---|---|---|
| A | F5-a → F5-b → F1-a → F5-k wave 1 → F5-l → F5-f → F1-b → F1-d → F1-f (added 2026-10-08) → F1-e → F1-c → F5-c → F5-d → F5-e → F5-g → F5-h → F13 (F39 beside F5-k, before F5-c/F5-d; F5-k’s waves 2–3 beside F5-l, before F5-c) | F2-a → F2-c → F2-d → F7-a → F7-b → F7-d → F7-c → F19 → F14 → F33 → F34-a → F34-b (2026-11-06: F33 is F33-b, attachments on deals, quotes, samples and briefs; F33-a and F34-c, the account, contact and lead parts, moved to Phase 1) |
| B | F11-a → F11-b → F11-f → F12 → F11-d → F11-c → F11-g → F11-h → F3-a; F4-a → F4-d → F4-b | F3-b → F24 → F17-a → F18-a → F15-a → F21-a → F21-b → F25-a → F25-b |
| C | F20-a → F20-b → F20-f → F20-c → F20-d (F20-f split on 2026-10-17: F20-i → F20-f → F20-j, F20-k; and on 2026-10-26: F4-d → F20-l → F20-f); F26-a → F26-b → F26-c → F26-f → F26-g → F26-d | F2-b → F6-a → F6-b → F6-c → F8-a → F8-b → F9 → F10 → F32-a → F32-b → F23-a → F23-b → F11-e → F20-g → F22 (2026-11-06: F20-g and F22 moved to Phase 1, and F32-d and F23-d, the account, lead and contact parts of F32-a and F23-a, with them; 2026-11-11: F20-g, F22 and F23-d moved back, and F20-k joined them; 2026-11-20: F20-k and F22 taken back into Phase 1, started early) |
| Started early (2026-11-06) | After Phase 1’s own work, by whoever is free: F23-d, F37-b, F20-k (after F20-f) and F22 (after F20-i) — each stays in Phase 1 through Empire’s Phase 1 UAT round, moves to Phase 2 if it is not done by its end (lead, 2026-11-19), and is added to the Phase 1 acceptance criteria when done (F20-g, F22, F23-d and F37-a moved back on 2026-11-11, F20-g returned to Phase 1 the same day and F37-a and F23-d on 2026-11-15; F37-b was taken in on 2026-11-19, and F20-k and F22 on 2026-11-20; F34-c, done, was added to Phase 1 on 2026-11-11, F33-a, done, on 2026-11-12, and F20-g, F32-d and F37-a, done, on 2026-11-18) | (their Phase 2 halves are in the lanes above) |
| Capture stream | F36-a → F36-b → F36-c, and F36-a → F36-d (Phase 1 scope from 2026-11-11; own repo) | — |
Sequential by necessity: F1-a gates every lane (F11-a, F26-a, F4-a all sit on it) — it goes first and fast, beside F5-a. F5-b gates every screen. F11-h and F26-d wait on the email lane (F20-c, F20-d). F5-f (the ownership and sharing substrate) comes before the account and lead lists — they read through its visibility rule — and F5-g (the sharing screens) waits on both list and detail screens. F5-k and F39 come before F5-c/F5-d. Safe to start beside each other on day one: F5-a and F1-a; from day two or three: F11-a, F26-a, F4-a, F20-a, F5-c, F5-d. (As of 2026-10-05: F39, F5-l, F5-k, F5-d and F5-f are done, so F1-b and F11-b have no open feature blocker; tracker.yaml holds the current state.)
Seam builders (R-FND-001 — the first consumer builds each on FS-11’s SeamGuard pattern): AIProvider — F12 · SearchProvider — F11-c · MailboxProvider — F20-a · AuctionPriceProvider (no-op) — F26-a · ErpHandoffService — F19. Workflow primitives (AD #29 first-consumer rule): RoundLifecycle — F6-a · ChecklistEngine/GateRule — F7-b · StaleClock — F18-a · the tag comparison — F9.
Features
Order: Phase 1 in lane order, then Phase 2 in lane order. Phase = lifecycle (all backlog at Gate 3); Pri = the PRD tier (P0 must-have, P1 core value, P2 enhancement — the tracker carries it as high / medium / low). ◐ = borderline split (see Slicing Principle).
Phase 1
| ID | Title | Pri | Phase | Spec | Plan | Blocked By | Notes |
|---|---|---|---|---|---|---|---|
| F5-a | Sign in with Microsoft and sign out | P0 | done | spec | — | — (FS-6) | Login page, callback, logout, session-expired handling, GET /me wiring (AD #28) |
| F5-b ◐ | App frame and navigation shell | P0 | done | spec | — | — | Design-system §6 frame (FS-3 Q-5), sidebar nav, current-user menu, route skeleton, hide-vs-disable rule |
| F5-c | Users: list, create, role, manager, deactivate | P0 | done | spec | — | F5-b, F39 | Everything under access.manage (AD #34); admin pre-creates every user, no invitation (OQ-51 closed); role mandatory; manager_id; deactivate ends sessions and is refused for self, the last admin, a user with direct reports or one who owns records (AD #35); audited (F39). Owns the six list-screen states (R-FND-002). Done — four waves merged; tracker.yaml holds the detail |
| F5-d | Roles editor | P0 | done | spec | — | F5-b, F39, F5-l | Role CRUD over the minimal catalog F5-k leaves, none / view / manage per entity plus an All records tick per owned entity (AD #37 — no per-permission scope), last-admin (access.manage) and role-in-use guards (AD #34) |
| F5-e | Effective-permissions viewer | P1 | done | spec | — | F5-c, F5-d, F5-l | “Why can this person see this?” |
| F5-f | Ownership and sharing substrate | P0 | done | spec | — | F5-l | Re-scoped 2026-09-24 (AD #35). record_share, the owner pattern, one visibility rule (the reporting tree, the entity’s all key and shares — AD #37) for lists and single records, share / remove / reassign operations (open to any manage holder who reaches the record, a sharee included — lead, 2026-09-30), the minimal user directory; accounts adopt it (BUG-021 was fixed ahead of it). Comes before the account and lead lists |
| F5-g | Record sharing screens on accounts and leads | P0 | done | spec | — | F5-f, F1-d, F11-f | Screens only (AD #35): Share dialog with the eligible-user picker, shared-with list with Remove, shared-with-me marker + filter; sharing is transitive and needs manage. Deal surface with F2-c |
| F5-h | Offboarding: bulk reassign owned records and reports | P0 | done | spec | — | F5-c, F5-f, F1-b, F11-b, F20-a | The screen that clears F5-c’s deactivation refusals: bulk-reassign owned records, re-parent reports (AD #35); F5-c’s deactivation itself ends the sessions and releases the mailbox. Done 2026-10-09: waves 1–3 (forge-et-be#217, #221; forge-et-fe#190, #197, #203), Reflect forge-et-harness#542 |
| F5-i | Real Microsoft sign-in from a developer laptop | P1 | done | spec | — | — | Added post-Gate-3 (2026-09-23). Developer tooling: opt-in real Entra sign-in + mailbox consent on a laptop before AWS exists. The Entra side is done (2026-09-24): the two localhost:8080 reply URLs are registered and the non-prod certificate (shared with dev and UAT — no laptop certificate of its own) is uploaded; (environments-and-identity.md §2.3, §2.5). Done 2026-10-01: Wave 1 the code (forge-et-fe#65, #69; forge-et-be#86, #87), Wave 2 the live end-to-end check as CRM01 (forge-et-harness#322) |
| F5-j | Cross-site CSRF cookie for the cloud (AD #33) | P0 | done | spec | — | — | Added post-Gate-3 (2026-09-24); owner Tharinda; done locally 2026-09-27 (forge-et-be#78, forge-et-fe#59); the per-environment values are F38’s. The XSRF-TOKEN cookie gets a configurable domain and a per-environment name (backend), and the frontend reads the name from build config — so the apps can call the backend cross-site. Buildable now; F38 needs it before the first dev deploy |
| F5-k | Access-model realignment: minimal catalog, no superadmin, first admin by migration | P0 | done | spec | — | — | Added post-Gate-3 (2026-09-24, AD #34). The catalog collapses to view/manage per entity plus access.manage, settings.manage, email.manage, price.publish; the superadmin, is_system and * go; one Flyway migration seeds the IT Admin role and user from a per-environment email; the runtime first-admin job retires; the frontend moves to the new keys and re-reads /me after a 403 and on focus. BUG-022’s consent gate shipped separately in forge-et-be#122 and meets F5-k AC-5. All three waves merged |
| F5-l | Reach from the reporting line: grants without scope, and an all key per owned entity | P0 | done | spec | — | — | Added post-Gate-3 (2026-09-27, AD #37). role_grant loses its scope column; lead.all / account.all join the catalog; reach is the entity’s all key, else the reporting tree; the account, contact and lead read paths, F4-a’s dry-run checks, the seed and the backend docs follow, and so do the frontend’s /me types and tests (not backend-only — corrected 2026-09-30). Done 2026-10-02: wave 1 (forge-et-be#126, forge-et-fe#97, forge-et-harness#319, merged 2026-09-30), Reflect forge-et-harness#367. Keeps every F1-a / F11-a / F4-a AC. F5-d, F5-e and F5-f no longer wait on it |
| F1-a | Account and contact substrate | P0 | done | spec | — | — (FS-2) | account, contact, tag, note, timeline_event, certification; API only, no screens. No order entity in V1 (OQ-63). All three waves merged (the last on 2026-09-25). Wave 3 also serves F1-b: list lastContactAt/dormant (Rev 4; the owner-options list is retired by Rev 5 — F5-f’s user directory replaces it). Contacts on account.* (Rev 5); the list’s team-as-own interim (BUG-021) was fixed in forge-et-be#61 |
| F1-b | Account list and create/edit | P0 | done | spec | — | F1-a, F5-b, F5-f | List columns + Dormant badge; create/edit; reads F5-f’s visibility rule (the reporting tree incl. shares, and account.all — spec Rev 4, AD #37); owner picker on F5-f’s user directory (spec Rev 3). Wave 1 (the only wave) merged 2026-10-07: forge-et-fe#171, forge-et-harness#495 |
| F1-d | Account detail: profile grid and contacts | P0 | done | spec | decomposition | F1-b | Done 2026-10-10: wave 1 merged (forge-et-be#225, forge-et-fe#208). Spec approved 2026-10-08: the /accounts/{id} page, profile grid, contacts panel (add, edit, make primary, archive, restore), ordered panel places composed from src/app, F26-b’s standards panel mounted; the record gains lastContactAt, dormant and the owner’s name; archive clears a contact’s primary flag on the server. No past-orders panel (OQ-63) and no participants place (OQ-57), both waived |
| F1-e ◐ | Notes and tags on accounts and contacts | P0 | done | spec | decomposition | F1-d | Done 2026-10-18: wave 1 merged (forge-et-be#265, forge-et-fe#284). Account and contact notes (edit and delete for any account.manage holder; delete marks, never removes; account notes on the timeline), account and contact tags, tag configuration on a new Settings › Tags page (retire, never delete), the account list’s tag filter |
| F1-f | Contacts page, including contacts with no account | P0 | done | spec | decomposition | F1-d | Added 2026-10-08 (lead; PRD Rev 56), answering F1-d Q-4. Spec approved 2026-10-12: /contacts list with search, sort, archived switch and, for account.all holders, a No account filter; the row gains accountName and the list a hasAccount filter; a read-only contact view holding F1-e’s tags and notes places; edit, archive, restore and Attach to account as row actions; no create, no tag filter (F32-a). Phase 1 criterion C7 |
| F1-c | Communication timeline and dormancy | P0 | done | spec | decomposition | F1-e | Done 2026-10-21: wave 1 shipped as forge-et-be#284 and forge-et-fe#312. Owns the rendering; rows written by F1-e, F3-a, F11-f, F20-f. Narrowed 2026-10-11 (lead): no computed lifetime value (no order data in V1, OQ-63); the entered Est. LTV that F1-a, F1-b and F1-d ship stays |
| F13 | AI account briefing | P1 | done | spec | decomposition | F1-c, F12 | The account page’s Before you meet this customer panel. The brief is made only when a person whose role holds account.manage presses Prepare briefing (AD #32 as edited for F13, lead sign-off 2026-10-21). The spec’s decisions settle the rest: nothing is stored; no order history (OQ-63 waived, default (b)); open items come from the timeline; the re-engagement prompt shows only on a dormant account; Sonnet 5.5 by default, Haiku 4.5 on dev until Sonnet answers; provenance (confidence and source) on every brief (spec § Context) |
| F11-a | Lead substrate and intake contract | P0 | done | spec | — | F1-a, F39 | lead (with the optional matched account and contact), lead_tag, note.lead_id, the single-record API and the intake contract (F36-a, F4-b). No screens. The snapshot and score tables moved to F11-c / F11-g (2026-09-25) |
| F11-b | Lead inbox: list, filters, add/edit | P0 | done | spec | — | F11-a, F5-b, F5-f | Full stack: the lead list API and a read-only tag list; the two-pane Leads screen — list with status, country, buyer type, source, tag and owner filters and search, a basic lead view, manual add/edit (F12 pre-fills it); reads through F5-f’s visibility rule; an “Unassigned” filter for lead.all holders (no queue; AD #37). Priority and hot/cold are F11-g’s, added to this list (spec 2026-10-05) |
| F11-f ◐ | Lead detail and archive/nurture | P0 | done | spec | — | F11-b | Extends F11-b’s lead view: archive / nurture and restore, notes, tag editing, matched account and contact, the account timeline entry, and the places for the AI, compose and share panels; OQ-57 waived (participants place only) |
| F12 | AI inquiry extraction (paste text → lead draft) | P1 | done | spec | — | F11-b | Builds AIProvider; null-not-guess; Phase 1 by Q4 |
| F11-c | Lead research job | P1 | done | spec | decomposition | F11-f, F12 | Done 2026-10-22: wave 1 (forge-et-be#297, forge-et-fe#329). Builds SearchProvider (Rev 30) on Exa, free credit, provisional (SP-ARCH-004). One company search a lead, and a person search, which F11-i puts behind a Settings switch, on by default (PRD Rev 99); the hourly sweep is also the paced batch over the F4-b backlog |
| F11-g | AI ranking: P1–P3, why, next action; hot/cold from buyer replies | P1 | done | spec | — | F11-c | Three priority levels (PRD Rev 55). Hot/cold is separate and not AI: hot while the buyer last wrote within 30 days (a setting), cold after — replaces Gate 3 Q6’s hot = P1–P2 |
| F11-d | AI summary and spam/duplicate detection | P1 | done | spec | — | F11-f, F12 | |
| F11-h | AI-drafted follow-up with Approve & send | P1 | done | spec | — | F11-f, F12, F20-c | The cold-lead follow-up (Q5); owns the AI-draft button in compose. Drafts only when a person presses the button — nothing in advance, backlog included (PRD Rev 56). The spec’s decisions 1–9 settle the rest: a draft is never stored, never states a price, and is sent only by a person; approval is tied to a sent email (spec § Context) |
| F11-i | Person-search switch on the Settings page | P1 | done | spec | decomposition | F11-c | Added 2026-11-17 (Dinil); follow-up of F11-c. Empire’s answer of 10 November: the person search may go to Exa, and an administrator turns it on or off on a Settings page, on by default. Replaces F11-c’s server setting et.research.person-search.enabled (off) with a stored switch under its own Settings key (AD #41) |
| F11-j | Summaries for migrated leads from their linked email | P1 | dev | spec | decomposition | F20-f | Added 2026-11-19 (Tharinda); follow-up of F11-d. The lead’s decision of 19 November: every migrated Pipedrive lead gets a summary written from its linked past email, so acceptance criterion E8 holds. Separate from F20-j (F20-j spec D-6); AI work paced under the Bedrock limits (F42, F43) |
| F3-a | Follow-up tasks on leads and accounts | P0 | done | spec | — | F1-d, F11-f | Phase 1 by team decision (Q7-B); deals + custom types = F3-b. Spec approved 2026-10-13: the six fixed types as seeded activity_type rows; each follow-up on exactly one account or lead, with one assignee who must already reach the record (no reach of its own); the Activities page at /activities (Overdue / Today / Upcoming by Colombo date, Completed; Mine or All I can see) with an overdue nav badge as the Phase 1 reminder; Add follow-up and a Follow-ups panel on the account page and the lead view (the lead view’s actions place becomes a list); a completed account follow-up writes a timeline row and counts as contact, a lead follow-up writes none. Phase 1 criteria H1–H3 |
| F20-a | Mailbox connection | P0 | done | spec | — | F5-b | Builds MailboxProvider (AD #16); client dep: M365 admin consent + test accounts |
| F20-b | Inbound sync and in-CRM inbox | P0 | done | spec | — | F20-a | Ingest, renewal on FS-9, lapsed alarm, plain inbox list. Superseded in part on 2026-10-17: the inbox moves to live reads (F20-i), storage to linked mail only (F20-f), the back-fill to F20-j (spec Rev 2) |
| F20-i | Live inbox from Microsoft | P0 | done | spec | — | F20-b | Split from F20-f, 2026-10-17 (reslice). The inbox read live from Microsoft, 50 a page; folders, categories, unread, search; the mailbox connects at sign-in, one connection for mail, calendar and contacts |
| F20-f | Auto-link mail to records and timeline | P0 | dev | spec | decomposition | F20-b, F1-c, F11-f, F20-i, F20-l | Automatic and manual linking, unlinking; linked email and its attachments stored; timeline rows; matches every address of a contact; a converted lead is never auto-linked. Narrowed 2026-10-17 and 2026-10-26 (reslice) |
| F20-j | Link past mail for new records, connected mailboxes and imports | P0 | dev | spec | decomposition | F20-f | Split from F20-f, 2026-10-17 (reslice). Background jobs, 12 months back by default |
| F20-l | Several email addresses per contact | P0 | done | spec | — | F1-a, F4-d | Split from F20-f, 2026-10-26 (reslice). Other addresses beside the main one; contact API and screens; the Pipedrive migration keeps every address; lands before the first production run of the migration |
| F20-c | Compose, reply and send from a record | P0 | done | spec | — | F20-a, F1-d, F11-f | CC/BCC; reply, reply-all, forward; formatted text (PRD Rev 68); one human-triggered send, idempotency key (AD #13); no bulk (F37-a/F37-b, Phase 2) |
| F20-h | Email attachments | P0 | done | spec | — | F20-c | Split out of F20-c by the lead, 2026-10-12 (PRD Rev 68): attach new files in the compose dialog; nothing depends on it |
| F20-d | Email templates and merge fields | P0 | done | spec | — | F20-c | Phase 1 by team decision (Q8-B); seeds the weekly-prices template |
| F4-a ◐ | Pipedrive import engine (dry-run report) | P0 | done | spec | — | F1-a, F11-a | Parse, map, dedupe preview, ID preservation, report — no writes; leads, organisations and people only (PRD Rev 44) |
| F4-d | Migrate organisations and people | P0 | done | spec | decomposition | F4-a, F1-e | The write half; re-runnable (first load, then the final run after the data freeze). Import owner = the signed-in user unless named; a later run never changes an owner (PRD Rev 47). Spec approved 2026-10-13: a write run answers in the request, in one transaction, and needs the dry run’s digest (PRD Rev 70); the standards list is not F4-d’s (OQ-27) |
| F4-b | Migrate leads | P0 | done | spec | decomposition | F4-d, F11-a, F42 | Spec approved 2026-11-06; backend-only; one wave of 4 WIs. Backlog → F11-c batch; Visible to not migrated (D-5); no deals (Rev 32); import owner as F4-d (PRD Rev 47) |
| F32-c | Bulk reassign leads and accounts (the import hand-out) | P0 | done | spec | — | F1-b, F11-b, F4-d, F4-b, F5-h | Added 2026-09-30 (lead; PRD Rev 47), split from F32-b. Only “change owner” on the account and lead lists, in Phase 1, so the import owner can hand the imported records out; filters by the hidden Pipedrive owner name, shown nowhere else. Reuses F5-h’s bulk reassign operation and row selection, so F5-h blocks it (2026-10-07). Needed by the first Pipedrive load |
| F26-a | Standards and price substrate | P1 | done | spec | — | F1-a | Extends FS-15 (the allocator); auction_sale, price (four-figure build-up, Rev 31) and cost tables; as-of reads + two read endpoints under buying_standard.view; PriceModel bean; AuctionPriceProvider no-op. No writes — each writing feature (F26-b/c/f/g) builds its own; the account-context read is F26-b’s |
| F26-b | Standards book on the account | P1 | done | spec | — | F26-a | Spec Rev 2: create/edit/archive/restore and cost entry (“replaces from the date”) under buying_standard.manage, audited, on a Standards book view on the Pricing page; the held-certs join; the account-context read (final USD only) and a read-only account panel, shipped unmounted for F1-d to mount (Rev 2); the shared standard picker. No price writes. OQ-9 / OQ-27 waived (seed halves) |
| F26-c | Weekly workbook upload as draft prices | P1 | done | spec | — | F26-a, F5-d | Tolerant importer for today’s workbook, the Tea Room confirming which column holds which figure per tab (remembered by tab name); duplicate flag; build-up figures plus the rate per price row (PRD Rev 53) |
| F26-f | Tea Room review, edit and publish | P1 | done | spec | — | F26-c | Audited publish (price.publish); price history; PL default quoted-per-deal (OQ-61) |
| F26-g | Price expiry roll and manual override | P1 | done | spec | — | F26-f | Expiry against the next auction_sale on FS-9 |
| F26-d | Send this week’s prices | P1 | done | spec | — | F26-f, F20-d, F26-b | Per-account, human-triggered, own standards only, via the weekly-prices template |
| F38-a | Cloud: account baseline and long-lead requests | P0 | done | spec | — | — (register §A-5 closed 2026-10-13: dev is usable) | Added 2026-09-27 (F38 split). The F38 items have no PRD parent: their requirements are in the F38 spec (approved 2026-09-27), which each item’s spec narrows; F38-a … F38-h done means dev is up, the retest is recorded and the first uat is applied, so Phase 1 cannot go to client UAT before them. F38 FR-1 – FR-7: accounts, security baseline, Terraform state, Bedrock and SES long-lead requests, certificates and the first DNS request. Check and close, development account only (F38 Rev 12, Rev 13, 2026-10-14/15): production’s half is F38-i’s. Closed 2026-10-26 with SES sending from dev.crm.empire.lk; the one call each to Sonnet 5.5 and Haiku 5.5 in dev moved to the register’s §C-5 row (F38-a spec Rev 4) |
| F38-b | Cloud: the dev estate in Terraform | P0 | done | spec | — | F38-a | Added 2026-09-27 (F38 split). F38 FR-8 – FR-15: the dev estate, no NAT. Check and close, not build (lead, 2026-10-11): the DevOps team built most of it first, so this checks forge-et-iaac against those requirements and closes the gaps in environments-and-identity.md §4 |
| F38-c | Cloud: GuardDuty file-scan adapter (FS-11 cloud half) | P0 | done | spec | — | — | Added 2026-09-27 (F38 split). F38 FR-18: the real scanner, the scanner half of register A-1. Done 2026-09-28 against GuardDuty-shaped event bodies and LocalStack (forge-et-be#82, #94); proved on dev by F38-f |
| F38-d | Cloud: deploy pipelines and the first dev deploy | P0 | done | spec | — | F38-b, F38-c, F5-f, F5-j | Added 2026-09-27 (F38 split). F38 FR-16, FR-19 – FR-23: CI’s AWS credentials (an IAM service user per account, F38 Rev 4), deploy-dev, the first dev deploy, the off-hours schedule. Check and close, not build (lead, 2026-10-11): the backend already deploys to dev, so this closes the gaps in environments-and-identity.md §4 and adds the two frontends’ pipelines |
| F38-e | Cloud: observability and mail on dev | P0 | dev | spec | — | F38-d | Added 2026-09-27 (F38 split). F38 FR-24 – FR-27: logs, alarms, SES mail |
| F38-f | Cloud: proving the platform on dev | P0 | dev | spec | — | F38-d, F38-e | Added 2026-09-27 (F38 split). F38 FR-28 – FR-30: the register walk on dev and AI on real Bedrock |
| F38-g | Cloud: browser suites against dev, the retest and the smoke tier | P0 | dev | spec | — | F38-d | Added 2026-09-27 (F38 split). F38 FR-31 – FR-34: dev-capable browser suites, the end-to-end retest, the smoke tier |
| F38-h | Cloud: the first UAT environment | P0 | dev | spec | — | F38-d, F38-g | Added 2026-09-27 (F38 split). F38 FR-35 – FR-37: deploy-uat, the uat instance and its rehearsal |
| F38-i | Cloud: production and go-live | P0 | dev | spec | decomposition | F38-h | Added 2026-09-27 (F38 split); outside F38’s done. Register checklist steps 28–29, deploy-prod, F38 FR-17: the production instance, the go-live commitments, dev’s first-month cost check, and the capture app’s UAT deploy for Phase 2’s round. Spec approved 2026-10-27; OQ-J closed (the proposal stands). Waits on Empire’s add-on answers, the admin email, and the DevOps team’s answers to its Q-5 – Q-7. Moved from Phase 2 to Phase 1 on 2026-11-02 for tracking (the lead): its code waves are worked during Phase 1; waves 11–17 wait until production is needed, after Phase 1’s UAT round, so it moves back to Phase 2 before Phase 1 seals unless it is done. Production’s dates still follow the Statement of Work’s Phase 2 |
| F38-j | Cloud: a switch to run the file pipeline without GuardDuty | P1 | done | spec | — | — | Added 2026-10-02 (lead); follow-up of F38-c; outside F38’s done. A cloud-profile setting selects GuardDuty or no scanner, so Malware Protection can be switched off without breaking file handling. With scanning off, uploads get a new NOT_SCANNED status that downloads allow; off is logged, audited and counted. Today removing the protection plan leaves every new file PENDING and undownloadable |
| F39 | Audit trail: one table, one service, security events | P0 | done | spec | — | — | Added post-Gate-3 (2026-09-24, AD #36); no PRD parent row — PRD NFR Observability. audit_event + a service written in the caller’s transaction; every write and every security event, never reads; the SYSTEM actor; timestamps on every table; retrofits the writes already on main. Blocks F5-c and F5-d; every later writing feature calls it |
| F40 | Accessibility and responsive checks at every supported size, as a PR gate | P0 | done | spec | — | — | Added 2026-09-27 (lead decision; no PRD parent row — PRD § Accessibility › Supported sizes, Rev 42). Playwright projects per supported size in both FEs (CRM tablet + desktop + 320px reflow; capture phone + tablet + desktop), WebKit alongside Chromium, one shared axe + layout check on every page, and a local pnpm e2e:gate in both app repos that must pass before a PR is ready, enforced by a harness hook and a Slow lane step — no CI job runs a browser (PRD Rev 45, 2026-09-28). The audit’s defects are BUG-028…031, fixed separately |
| F41 | Dependency bumps that cannot change the browser gate’s result need no gate run | P1 | done | spec | — | — | Added 2026-09-30 (lead decision; follow-up of F40), raised by forge-et-fe#91. A package.json + pnpm-lock.yaml change counts as touching no gate input when the lockfile’s gate graph (packages reached from direct dependencies on neither of two new lists in gate-inputs.json, types-only and tools not run by the gate, with their resolutions and links) is unchanged; one rule in rules.mjs for the CLI, the harness hook and the Fast lane check; fail closed on a lockfile it cannot analyse; a boundary check keeps gate-loaded files off listed packages; Dependabot’s npm group split into tooling and runtime. Both FEs |
| F42 | Bedrock call pacing under the account’s request quota | P0 | done | spec | — | F12 | Added 2026-10-27 (lead decision; follow-up of F12), from owed.md “The AI layer under Bedrock’s new-account limits”. Each backend task paces its Bedrock calls to a configured share of the account’s requests-a-minute quota per inference profile; a reserve for calls a person waits on; a background call that gets no slot in time ends RATE_LIMITED and the hourly sweep re-queues the lead; throttles no longer open the circuit breaker. Backend only; before F4-b’s first production run |
| F43 | AI load under the Bedrock quota: backlogs that drain, and a busy answer for people | P0 | done | spec | — | F42 | Added 2026-11-02 (lead decision; follow-up of F42), from F42’s dev proof (register §B F42 items 1 and 5). Designs for every source of AI load (its spec’s table): a burst of leads is triaged in minutes, where today about two in five wait for the next hourly sweep (up to an hour) and some for the one after; a person’s AI call refused for no free slot answers “busy, try again in N seconds” instead of reading as an outage; background work moves to Haiku 4.5’s Global profile, which has its own 10 requests a minute. Backend, CRM and the same forge-et-iaac grant in each environment. No Phase 1 feature waits on it; the Phase 2 features that make or cause AI calls do |
| F44 | Follow-up for an unreplied customer email | P0 | spec | spec | — | F20-f, F3-a, F20-c | Added 2026-11-12 (lead: Tharinda) from Empire’s ask at the 10 November progress meeting (Roshan; Kavindu believed it was built). An email from a customer or lead that F20-f has linked, with no reply after one working day (an administrator can change it on the Settings page), creates a follow-up in Activities for the person who received it, with Reply (compose, with a template or an AI draft) and No Reply Needed. Nothing is sent without a person. Phase 1, acceptance criterion F7. Spec approved 2026-11-19: working days are Monday to Friday in Colombo time; one follow-up per email, for the To recipient; a 15-minute sweep raises and closes them; an Email Follow-Ups Settings page under settings.email_follow_ups.manage. |
| F45 | Split the largest backend classes | P1 | done | spec | — | — | Added 2026-11-12 (lead: Tharinda) from the code review of 2026-11-08. forge-et-be’s GraphMailboxProvider, LocalMailboxProvider and LeadService are split into smaller classes by job, with no change in behaviour and the one MailboxProvider interface kept (AD #16). Engineering work with no PRD feature and no acceptance criterion of its own; Phase 1. |
| F46 | Split the other source files over the size limit | P1 | spec | spec | — | — | Added 2026-11-14 (lead: Tharinda) from the file-size check (.forge/design/harness/file-size-check.md). Every source file over 800 code lines that F45 does not split — nine forge-et-fe files, three of them the largest CRM screens, and forge-et-be’s LocalLiveMailbox and EmailSendService — is split by job, with no change in behaviour. Engineering work with no PRD feature; Phase 1. |
| F20-g | Open/link tracking and scheduled send | P0 | done | spec | — | F20-c | Started early in Phase 1, 2026-11-06 (lead: Tharinda; was Phase 2); moved back to Phase 2 and released on 2026-11-11, then taken back into Phase 1 by Dinil the same day to finish it; done, and added to Phase 1 on 2026-11-18 (acceptance criteria F8 and F9; PRD Rev 100). Open tracking needs an endpoint reached without sign-in and a privacy decision (a security-sensitive PR); scheduled send runs on EventBridge Scheduler (AD #12). Spec approved 2026-11-09: tracking chosen per email, on by default; no delivered state for a single email (bounces are F37-b’s); one minute sweep sends due scheduled emails |
| F32-d | List views and saved filters on accounts, leads and contacts | P1 | done | spec | — | F1-b, F11-b, F1-f, F5-g | Split from F32-a 2026-11-06 (Gate 3 Run 4, reslice; lead: Tharinda). Builds the list-view engine (columns, sorting, saved filters, FS-10 offset pagination with a total); F32-a adds deals. Started early; done, and added to Phase 1 on 2026-11-18 (acceptance criteria Section N; PRD Rev 100) |
| F23-d | Export of the account, lead and contact lists (CSV/Excel) | P1 | workitem-decompose | spec | decomposition | F32-d | Split from F23-a 2026-11-06 (Gate 3 Run 4, reslice; lead: Tharinda). Only viewable records; every export audited (AD #36). Started early in Phase 1; moved to Phase 2 on 2026-11-11, not started; taken back into Phase 1 on 2026-11-15 (lead: Tharinda), owner Tharinda; stays in Phase 1 through Empire’s Phase 1 UAT round and moves to Phase 2 if not done by its end (lead, 2026-11-19) |
| F33-a | File attachments on accounts, contacts and leads | P1 | done | spec | decomposition | F1-d, F1-f, F11-f | Split from F33 2026-11-06 (Gate 3 Run 4, reslice; lead: Tharinda). Builds the attachment store on the FS-11 pipeline (entity-map D-6) and its type allow-list; F33-b adds deals. F33’s own row removed, as F38’s was. Started early; done, and added to Phase 1 on 2026-11-12 (Phase 1 acceptance criteria, Section M; PRD Rev 92) |
| F34-c | Custom field definitions and forms on accounts, contacts and leads | P1 | done | spec | decomposition | F1-d, F1-f, F11-f | Split from F34-a 2026-11-06 (Gate 3 Run 4, reslice; lead: Tharinda). JSONB (AD #8); OQ-26 open but blocks only F17-a and F24. F34-a adds deals. Started early; done 2026-11-11 and added to Phase 1 the same day (Phase 1 acceptance criteria, Section K; PRD Rev 90) |
| F37-a | Weekly price broadcast to every customer | P1 | done | spec | — | F26-d, F20-d | Committed to Empire 2026-10-09 (PRD Rev 57). F26-d’s per-account send repeated for every customer under one confirmation, each email carrying only that customer’s own standards; clear of OQ-62. Started early in Phase 1 on 2026-11-06, moved back to Phase 2 on 2026-11-11 (not started), and started early in Phase 1 again on 2026-11-15 (lead: Tharinda); done, and added to Phase 1 on 2026-11-18 (acceptance criterion G9; PRD Rev 100) |
| F37-b | Bulk email to a saved contact list | P1 | spec | spec | — | F37-a, F32-d, F20-g | Committed to Empire 2026-10-09 (PRD Rev 57). One message to the contacts of a saved list (newsletters, product promotions, trade-fair invitations), with an opens-and-clicks summary per send. Not F28: no segmentation builder or campaign reports beyond the per-send summary. Started early in Phase 1 on 2026-11-19 (lead: Tharinda); stays in Phase 1 through Empire’s Phase 1 UAT round and moves to Phase 2 if not done by its end (lead, 2026-11-19). OQ-62 was decided by the delivery team on 2026-11-19 under the lead’s rule of 2026-11-13 (PRD Rev 103): the sender’s own mailbox, everyone on the list unless unsubscribed, an unsubscribe link in every email, bounces read; Empire confirms at the hand-over. Spec approved 2026-11-19 |
| F20-k | Email block lists | P0 | dev | spec | — | F20-f | Split from F20-f, 2026-10-17 (reslice). Per-user and admin lists; Block sender. Spec approved 2026-11-20: blocks work per address and look forward only, with no bulk removal of past email. Moved from Phase 1 to Phase 2 on 2026-11-11 (lead: Tharinda); taken back into Phase 1 on 2026-11-20 (lead: Tharinda) to start early; stays in Phase 1 through Empire’s Phase 1 UAT round, goes out in a later UAT drop if done, and moves to Phase 2 if not done by its end (lead, 2026-11-19) |
| F22 | Contact sync | P2 | spec | spec | — | F20-a, F1-a, F20-i, F20-l | Scope lever. Spec approved 2026-11-20 (Tharinda): one way from Outlook into the CRM, through a per-user review list (PRD Rev 107). Started early in Phase 1 on 2026-11-06 (lead: Tharinda); moved back to Phase 2 on 2026-11-11, not started; taken back into Phase 1 on 2026-11-20 (lead: Tharinda) to start early, on the same terms as F20-k. Contacts.ReadWrite is granted (environments-and-identity.md §2.4) |
| F36-a | Capture and upload (card photo, badge QR) | P1 | done | spec | — | F11-a | Own repo (AD #20); ports from the POC; the descope lever. 2026-10-11 (PRD Rev 64): a capture whose upload fails is kept on the phone and resent when the app is open with a connection, replacing F36-e. Phase 1 scope from 2026-11-11 (lead: Tharinda; was Phase 2), with F36-b, F36-c and F36-d, as agreed with Empire at the 10 Nov progress meeting. Its screens are drawn in pwa-current before the spec (owed.md) |
| F36-b | AI card reading | P1 | done | spec | — | F36-a, F12, F43 | Haiku vision; designed under the Bedrock pacing (its spec’s constraints, 2026-11-02). Phase 1 scope from 2026-11-11 (was Phase 2) |
| F36-c | Capture research, scoring and in-app notification | P1 | done | spec | — | F36-b, F11-g, F43 | In-app notifications only, no email (AD #42, 2026-11-12); a burst of captures is triaged at F43’s pace. Phase 1 scope from 2026-11-11 (was Phase 2) |
| F36-d | Existing-client check at scan | P1 | done | spec | — | F36-a, F1-a | Rev 23. Phase 1 scope from 2026-11-11 (was Phase 2) |
| F20-e | Shared inquiries inbox (info@) |
P0 | dropped | spec | — | F20-f | Dropped from V1 on 2026-09-24 (lead). info@ is handled by forwarding to a rep’s own synced mailbox — nothing to build; info@ may be added as an ordinary user. OQ-52 and OQ-54 closed. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F4-c | Migrate activities and custom fields (final migration) | P1 | dropped | spec | — | F4-b, F3-b, F34-a | Dropped 2026-09-30 (lead). PRD Rev 44 took activities and custom fields out of the migration; the final run after the data freeze is F4-d and F4-b run again, and F4-a’s report serves the client. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F31 | Global search | P0 | dropped | spec | — | F2-a, F7-a, F6-a, F26-a | Dropped 2026-10-11 (lead, PRD Rev 60). No search across all records: each list screen keeps its own search, and the revised app frame has no top bar to hold a global box. AD-O-2 closed with it. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F7-e | AI similar past quotes | P1 | dropped | spec | — | F7-c, F12 | Dropped 2026-10-11 (lead, PRD Rev 61). No AI matching of past quotes; a rep finds earlier quotes on the account and the quote list. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F16 | AI product-brief assistant | P2 | dropped | spec | — | F8-b, F12 | Dropped 2026-10-11 (lead, PRD Rev 61). The first descope lever: a rep fills the product brief (F8) by hand. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F26-e | Price-lookup page | P2 | dropped | spec | — | F26-f, F26-b, F5-f | Dropped 2026-10-11 (lead, PRD Rev 61). F26-b’s Standards book finds a standard by number or client with its published price; the Tea Room’s round (F26-f) shows the four-figure build-up and, under History, each standard’s published prices (F26-f FR-22). Recorded in Phase 1, where it was dropped (was Phase 2) |
| F17-b | Pipeline funnel, weighted forecast, leads-by-source | P0 | dropped | spec | — | F17-a, F2-b, F24 | Merged into F17-a 2026-10-11 (lead) — a ◐ split merged back; its scope is unchanged and is now F17-a’s. Recorded in Phase 1, where the merge was decided (was Phase 2) |
| F18-b | Dormant account detection | P1 | dropped | spec | — | F1-c, F18-a | Merged into F18-a 2026-10-11 (lead) — a ◐ split merged back; its scope is unchanged and is now F18-a’s. Recorded in Phase 1, where the merge was decided (was Phase 2) |
| F15-b | “What’s stuck” and ranked-leads panels | P1 | dropped | spec | — | F17-a, F6-b, F7-c, F11-g, F12 | Merged into F15-a 2026-10-11 (lead) — a ◐ split merged back; its scope is unchanged and is now F15-a’s. Recorded in Phase 1, where the merge was decided (was Phase 2) |
| F23-c | Create custom fields during import mapping | P1 | dropped | spec | — | F23-b, F34-a | Dropped 2026-10-11 (lead, PRD Rev 63). An administrator creates a custom field (F34-a) before importing; the import maps columns to fields that exist. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F36-f | Same-day follow-up email from the capture app | P1 | dropped | spec | — | F36-d, F20-c | Dropped 2026-10-11 (lead, PRD Rev 63). Empire’s 9 Sep ask; OQ-60 closed and Q15 withdrawn. The same message can go to a show’s contacts through bulk email to a saved list (F37-b), or a rep emails a lead from the CRM (F20-c). Recorded in Phase 1, where it was dropped (was Phase 2) |
| F36-e | Offline queue and sync | P1 | dropped | spec | — | F36-a | Dropped 2026-10-11 (lead, PRD Rev 64). The proposal does not name offline capture and Empire never answered Q23 of the 2026-09-03 requirements questions; client/open-questions.md Q9 had said working with no signal was agreed, and the keep-and-retry keeps that — no capture is lost (PRD Rev 65). F36-a keeps a failed upload on the phone and resends it when the app is open with a connection; no background sync. Recorded in Phase 1, where it was dropped (was Phase 2) |
| F27 | Website chatbot and live chat (AI-powered) | — | dropped | — | — | — | Dropped 2026-10-11 (PRD Rev 66), not planned after V1 either; out of V1 since 2026-08-20 (Pipedrive comparison P-23). Never decomposed, no spec. Recorded in Phase 1, where it was dropped (was in no phase) |
| F28 | Email campaigns (marketing product) | — | dropped | — | — | — | Dropped 2026-10-11 (PRD Rev 66), not planned after V1 either; out of V1 since 2026-08-20 (Pipedrive comparison P-24). The plain bulk send is F37-a (started early in Phase 1, 2026-11-06) and F37-b (Phase 2) and is not affected. Never decomposed, no spec. Recorded in Phase 1, where it was dropped (was in no phase) |
| F29 | Data enrichment | — | dropped | — | — | — | Dropped 2026-10-11 (PRD Rev 66), not planned after V1 either; out of V1 since 2026-08-20 (Pipedrive comparison P-25). The V1 lead research (F11-c) is not affected. Never decomposed, no spec. Recorded in Phase 1, where it was dropped (was in no phase) |
| F30 | LinkedIn integration | — | dropped | — | — | — | Dropped 2026-10-11 (PRD Rev 66), not planned after V1 either; out of V1 since 2026-08-20 (Pipedrive comparison P-26). Never decomposed, no spec. Recorded in Phase 1, where it was dropped (was in no phase) |
| F35 | Sales goals and targets | — | dropped | — | — | — | Dropped 2026-10-11 (PRD Rev 66), not planned after V1 either; out of V1 since 2026-08-20 (Pipedrive comparison P-33). Never decomposed, no spec. Recorded in Phase 1, where it was dropped (was in no phase) |
Phase 2
| ID | Title | Pri | Phase | Spec | Plan | Blocked By | Notes |
|---|---|---|---|---|---|---|---|
| F2-a | Deal and pipeline substrate | P0 | backlog | spec | — | F1-a, F5-f | pipeline, stage + stable stage_type (AD #11), deal; two seeded pipelines; deals read through F5-f’s visibility rule and join record_share (AD #35) |
| F2-b | Kanban boards and deal cards | P0 | backlog | spec | — | F2-a, F5-b | Rotting dot; drag between stages; header stats |
| F2-c | Deal detail and create/edit | P0 | backlog | spec | — | F2-a, F1-d | Owns the drawer; share surface (F5-g) |
| F2-d | Deal line items from the account’s standards | P0 | backlog | spec | — | F2-c, F26-b | Quantity + discount → deal value |
| F11-e | Convert lead to opportunity | P1 | backlog | spec | — | F11-f, F2-c | |
| F3-b | Activities on deals and custom activity types | P0 | backlog | spec | — | F3-a, F2-c, F5-d | |
| F17-a | Dashboard: KPI cards, pipeline funnel, forecast and leads-by-source | P0 | backlog | spec | — | F3-b, F1-c, F11-g, F2-b, F24 | Landing page; F6/F7/F18 add cards. F17-b merged in 2026-10-11 |
| F24 | Configurable pipelines | P1 | backlog | spec | — | F2-a, F5-d | OQ-28/30 |
| F18-a | Stale deal, quote-aging and dormant-account alerts | P1 | backlog | spec | — | F24, F3-b, F7-a, F1-c | Builds StaleClock; OQ-12/13. F18-b merged in 2026-10-11 |
| F6-a | Sample rounds and lifecycle board | P1 | backlog | spec | — | F2-c | Builds RoundLifecycle |
| F6-b | Sample table with stuck reasons | P1 | backlog | spec | — | F6-a | |
| F6-c | AI feedback-chase draft | P1 | backlog | spec | — | F6-b, F12, F20-c, F43 | |
| F7-a | Quote records, line items, payment terms, GP% | P1 | backlog | spec | — | F2-d | OQ-10 |
| F7-b | 8-item readiness checklist | P1 | backlog | spec | — | F7-a | Builds ChecklistEngine/GateRule |
| F7-d | GP floor and sub-floor MD approval | P1 | backlog | spec | — | F7-b, F5-d | quote.approve_sub_floor (AD #26); OQ-61 |
| F7-c | Quote revisions and aging | P1 | backlog | spec | — | F7-a | |
| F8-a | Product brief form | P1 | backlog | spec | — | F2-c | |
| F8-b ◐ | Brief open questions and completion gate | P1 | backlog | spec | — | F8-a | |
| F9 | Certification mismatch check | P1 | backlog | spec | — | F26-b, F1-d, F2-d | Gated on OQ-9; fallback = manual checklist (proposal §15) |
| F10 | Export documentation checklist | P1 | backlog | spec | — | F2-d, F26-b | Reference only |
| F14 | AI quote assistant | P1 | backlog | spec | — | F7-b, F12, F43 | Never prices |
| F15-a | AI morning briefing, what’s stuck and ranked leads | P1 | backlog | spec | — | F17-a, F12, F6-b, F7-c, F11-g, F43 | F15-b merged in 2026-10-11 |
| F19 | CRM→ERP handoff on Won | P1 | backlog | spec | — | F7-d, F9, F8-b | Builds ErpHandoffService (AD #10); OQ-2/OQ-19 |
| F21-a | Activity calendar view | P1 | backlog | spec | — | F3-b | |
| F21-b | Two-way calendar sync | P1 | backlog | spec | — | F21-a, F20-a, F20-i | Graph; future events only |
| F32-a | List views and saved filters on deals, quotes, samples and standards | P1 | backlog | spec | — | F32-d, F2-c | Narrowed 2026-11-06 (Gate 3 Run 4, reslice): these lists join F32-d’s list-view engine; the account, lead and contact lists are F32-d’s |
| F32-b | Bulk actions | P1 | backlog | spec | — | F32-a, F3-b, F43 | “Change owner” on leads and accounts moved to Phase 1 as F32-c (2026-09-30); the other actions and deal reassignment stay here |
| F23-a | Export of the deal, quote, sample and standard lists (CSV/Excel) | P1 | backlog | spec | — | F23-d, F32-a | Narrowed 2026-11-06 (Gate 3 Run 4, reslice): the export of F32-a’s lists, on F23-d’s export |
| F23-b | Spreadsheet import tool | P1 | backlog | spec | — | F4-a, F2-c, F43 | Exposes the F4-a engine |
| F33-b | File attachments on deals, quotes, samples and briefs | P1 | backlog | spec | — | F33-a, F2-c | Split from F33 2026-11-06 (Gate 3 Run 4, reslice): these records join F33-a’s attachment store |
| F34-a | Custom fields on deals, quotes, standards and samples | P1 | backlog | spec | — | F34-c, F2-c | Narrowed 2026-11-06 (Gate 3 Run 4, reslice): these records join F34-c’s definitions and forms |
| F34-b | Custom fields in list views and filters | P1 | backlog | spec | — | F34-a, F32-a | Covers every list, deals included, so it follows the deal parts (2026-11-06) |
| F25-a | Sequence builder and enrolment | P1 | backlog | spec | — | F11-f, F20-d, F3-b | OQ-25 |
| F25-b | Sequence execution with HITL steps | P1 | backlog | spec | — | F25-a, F12, F43 | FS-9; AD #13 |
Legend
- Phase:
backlog→spec→plan(orworkitem-decomposefor a feature built in waves) →dev→review→ship→done. Exit states from any phase:paused,dropped. - Pri: P0 = must-have to replace Pipedrive / critical path · P1 = core business value · P2 = supporting / enhancement. The tracker stores the same tier as
high/medium/low. - Spec / Plan columns: the spec link points at the Gate 3 stub (
Status: draft); plans land per-feature once each spec is approved (.forge/plans/<id>-<name>-plan.md, or.forge/plans/<id>/in wave mode). - ◐: a borderline split the team accepted at Gate 3 and may merge back (
/forge-decompose --resliceis the tool for the reverse direction; a merge is a hand edit plus a tracker note).
Cross-references
- PRD §In Scope (V1) + §Functional Surface (Rev 32) — origin of this list; frozen at Gate 1, live state lives here.
tracker.yamlfeatures:— structured-state mirror.engagement-gate-runs.md § Gate 3 Run 1— the audit of the decomposition pass, including the FR-5 feature-sizing table.project-prd-signals.md— live OQs, each row’sBlockscolumn re-mapped to the ids above at Gate 3; OQ-63 (past orders) raised here.- Dropped, not planned after V1: F27 chatbot/live chat, F28 campaigns (its bulk send is F37-a, done in Phase 1, and F37-b, started early in Phase 1; the segmentation builder and campaign reports stay out), F29 enrichment, F30 LinkedIn, F35 sales goals — out of V1 regardless of the Pipedrive audit since 2026-08-20, and dropped on 2026-10-11 (PRD Rev 66); each has a
droppedrow in the Phase 1 table. The post-V1 items in PRD §Deferred have no rows.
Cross-cutting NFRs (acceptance gates, not features)
| NFR | Source | Owner |
|---|---|---|
| Screens < 2s, UI interactions < 200ms, AI calls < 10s (else background job + review queue) | PRD §NFR Performance | every feature spec’s ACs |
| WCAG 2.1 AA — keyboard nav, contrast on the warm palette, status never by color alone | PRD §NFR Accessibility | every UI-bearing spec |
Audit trail (AD #36): every write and every security event (sign-in, sign-out, deactivation, role and permission changes, sharing, reassignment, exports) in one audit_event trail, written in the same transaction; never reads |
PRD §NFR Observability | F39 builds it and retrofits what is on main; every writing feature calls it |
| AI provenance: outputs tagged AI-generated + confidence + edited-by-you state | PRD §NFR Observability | every AI-surface spec |
Role/ownership data scoping enforced at service layer (not just routes), through the one visibility rule — the reporting tree, the entity’s all key and shares — for lists and single records (AD #35, AD #37) |
PRD §Users / architecture §AuthN/AuthZ | F5-f builds the rule; every endpoint-bearing spec uses it |
| Idempotent queue consumers; idempotency key on every enqueued job | AD #13 | every background-job spec |
| The six list-screen states (empty, empty-filtered, loading, error, refresh-failed with as-of label, populated) | R-FND-002 / design-system §3.2 | F5-c first, then every list screen |
Every provider seam ships a local/test stub and a fail-closed cloud guard on the FS-11 SeamGuard pattern |
R-FND-001 | F12, F11-c, F20-a, F26-a, F19 |