{
  "snapshot_date": "9 October 2026",
  "source": "Beth source delegation blueprint",
  "packages": [
    {
      "code": "P01",
      "anchor": "p01",
      "title": "Approve the pilot journeys and service catalogue",
      "group": "P",
      "parent": null,
      "result": "An approved catalogue identifies each included service and package, its evidence, owner and scope; excluded or complex cases have a clear review route.",
      "owner": "Product owner / business analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.1",
        "P01.2"
      ],
      "steps": [
        "Choose 3 pilot journeys: straightforward business setup, routine records/compliance and ordinary backlog assessment.",
        "Approve 12–15 service codes with deliverables, prerequisites, exclusions, work unit and period.",
        "Assemble 4 packages and check shared-work duplication and escalation boundaries.",
        "Record named service owners, approvers and release version; keep the remaining catalogue in draft."
      ],
      "reviewer": "Product owner and Philippine CPA / practice lead",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P01.1",
        "P01.2",
        "P01.3"
      ],
      "prerequisites": [],
      "features": [
        "quote.1",
        "quote.2",
        "start.2",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P01.1",
      "anchor": "p01-1",
      "title": "Approve the three pilot founder journeys",
      "group": "P",
      "parent": "P01",
      "result": "Three versioned journey briefs have approved outcomes and boundaries.",
      "owner": "Product owner / business analyst",
      "evidence": "Journey briefs, approval record and decision log.",
      "dependencies": [],
      "steps": [
        "Read existing setup, monthly-compliance and backlog journey drafts.",
        "List allowed founder segments and explicit exclusions for each journey.",
        "Write the observable founder outcome and human-review boundary.",
        "Obtain accountable-owner review and record unresolved decisions."
      ],
      "reviewer": "Domain reviewer",
      "inputs": [
        "P01 scope brief"
      ],
      "blocker": "If a segment or advice boundary is disputed, leave that journey draft and request the named domain decision. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [],
      "features": [
        "start.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P01.2",
      "anchor": "p01-2",
      "title": "Validate each pilot service unit and deliverable",
      "group": "P",
      "parent": "P01",
      "result": "Each selected code has a reviewed bounded service card; unknown evidence is visibly unresolved.",
      "owner": "Service owner / specialist",
      "evidence": "Service-card register, source references and review decisions.",
      "dependencies": [
        "P01.1"
      ],
      "steps": [
        "Select the proposed 12–15 pilot service codes.",
        "Define one entity, period, workload unit and included result for each code.",
        "List exclusions, required inputs, prerequisites and observable completion checks.",
        "Label each input measured, estimated or proposed; record its evidence and reviewer.",
        "Resolve duplicate codes or incompatible service definitions."
      ],
      "reviewer": "Practice lead / Philippine CPA",
      "inputs": [
        "P01.1"
      ],
      "blocker": "If evidence or professional approval is missing, retain the service in draft and identify the question needed to approve it. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.1"
      ],
      "features": [
        "quote.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P01.3",
      "anchor": "p01-3",
      "title": "Approve four packages without overlapping work",
      "group": "P",
      "parent": "P01",
      "result": "Four reviewed package definitions have clear boundaries and no duplicate shared work.",
      "owner": "Operations / service-design owner",
      "evidence": "Package composition matrix, overlap examples and approval record.",
      "dependencies": [
        "P01.2"
      ],
      "steps": [
        "Match one approved founder need to each proposed package.",
        "List included service codes, prerequisites and conditional additions.",
        "Check entity/period/work-unit overlaps and remove duplicate work.",
        "Write founder-facing inclusions, exclusions and escalation options.",
        "Record package owner and versioned approval."
      ],
      "reviewer": "Finance owner and domain reviewer",
      "inputs": [
        "P01.1",
        "P01.2"
      ],
      "blocker": "If the component services conflict or lack approval, block package release and list the required service decisions. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.2"
      ],
      "features": [
        "quote.2",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P02",
      "anchor": "p02",
      "title": "Map the revised 20-topic interview to Beth decisions",
      "group": "P",
      "parent": null,
      "result": "All 20 topics map to a named decision, structured record, approver and test; no legacy 23-topic map is silently used.",
      "owner": "Business analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.1",
        "P02.1",
        "P02.2"
      ],
      "steps": [
        "Inventory the revised collection topics and identify the exact decision each answer changes.",
        "Define typed outputs, units, periods, service codes and evidence links for each topic.",
        "Assign the appropriate reviewer and one acceptance example per topic.",
        "Preserve unknowns and measured-versus-estimated evidence; retire or revise questions without a useful consumer."
      ],
      "reviewer": "Product owner and domain / finance reviewers",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P02.1",
        "P02.2",
        "P02.3"
      ],
      "prerequisites": [
        "P01.1"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P02.1",
      "anchor": "p02-1",
      "title": "Reconcile the current 20 topics with the learning map",
      "group": "P",
      "parent": "P02",
      "result": "A versioned crosswalk covers all 20 current topics and explains each retired or changed legacy link.",
      "owner": "Business analyst",
      "evidence": "Current-to-legacy crosswalk and accepted mapping review.",
      "dependencies": [
        "P01.1"
      ],
      "steps": [
        "List s1–s8, m1–m6 and e1–e6 with the current collection version.",
        "Compare them against the legacy 23-question learning audit.",
        "Link each current topic to a specific founder or business decision.",
        "Record obsolete mappings and missing consumers without altering submitted snapshots."
      ],
      "reviewer": "Product owner",
      "inputs": [
        "collection-spec.mjs",
        "Beth_Learning_Logic.json"
      ],
      "blocker": "If a topic has no decision consumer, mark the gap and seek a product decision; do not invent a consumer. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.1"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P02.2",
      "anchor": "p02-2",
      "title": "Define typed candidate records for interview answers",
      "group": "P",
      "parent": "P02",
      "result": "The approved record contract preserves provenance and rejects invented defaults or executable interview text.",
      "owner": "Data / backend engineer",
      "evidence": "Candidate schema, validation table and redacted examples.",
      "dependencies": [
        "P02.1"
      ],
      "steps": [
        "Define field type, unit, period, service ID and allowed values for each consumer.",
        "Keep unknown, estimate, measured observation and proposed policy as separate states.",
        "Retain exact submission/topic/field and evidence references.",
        "Specify checks for dates, missing units, conflicting scope and permitted rule operators.",
        "Provide one valid, one unknown and one invalid record example per candidate type."
      ],
      "reviewer": "Business analyst and domain reviewer",
      "inputs": [
        "P02.1"
      ],
      "blocker": "If unit, scope or evidence meaning is unresolved, keep the candidate incomplete and route the question to its decision owner. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P02.1"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P02.3",
      "anchor": "p02-3",
      "title": "Approve interview consumers and collection guidance",
      "group": "P",
      "parent": "P02",
      "result": "Each topic has one named decision consumer, reviewer role and test, with examples visibly separated from approved rules.",
      "owner": "Business analyst / interview coordinator",
      "evidence": "Signed consumer matrix and guidance review.",
      "dependencies": [
        "P02.2"
      ],
      "steps": [
        "Assign a reviewer role and acceptance example to every topic.",
        "Explain how each answer changes scope, knowledge, pricing, matching or evaluation.",
        "Check that contributors see anonymisation, evidence-basis and honest-unknown instructions.",
        "Keep model answers labelled illustrative and separate from respondent evidence.",
        "Approve the map and record revision/retirement decisions."
      ],
      "reviewer": "Service, finance and expert reviewers",
      "inputs": [
        "P02.1",
        "P02.2"
      ],
      "blocker": "If a reviewer is not appointed or evidence is unsuitable, report that topic as awaiting review rather than complete. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P02.2"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P03",
      "anchor": "p03",
      "title": "Implement review and approval for submitted interview packs",
      "group": "P",
      "parent": null,
      "result": "A reviewer can return a submission, contributor corrects it, and a separately approved version retains its audit trail; raw answers cannot change Beth's live output.",
      "owner": "Product owner / workflow analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P02.3",
        "P16",
        "P03.1",
        "P03.2"
      ],
      "steps": [
        "Add reviewer roles and assign submitted snapshots without exposing other contributors' private studies.",
        "Provide approve, reject and return-for-correction decisions with reasons and preserved history.",
        "Extract structured candidates while retaining exact answer/evidence references.",
        "Display unresolved disagreements and block unreviewed input from live knowledge or prices."
      ],
      "reviewer": "Accountable service, finance or expert approver",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P03.1",
        "P03.2",
        "P03.3"
      ],
      "prerequisites": [
        "P02.3",
        "P16"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P03.1",
      "anchor": "p03-1",
      "title": "Define review roles and candidate state transitions",
      "group": "P",
      "parent": "P03",
      "result": "An approved matrix identifies every review action, authorised role and required record.",
      "owner": "Product owner / workflow analyst",
      "evidence": "Role/action matrix and state diagram.",
      "dependencies": [
        "P02.3",
        "P16"
      ],
      "steps": [
        "List contributor, assigned reviewer, manager, expert and publisher actions.",
        "Define captured, draft, conflict, reviewed, approved and returned states.",
        "Specify who can view identities, evidence and private commercial inputs.",
        "Define return reasons, resubmission links and reviewer assignment rules.",
        "Approve the transition/permission matrix."
      ],
      "reviewer": "Review lead and access owner",
      "inputs": [
        "P02.3",
        "P16 business-role policy"
      ],
      "blocker": "If reviewer authority or data access is disputed, stop that transition and request an access-policy decision. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P02.3",
        "P16"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P03.2",
      "anchor": "p03-2",
      "title": "Build assigned review and return-for-correction",
      "group": "P",
      "parent": "P03",
      "result": "An assigned reviewer can return a pack; a corrected version retains both snapshots and decisions.",
      "owner": "Backend / frontend engineer",
      "evidence": "Redacted walkthrough, permission tests and review-history export.",
      "dependencies": [
        "P03.1"
      ],
      "steps": [
        "Reuse immutable submitted packs instead of reviewing mutable drafts.",
        "Provide an assigned-review queue and evidence/gap view.",
        "Record approve, reject or return decisions with reason and reviewer.",
        "Link corrected resubmissions to the original without overwriting history.",
        "Verify unauthorised accounts cannot inspect or decide a review."
      ],
      "reviewer": "Review lead and QA",
      "inputs": [
        "P03.1",
        "Cloud account storage verified"
      ],
      "blocker": "If cloud identity or review storage is unavailable, mark implementation blocked and retain the approved contract. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P03.1"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P03.3",
      "anchor": "p03-3",
      "title": "Resolve candidate conflicts before release handoff",
      "group": "P",
      "parent": "P03",
      "result": "Only reviewed candidates enter the release bundle; unresolved conflicts remain excluded and traceable.",
      "owner": "Review coordinator",
      "evidence": "Conflict register, decisions and candidate-bundle manifest.",
      "dependencies": [
        "P03.2"
      ],
      "steps": [
        "Compare conflicting candidates by unit, segment, period and evidence basis.",
        "Request the missing evidence or correction from the appropriate contributor.",
        "Record accepted variants or a reasoned resolution by the accountable reviewer.",
        "Create an approved candidate bundle with unresolved exclusions visible.",
        "Hand the bundle and decisions to the release owner."
      ],
      "reviewer": "Qualified service/finance/expert owner",
      "inputs": [
        "P03.2",
        "P02.2"
      ],
      "blocker": "Do not average incompatible answers; block affected candidates until the accountable reviewer resolves or preserves distinct variants. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P03.2"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P04",
      "anchor": "p04",
      "title": "Publish applicable knowledge with verified citations",
      "group": "P",
      "parent": null,
      "result": "Every material pilot claim resolves to its supporting applicable passage; superseded information cannot appear as current and unavailable evidence triggers the approved fallback.",
      "owner": "Knowledge analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.1",
        "P03.3",
        "P04.1",
        "P14.2",
        "P04.2"
      ],
      "steps": [
        "Create the approved fact/source registry with authority, original passage, locator, effective dates and applicable tax period.",
        "Approve a small FAQ set and the pilot BIR, CTA and Supreme Court source families.",
        "Implement current-versus-historical retrieval and supersession, cache expiry and changed-source review.",
        "Test stale, blocked, conflicting and unsupported sources; provide bounded help and specialist escalation.",
        "Accept the PDF knowledge lifecycle and engine ownership documented at beth2.top/scope#rag; revalidate the affected effort allocations."
      ],
      "reviewer": "Philippine tax / legal reviewer and knowledge QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting.",
        "RAG/document-lifecycle design: beth2.top/scope#rag; approved compatibility, licence and freshness decisions."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P04.1",
        "P04.2",
        "P04.3"
      ],
      "prerequisites": [
        "P01.1",
        "P03.3",
        "P14.2"
      ],
      "features": [
        "sources.1",
        "sources.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Existing planning allocations predate the 9 October RAG refinement. Validate the PDF/CMS/durable-worker integration and test effort within knowledge, administration, QA and operations before assignment; no additional total has been approved.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P04.1",
      "anchor": "p04-1",
      "title": "Approve pilot facts and supporting source passages",
      "group": "P",
      "parent": "P04",
      "result": "Every approved fact has inspectable support, applicability and a responsible reviewer.",
      "owner": "Knowledge analyst",
      "evidence": "Fact/source register, locators and expert approvals. Include the PDF/source schema, role-access test, version history, licence decision and recorded editor walkthrough.",
      "dependencies": [
        "P01.1",
        "P03.3"
      ],
      "steps": [
        "Select a bounded FAQ set for the approved pilot journeys.",
        "Capture exact BIR, CTA or Supreme Court document and supporting locator.",
        "Distinguish legal rule, expert interpretation and internal practice policy.",
        "Record applicability, effective dates, amendment checks and source owner.",
        "Obtain qualified review; keep uncertain dates or interpretations unpublished.",
        "Configure the single Directus knowledge workspace, record/field permissions and production licence decision; avoid duplicate knowledge administration.",
        "Register PDFs with official URL/publication channel, document ID/version, page locators, applicability, source owner and freshness policy.",
        "Let a nontechnical editor upload, review extracted metadata, test examples and request approval; uncertain OCR or dates remain candidates."
      ],
      "reviewer": "Philippine tax/legal reviewer",
      "inputs": [
        "P01.1",
        "P03.3",
        "RAG/document-lifecycle design: beth2.top/scope#rag; approved compatibility, licence and freshness decisions."
      ],
      "blocker": "If source support or applicability cannot be established, retain the fact as a candidate and specify a human-review route. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.1",
        "P03.3"
      ],
      "features": [
        "sources.1",
        "sources.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Existing planning allocations predate the 9 October RAG refinement. Validate the PDF/CMS/durable-worker integration and test effort within knowledge, administration, QA and operations before assignment; no additional total has been approved.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P04.2",
      "anchor": "p04-2",
      "title": "Verify retrieval and citation support against claims",
      "group": "P",
      "parent": "P04",
      "result": "Answers cite the actual applicable support and do not turn fetched source text into agent instructions.",
      "owner": "AI / data engineer",
      "evidence": "Redacted answer-to-passage trace and claim-support test results. Include original-PDF versus extracted-table checks, ingestion manifest, active-version transaction proof and held-out retrieval results.",
      "dependencies": [
        "P04.1",
        "P14.2"
      ],
      "steps": [
        "Retrieve relevant approved passages for the selected founder facts and tax period.",
        "Retain source/version IDs and exact evidence used by the answer.",
        "Check each material claim against the cited passage.",
        "Reject unsupported claims and disclose cached or incomplete evidence.",
        "Test current, historical, contradictory and prompt-injected source cases.",
        "Run Docling conversion and LlamaIndex ingestion as libraries in one worker with persistent IDs/hashes and page/section provenance.",
        "Use PostgreSQL full-text/identifier search plus pgvector retrieval; rank relevant passages and retain tables/exceptions.",
        "Stage a complete approved passage version and activate it consistently; enforce approval/version/date checks before prompt assembly.",
        "Benchmark PDF extraction, retrieval and citation support on expert-approved cases; reject unsupported or uncertain consequential guidance."
      ],
      "reviewer": "Knowledge reviewer and QA",
      "inputs": [
        "P04.1",
        "P14 runtime contract",
        "RAG/document-lifecycle design: beth2.top/scope#rag; approved compatibility, licence and freshness decisions."
      ],
      "blocker": "If a claim lacks support, remove or qualify it and request review; do not fabricate a citation to complete the answer. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P04.1",
        "P14.2"
      ],
      "features": [
        "sources.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Existing planning allocations predate the 9 October RAG refinement. Validate the PDF/CMS/durable-worker integration and test effort within knowledge, administration, QA and operations before assignment; no additional total has been approved.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P04.3",
      "anchor": "p04-3",
      "title": "Test source freshness, retirement and outage fallback",
      "group": "P",
      "parent": "P04",
      "result": "Superseded evidence cannot be reused as current; all tested outages lead to a documented verified fallback or review.",
      "owner": "Knowledge / data engineer",
      "evidence": "Freshness policy, retirement trace and outage test report. Include durable-workflow recovery trace, reconciliation report, freshness dashboard and retirement/cache invalidation results.",
      "dependencies": [
        "P04.2"
      ],
      "steps": [
        "Define review-due, changed-source and retirement triggers.",
        "Expire affected cached answers while preserving historical versions.",
        "Test changed hashes, later amendments and uncertain effective dates.",
        "Test blocked sources and verify alternate-copy identity before reuse.",
        "Record bounded fallback wording and specialist escalation when evidence remains unavailable.",
        "Implement Temporal schedules and resumable activities for source checks and ingestion with bounded retries/timeouts and duplicate-safe writes.",
        "Monitor publication lists for new amendments and selected document hashes; preserve last successful checks and review-due status.",
        "Use explicit retirement and dependent answer-cache invalidation; do not interpret website outages or partial-sync absence as deletion.",
        "Reconcile approved/indexed versions and alert on failures, lag and overdue reviews; delayed events cannot reactivate retired versions.",
        "Test interruption recovery, duplicate events, scanned PDFs, partial sync, publication changes and offline fallback with exact expected/actual evidence."
      ],
      "reviewer": "Domain reviewer and QA",
      "inputs": [
        "P04.1",
        "P04.2",
        "RAG/document-lifecycle design: beth2.top/scope#rag; approved compatibility, licence and freshness decisions."
      ],
      "blocker": "If freshness or alternate identity is unresolved, quarantine current use and record the source owner's next check. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P04.2"
      ],
      "features": [
        "sources.1",
        "sources.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Existing planning allocations predate the 9 October RAG refinement. Validate the PDF/CMS/durable-worker integration and test effort within knowledge, administration, QA and operations before assignment; no additional total has been approved.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P05",
      "anchor": "p05",
      "title": "Validate founder profiling and scope confirmation",
      "group": "P",
      "parent": null,
      "result": "The same confirmed facts yield consistent scope, volunteered information is not repeatedly asked, unknown values are not invented, and risk cases receive the documented review route.",
      "owner": "Business analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.2",
        "P02.2",
        "P05.1",
        "P04.1",
        "P05.2"
      ],
      "steps": [
        "Map approved founder facts to service eligibility, prerequisites, urgency and escalation.",
        "Track unknown, approximate and confirmed facts separately and retain corrections.",
        "Choose the easiest unresolved question that changes a scope or review decision.",
        "Test pilot cases including 'not sure', official notices and out-of-scope situations; request founder confirmation of resulting scope."
      ],
      "reviewer": "Domain reviewer and founder-experience QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P05.1",
        "P05.2",
        "P05.3"
      ],
      "prerequisites": [
        "P01.2",
        "P02.2",
        "P04.1"
      ],
      "features": [
        "profile.1",
        "profile.2",
        "start.1",
        "start.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P05.1",
      "anchor": "p05-1",
      "title": "Approve founder fact definitions and correction rules",
      "group": "P",
      "parent": "P05",
      "result": "No pilot rule relies on an undefined fact or silently converts an unknown into a confirmed value.",
      "owner": "Business analyst",
      "evidence": "Fact dictionary, correction examples and reviewer sign-off.",
      "dependencies": [
        "P01.2",
        "P02.2"
      ],
      "steps": [
        "Define canonical fact keys and units for the pilot decisions.",
        "Record volunteered information with confirmed, approximate or unknown state.",
        "Define how conflicting answers are clarified and corrections are attributed.",
        "Identify material changes requiring scope reconfirmation.",
        "Approve a fact-to-question-to-decision crosswalk."
      ],
      "reviewer": "Domain reviewer",
      "inputs": [
        "P01.2",
        "P02.2"
      ],
      "blocker": "If fact meaning is ambiguous, leave it unknown and request one clarifying definition before implementing a rule. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.2",
        "P02.2"
      ],
      "features": [
        "start.2",
        "profile.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P05.2",
      "anchor": "p05-2",
      "title": "Implement next-question and escalation rules",
      "group": "P",
      "parent": "P05",
      "result": "Pilot routes preserve uncertainty, avoid repetitive questions and choose the approved review boundary.",
      "owner": "AI / backend engineer",
      "evidence": "Decision table and typical/unknown/urgent routing results.",
      "dependencies": [
        "P05.1",
        "P04.1"
      ],
      "steps": [
        "Map approved facts to eligible work, missing prerequisites and escalation.",
        "Ask the easiest unresolved question that changes the decision.",
        "Skip already volunteered facts and explain why a new fact matters.",
        "Prioritise stated deadlines and qualified review for official notices.",
        "Record the rule/version and reason for each routing decision."
      ],
      "reviewer": "Product owner and domain reviewer",
      "inputs": [
        "P05.1",
        "P04.1"
      ],
      "blocker": "If required applicability or urgency rules are unapproved, route to a person instead of guessing the service outcome. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P05.1",
        "P04.1"
      ],
      "features": [
        "start.1",
        "start.2",
        "profile.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P05.3",
      "anchor": "p05-3",
      "title": "Verify founder confirmation and scope corrections",
      "group": "P",
      "parent": "P05",
      "result": "Reviewed scenarios produce the right scope, recorded confirmation and traceable correction history.",
      "owner": "QA / conversational UX reviewer",
      "evidence": "Scenario transcripts, confirmation records and reviewer decisions.",
      "dependencies": [
        "P05.2"
      ],
      "steps": [
        "Run normal, conflicting and not-sure founder conversations.",
        "Show a plain-language fact and proposed-scope summary.",
        "Record explicit confirmation and the exact profile snapshot.",
        "Change a material workload or tax-status fact and require reconfirmation.",
        "Verify a quote never treats unconfirmed guesses as verified inputs."
      ],
      "reviewer": "Product owner and domain reviewer",
      "inputs": [
        "P05.2"
      ],
      "blocker": "If a critical scope error occurs, report the failing rule and block that route's acceptance until corrected. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P05.2"
      ],
      "features": [
        "start.2",
        "profile.1",
        "profile.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P06",
      "anchor": "p06",
      "title": "Make pilot estimates replayable from approved pricing inputs",
      "group": "P",
      "parent": null,
      "result": "A saved quote can be reproduced exactly; changing an approved allowance affects only the relevant units; missing critical inputs prevents a firm quote.",
      "owner": "Service-costing analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.2",
        "P03.3",
        "P06.1",
        "P01.3",
        "P06.2",
        "P05.3"
      ],
      "steps": [
        "Approve service units, base allowances, workload increments, role effort and commercial policies.",
        "Replace hardcoded quantity allowances with validated versioned rule inputs where identified.",
        "Prevent duplicate same-entity/same-period work and separate pass-through fees and conditional additions.",
        "Save quote inputs, assumptions and rule version; test counts, missing critical facts and quote replay."
      ],
      "reviewer": "Finance owner, service owner and pricing QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P06.1",
        "P06.2",
        "P06.3"
      ],
      "prerequisites": [
        "P01.2",
        "P03.3",
        "P01.3",
        "P05.3"
      ],
      "features": [
        "portal.2",
        "profile.1",
        "profile.2",
        "quote.1",
        "quote.2",
        "report.1",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P06.1",
      "anchor": "p06-1",
      "title": "Approve pricing units and evidence-based drivers",
      "group": "P",
      "parent": "P06",
      "result": "A reviewed pricing-input contract identifies units, evidence basis and authority; confidential values remain restricted.",
      "owner": "Service-costing analyst",
      "evidence": "Redacted driver register, evidence references and approval manifest.",
      "dependencies": [
        "P01.2",
        "P03.3"
      ],
      "steps": [
        "Specify entity, period, currency, work unit and increment for each pilot service.",
        "Separate productive delivery/review/coordination hours from waiting days.",
        "Label measured jobs, professional estimates and proposed commercial policy distinctly.",
        "Define assumptions, exclusions, minimum inputs and fee-policy authority.",
        "Provide approved version references without posting confidential amounts to the shared board."
      ],
      "reviewer": "Finance owner and practice lead",
      "inputs": [
        "P01.2",
        "P03.3"
      ],
      "blocker": "If costs or policy approval are missing, retain a draft estimate basis and request the finance decision; do not invent rates. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.2",
        "P03.3"
      ],
      "features": [
        "quote.1",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P06.2",
      "anchor": "p06-2",
      "title": "Make quantities and bundles follow approved rule versions",
      "group": "P",
      "parent": "P06",
      "result": "Approved rule changes affect the correct quantities, and overlapping work is never charged twice.",
      "owner": "Backend engineer",
      "evidence": "Boundary calculations, overlap checks and rule-version change trace.",
      "dependencies": [
        "P06.1",
        "P01.3"
      ],
      "steps": [
        "Locate existing hardcoded base allowances and quantity rules.",
        "Replace only approved inputs with versioned validated rule records.",
        "Calculate workload increments without LLM arithmetic.",
        "Deduplicate shared work by entity and period and respect prerequisites.",
        "Test boundary counts, conditional extras and wrong-unit/currency/period rejection."
      ],
      "reviewer": "Service owner and QA",
      "inputs": [
        "P06.1",
        "P01.3"
      ],
      "blocker": "If rule interpretation differs from the reviewed unit, stop that service calculation and return the definition for correction. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P06.1",
        "P01.3"
      ],
      "features": [
        "profile.1",
        "quote.1",
        "quote.2",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P06.3",
      "anchor": "p06-3",
      "title": "Verify quote replay and founder-facing estimate boundaries",
      "group": "P",
      "parent": "P06",
      "result": "The exact saved estimate is reproducible and its uncertainty/exclusions are visible to the founder.",
      "owner": "QA / backend engineer",
      "evidence": "Redacted quote snapshots, replay results and missing-input test report.",
      "dependencies": [
        "P06.2",
        "P05.3"
      ],
      "steps": [
        "Save confirmed inputs, explicit assumptions and quote/rule version.",
        "Explain range, billing period, exclusions and pass-through fees.",
        "Block firm quotes where critical inputs remain unknown.",
        "Replay saved quotations after a later rule-version change.",
        "Verify new prices affect future quotes while previous accepted versions stay intact."
      ],
      "reviewer": "Finance owner and domain reviewer",
      "inputs": [
        "P06.2",
        "P05.3"
      ],
      "blocker": "If saved inputs or rule versions are incomplete, mark the quote unreplayable and block approval until the record is repaired. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P06.2",
        "P05.3"
      ],
      "features": [
        "profile.2",
        "quote.1",
        "quote.2",
        "report.1",
        "portal.2",
        "workshop.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P07",
      "anchor": "p07",
      "title": "Onboard and verify the pilot specialist roster",
      "group": "P",
      "parent": null,
      "result": "Every recommended specialist has verified eligibility for the exact job; an unavailable person is not promised as immediately deployable.",
      "owner": "Specialist operations coordinator",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.2",
        "P07.1",
        "P07.2"
      ],
      "steps": [
        "Recruit the scoped 8–12 pilot specialists and verify service-specific capabilities and credentials.",
        "Record coverage, language, seniority, conflicts and capacity with owners and review dates.",
        "Define hard eligibility filters before ranking service fit or location.",
        "Test available, busy, offline, unqualified and no-match scenarios; save understandable match reasons."
      ],
      "reviewer": "Practice lead / credential reviewer and operations",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P07.1",
        "P07.2",
        "P07.3"
      ],
      "prerequisites": [
        "P01.2"
      ],
      "features": [
        "handoff.1",
        "specialists.1",
        "specialists.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P07.1",
      "anchor": "p07-1",
      "title": "Verify service-specific specialist credentials and coverage",
      "group": "P",
      "parent": "P07",
      "result": "Each eligible pilot roster entry has verified job-specific capability and explicit limitations.",
      "owner": "Specialist operations coordinator",
      "evidence": "Redacted roster, private verification references and review decisions.",
      "dependencies": [
        "P01.2"
      ],
      "steps": [
        "Confirm the proposed 8–12 pilot practitioners and service codes.",
        "Record qualification type, issuer, review/expiry and verification reference privately.",
        "Verify actual service experience, segment, language and location/remote coverage.",
        "List professional limitations and incompatible engagements.",
        "Approve roster entries or record missing evidence."
      ],
      "reviewer": "Practice lead / credential reviewer",
      "inputs": [
        "P01.2"
      ],
      "blocker": "If capability or a required qualification is unverified, exclude the practitioner from that service's eligible results. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.2"
      ],
      "features": [
        "specialists.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P07.2",
      "anchor": "p07-2",
      "title": "Define capacity, acceptance and no-reply policies",
      "group": "P",
      "parent": "P07",
      "result": "Availability promises require verified status and explicit acceptance, with documented fallback.",
      "owner": "Specialist operations owner",
      "evidence": "Capacity register, status-expiry examples and signed handoff policy.",
      "dependencies": [
        "P07.1"
      ],
      "steps": [
        "Collect productive capacity, lead time and callback target for each pilot specialist.",
        "Define explicit available/busy/offline states and expiry.",
        "Identify backup roles and the acceptance needed before promising a slot.",
        "Define no-reply, declined-job and reassignment handling.",
        "Approve the operating policy without treating online activity as acceptance."
      ],
      "reviewer": "Practice lead / operations manager",
      "inputs": [
        "P07.1"
      ],
      "blocker": "If a specialist has not confirmed capacity, display unavailable or pending and route the case to its operations owner. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P07.1"
      ],
      "features": [
        "specialists.1",
        "handoff.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P07.3",
      "anchor": "p07-3",
      "title": "Test eligibility ranking and selected-specialist persistence",
      "group": "P",
      "parent": "P07",
      "result": "No ineligible practitioner is recommended and every selected specialist remains traceable across the handoff.",
      "owner": "Backend engineer / QA",
      "evidence": "Matching fixtures, reasons and selection/reassignment trace.",
      "dependencies": [
        "P07.2"
      ],
      "steps": [
        "Apply verified skills, required credentials, coverage and conflicts as hard filters.",
        "Rank only eligible people with readable reasons.",
        "Test nearer-unqualified, expired, busy/offline and no-match cases.",
        "Persist exact specialist/profile IDs on selection.",
        "Verify downstream appointment and case keep that selection or an audited reassignment."
      ],
      "reviewer": "Specialist operations reviewer",
      "inputs": [
        "P07.1",
        "P07.2"
      ],
      "blocker": "If filtering or identity linkage fails, suppress that match and report the roster or mapping correction required. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P07.2"
      ],
      "features": [
        "specialists.1",
        "specialists.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P08",
      "anchor": "p08",
      "title": "Complete supervised cases and additional-work approval",
      "group": "P",
      "parent": null,
      "result": "A founder sees only their cases, a specialist sees only assigned cases, repeated acceptance cannot duplicate a job, and unapproved extra work never starts.",
      "owner": "Backend engineer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P06.3",
        "P07.3",
        "P08.1",
        "P16",
        "P08.2"
      ],
      "steps": [
        "Verify quote acceptance creates one saved case containing confirmed scope, version and assignment.",
        "Implement client-versus-assigned-specialist permissions, private document access and milestones.",
        "Verify the case links to P17’s accepted consultation lifecycle without duplicating booking implementation",
        "Require founder approval of priced additional work; record assignment changes and staff follow-up."
      ],
      "reviewer": "Case operations and permission / workflow QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P08.1",
        "P08.2",
        "P08.3"
      ],
      "prerequisites": [
        "P06.3",
        "P07.3",
        "P16"
      ],
      "features": [
        "handoff.3",
        "portal.1",
        "portal.2",
        "report.1",
        "specialists.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P08.1",
      "anchor": "p08-1",
      "title": "Verify accepted scope creates one traceable case",
      "group": "P",
      "parent": "P08",
      "result": "Repeated acceptance creates one case with the agreed scope and a visible responsible role/next action.",
      "owner": "Backend engineer",
      "evidence": "Redacted case record, state-transition checks and retry result.",
      "dependencies": [
        "P06.3",
        "P07.3"
      ],
      "steps": [
        "Define case states, responsible role and allowed transitions.",
        "Create a case from the exact accepted quote/profile/specialist versions.",
        "Give retries one identity so acceptance creates one case.",
        "Show owner, current milestone and next action to the client.",
        "Record reassignment and staff-owned follow-up without promising autonomous recovery."
      ],
      "reviewer": "Case operations and QA",
      "inputs": [
        "P06.3",
        "P07.3",
        "Cloud /cases storage verified"
      ],
      "blocker": "If scope or specialist identity is unresolved, keep acceptance pending and ask the authorised owner to resolve it. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P08. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P06.3",
        "P07.3"
      ],
      "features": [
        "report.1",
        "specialists.2",
        "handoff.3",
        "portal.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P08.2",
      "anchor": "p08-2",
      "title": "Define document readiness and additional-work acceptance",
      "group": "P",
      "parent": "P08",
      "result": "A case has a usable readiness checklist; missing evidence and unapproved extra work remain visibly blocked.",
      "owner": "Case operations analyst",
      "evidence": "Document-preparation checklist, redacted change proposal and approval history.",
      "dependencies": [
        "P08.1",
        "P16"
      ],
      "steps": [
        "Translate service prerequisites into a document-type/period checklist.",
        "Separate quick intake answers from later secure document requests.",
        "Record missing records, permitted substitutes and the reason work must pause.",
        "Propose extra work with exact deliverable, fee version and acceptance checks.",
        "Require authorised client approval before starting the changed scope."
      ],
      "reviewer": "Practice lead and authorised client representative",
      "inputs": [
        "P08.1",
        "P16 secure file controls"
      ],
      "blocker": "If required records or approval are absent, pause only the affected milestone and record who must supply or approve the next input. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P08. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P08.1",
        "P16"
      ],
      "features": [
        "portal.1",
        "portal.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P08.3",
      "anchor": "p08-3",
      "title": "Verify case milestones, messages and completion states",
      "group": "P",
      "parent": "P08",
      "result": "A case retains correct scope/owner/messages, rejects unapproved work, and closes only against reviewed delivery evidence.",
      "owner": "Booking / case operations engineer",
      "evidence": "Approved state table, redacted message history, retry/denial results and reviewed delivery sample",
      "dependencies": [
        "P08.1",
        "P08.2"
      ],
      "steps": [
        "Define case/work states and the authorised actor for each transition",
        "Retain assigned specialist and approved scope across messages and follow-ups",
        "Attempt start of unapproved/rejected additional work and require rejection",
        "Retry start/completion actions and verify one recorded transition and audit entry",
        "Record delivery output against each agreed milestone and unresolved exception",
        "Obtain client-facing completion review; link consultation work to P17 rather than duplicating booking controls"
      ],
      "reviewer": "Operations manager and QA",
      "inputs": [
        "P08.1 case state and agreed service outcome"
      ],
      "blocker": "If a milestone or approval is missing, leave the affected work/case pending and record the required owner decision. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P08. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P08.1",
        "P08.2"
      ],
      "features": [
        "specialists.2",
        "portal.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P09",
      "anchor": "p09",
      "title": "Connect one live founder channel and specialist handoff",
      "group": "P",
      "parent": null,
      "result": "A real founder reaches the correct shared inbox; only one specialist owns a conversation; AI stays paused during takeover and failed delivery does not lose the case.",
      "owner": "Integration engineer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P07.3",
        "P08.1",
        "P16",
        "P09.1",
        "P07.2",
        "P09.2",
        "P13"
      ],
      "steps": [
        "Prove one Telegram founder channel and website-to-shared-inbox identity bridge.",
        "Require explicit specialist ownership and available/busy/offline status with expiry.",
        "Pause Beth during accepted human takeover and suppress delayed AI replies.",
        "Retain unanswered tickets with consent, timeout/reassignment and explicit return to Beth.",
        "Persist alert delivery IDs; retry without duplicate tickets and display failures."
      ],
      "reviewer": "Support operations, security and integration QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P09.1",
        "P09.2",
        "P09.3"
      ],
      "prerequisites": [
        "P07.3",
        "P08.1",
        "P16",
        "P07.2",
        "P13"
      ],
      "features": [
        "handoff.1",
        "handoff.2",
        "handoff.3",
        "portal.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P09.1",
      "anchor": "p09-1",
      "title": "Prove one Telegram and website shared-inbox bridge",
      "group": "P",
      "parent": "P09",
      "result": "A founder's website and Telegram messages resolve to the correct authorised case without duplicate tickets.",
      "owner": "Integration engineer",
      "evidence": "Channel setup manifest, redacted ticket trace and routing/deduplication tests.",
      "dependencies": [
        "P07.3",
        "P08.1",
        "P16"
      ],
      "steps": [
        "Select the approved pilot channel and shared-inbox destination.",
        "Map verified founder, conversation and case identities.",
        "Send a consented redacted brief into the correct inbox.",
        "Deduplicate repeated inbound events and retain ticket identifiers.",
        "Test wrong-account routing and rejected/expired access."
      ],
      "reviewer": "Support operations and access reviewer",
      "inputs": [
        "P07.3",
        "P08.1",
        "P16 identity policy"
      ],
      "blocker": "If provider access or identity linkage is unavailable, retain manual supervised handoff and report the exact account/connector requirement. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P09. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P07.3",
        "P08.1",
        "P16"
      ],
      "features": [
        "handoff.1",
        "handoff.2",
        "handoff.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P09.2",
      "anchor": "p09-2",
      "title": "Verify exclusive human ownership and AI pause",
      "group": "P",
      "parent": "P09",
      "result": "One person owns the conversation and Beth cannot speak over active human takeover.",
      "owner": "Realtime / backend engineer",
      "evidence": "Concurrent-accept, late-reply, expiry and resume test results.",
      "dependencies": [
        "P09.1",
        "P07.2"
      ],
      "steps": [
        "Require a verified specialist to accept conversation ownership.",
        "Atomically reject competing simultaneous accepts.",
        "Pause Beth and suppress late generated replies after takeover.",
        "Expire stale presence and retain disconnection status.",
        "Require explicit return-to-Beth before automated replies resume."
      ],
      "reviewer": "Support operations and QA",
      "inputs": [
        "P09.1",
        "P07.2"
      ],
      "blocker": "If ownership is uncertain, pause automated posting and assign operations to reconcile the ticket rather than choose a speaker silently. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P09. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P09.1",
        "P07.2"
      ],
      "features": [
        "handoff.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P09.3",
      "anchor": "p09-3",
      "title": "Test no-reply tickets and channel delivery receipts",
      "group": "P",
      "parent": "P09",
      "result": "No reply retains an owned follow-up task; retries cannot duplicate the handoff or expose an unconsented brief.",
      "owner": "Support integration engineer",
      "evidence": "No-reply walkthrough, redacted channel receipts and reassignment/withdrawal tests.",
      "dependencies": [
        "P09.2",
        "P13"
      ],
      "steps": [
        "Retain the case/ticket when no specialist answers.",
        "Record callback consent, target and accountable fallback role.",
        "Save channel acknowledgement and failure states separately from case state.",
        "Retry or reassign with duplicate-safe ticket/action receipts.",
        "Verify contact withdrawal or changed assignment stops inappropriate sharing."
      ],
      "reviewer": "Support operations reviewer",
      "inputs": [
        "P09.2",
        "P13 sharing-consent policy"
      ],
      "blocker": "If delivery remains unacknowledged, keep it failed/pending with an operations owner; never report sent as received. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P09. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P09.2",
        "P13"
      ],
      "features": [
        "handoff.1",
        "handoff.2",
        "handoff.3",
        "portal.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P10",
      "anchor": "p10",
      "title": "Enable business staff to preview, publish and roll back changes",
      "group": "P",
      "parent": null,
      "result": "A trained manager corrects a routine rule, previews its impact, obtains approval, publishes and reverses it without changing code or database records.",
      "owner": "Product / UX analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P03.1",
        "P01.3",
        "P16",
        "P10.1",
        "P03.3",
        "P04.1",
        "P06.2",
        "P10.2",
        "P04.3"
      ],
      "steps": [
        "Provide guided editors for approved FAQs, applicability, services, packages, pricing inputs and specialist records.",
        "Separate author, reviewer and publisher permissions and preserve change/audit history.",
        "Preview a candidate version against agreed founder cases and expose affected decisions.",
        "Publish only reviewed tested versions and roll back to the previous version with cache invalidation."
      ],
      "reviewer": "Authorised publisher and business / release QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P10.1",
        "P10.2",
        "P10.3"
      ],
      "prerequisites": [
        "P03.1",
        "P01.3",
        "P16",
        "P03.3",
        "P04.1",
        "P06.2",
        "P04.3"
      ],
      "features": [
        "workshop.1",
        "workshop.2",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P10.1",
      "anchor": "p10-1",
      "title": "Define guided business editors and change permissions",
      "group": "P",
      "parent": "P10",
      "result": "Approved editor contracts cover routine business changes without direct code/database edits.",
      "owner": "Product / UX analyst",
      "evidence": "Editor field/action matrix and manager usability notes.",
      "dependencies": [
        "P03.1",
        "P01.3",
        "P16"
      ],
      "steps": [
        "List routine FAQ, source, service, package, price-driver and specialist changes.",
        "Define author/reviewer/publisher actions for each record type.",
        "Specify plain-language fields, help, required evidence and validation.",
        "Show changed values and affected founder decisions.",
        "Review the design with a manager using existing records and fictional examples."
      ],
      "reviewer": "Business operations and access owner",
      "inputs": [
        "P03.1",
        "P01.3",
        "P16 role policy"
      ],
      "blocker": "If a change needs policy authority or unsafe direct access, exclude that action and request a role/workflow decision. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P10. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P03.1",
        "P01.3",
        "P16"
      ],
      "features": [
        "workshop.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P10.2",
      "anchor": "p10-2",
      "title": "Build candidate preview and immutable release records",
      "group": "P",
      "parent": "P10",
      "result": "A manager can inspect a candidate's effect and evidence without changing live Beth; every preview ties to an immutable version.",
      "owner": "Backend / frontend engineer",
      "evidence": "Release manifest, change comparison and failed-gate walkthrough.",
      "dependencies": [
        "P10.1",
        "P03.3",
        "P04.1",
        "P06.2"
      ],
      "steps": [
        "Bundle candidate knowledge, source, pricing and prompt/rule versions.",
        "Display approvals, gaps and change comparison before preview.",
        "Run agreed development examples against the candidate version.",
        "Record preview inputs, outputs and failed gates with the bundle.",
        "Prevent unapproved or incomplete candidates from becoming current."
      ],
      "reviewer": "Authorised publisher and QA",
      "inputs": [
        "P10.1",
        "P03.3",
        "P04.1",
        "P06.2"
      ],
      "blocker": "If an approval or test fails, retain the previous current version and identify the candidate record needing correction. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P10. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P10.1",
        "P03.3",
        "P04.1",
        "P06.2"
      ],
      "features": [
        "workshop.1",
        "workshop.2",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P10.3",
      "anchor": "p10-3",
      "title": "Verify controlled publish, retirement and rollback",
      "group": "P",
      "parent": "P10",
      "result": "The manager can publish and reverse a tested change without developer intervention, with a complete audit trail.",
      "owner": "Backend engineer / release coordinator",
      "evidence": "Publish/rollback exercise record, version audit and cache-retirement checks.",
      "dependencies": [
        "P10.2",
        "P04.3"
      ],
      "steps": [
        "Require the authorised publisher and recorded accepted test result.",
        "Publish one atomic version bundle and append an audit record.",
        "Invalidate affected caches and retire superseded current records.",
        "Restore the previous bundle while preserving applicable history.",
        "Have a trained manager complete a fictional correction/publish/rollback exercise."
      ],
      "reviewer": "Authorised publisher and QA",
      "inputs": [
        "P10.2",
        "P04.3"
      ],
      "blocker": "If a release or rollback cannot be proven consistent, keep or restore the verified previous release and escalate to its operating owner. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P10. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P10.2",
        "P04.3"
      ],
      "features": [
        "workshop.1",
        "workshop.2",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P11",
      "anchor": "p11",
      "title": "Run an expert-reviewed pilot evaluation before expansion",
      "group": "P",
      "parent": null,
      "result": "The approved pilot suite has no critical failures; held-out results and limitations are recorded, and measured outcomes lead to reviewed changes rather than automatic price edits.",
      "owner": "Evaluation analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P01.1",
        "P01.2",
        "P02.3",
        "P11.1",
        "P10.2",
        "P04.2",
        "P05.3",
        "P06.3",
        "P07.3",
        "P15.2",
        "P11.2",
        "P08.3",
        "P15.3",
        "D07.3"
      ],
      "steps": [
        "Approve45 reference scenarios across3journeys and5categories, grouping related variants together.",
        "Reserve15 unseen cases and use30 for development; separate examples from actual job evidence.",
        "Compare baseline and approved enriched Beth using fixed model/tool/source versions and redacted results.",
        "Check citations, unnecessary/missed services, question burden, quote scope, matching and critical failures.",
        "Publish release evidence and monitor real quote-versus-actual effort with reviewed adjustments."
      ],
      "reviewer": "Independent Philippine domain reviewers and evaluation lead",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P11.1",
        "P11.2",
        "P11.3"
      ],
      "prerequisites": [
        "P01.1",
        "P01.2",
        "P02.3",
        "P10.2",
        "P04.2",
        "P05.3",
        "P06.3",
        "P07.3",
        "P15.2",
        "P08.3",
        "P15.3",
        "D07.3"
      ],
      "features": [
        "start.1",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P11.1",
      "anchor": "p11-1",
      "title": "Approve evaluation cases and protected holdout",
      "group": "P",
      "parent": "P11",
      "result": "The reviewed suite and frozen split have expected outcomes and no development/holdout leakage.",
      "owner": "Evaluation analyst",
      "evidence": "Redacted scenario manifest, split/version record and reviewer acceptance.",
      "dependencies": [
        "P01.1",
        "P01.2",
        "P02.3"
      ],
      "steps": [
        "Draft 45 cases across three journeys and five scenario categories.",
        "Label expected facts, clarifications, scope, pricing drivers, citations and escalation.",
        "Group paraphrases/related clients before assigning 30development and15holdout cases.",
        "Restrict holdout answers from prompts and worked examples.",
        "Agree metrics and critical-failure gates before any comparison."
      ],
      "reviewer": "Independent Philippine domain reviewers",
      "inputs": [
        "P01.1",
        "P01.2",
        "P02.3"
      ],
      "blocker": "If reference outcomes are disputed or holdout leaks, stop evaluation and have independent reviewers correct/refreeze the affected cases. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P11. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01.1",
        "P01.2",
        "P02.3"
      ],
      "features": [
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P11.2",
      "anchor": "p11-2",
      "title": "Compare baseline and approved candidates reproducibly",
      "group": "P",
      "parent": "P11",
      "result": "A reproducible paired evaluation has reviewed results and no critical suite failure before release acceptance.",
      "owner": "QA / AI evaluation engineer",
      "evidence": "Run manifest, redacted outputs, blinded scoring and critical-failure log.",
      "dependencies": [
        "P11.1",
        "P10.2",
        "P04.2",
        "P05.3",
        "P06.3",
        "P07.3",
        "P15.2"
      ],
      "steps": [
        "Pin model, prompt, source, tool and candidate versions for the run.",
        "Run baseline, enriched and relevant input-removal comparisons.",
        "Repeat holdout cases as agreed and retain redacted output traces.",
        "Blind reviewers to version and record metric/critical-failure judgments.",
        "Publish measured results and limits without claiming universal accuracy."
      ],
      "reviewer": "Independent domain reviewers",
      "inputs": [
        "P11.1",
        "P10.2",
        "P04.2",
        "P05.3",
        "P06.3",
        "P07.3",
        "P15 tracing"
      ],
      "blocker": "If a critical error occurs, block that candidate and assign the failed rule/source/action for correction and affected-case rerun. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P11. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P11.1",
        "P10.2",
        "P04.2",
        "P05.3",
        "P06.3",
        "P07.3",
        "P15.2"
      ],
      "features": [
        "start.1",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P11.3",
      "anchor": "p11-3",
      "title": "Track real job outcomes and review pilot readiness",
      "group": "P",
      "parent": "P11",
      "result": "Pilot acceptance and improvement proposals rely on reviewed outcomes, not filled surveys or conversion alone.",
      "owner": "Operations / analytics coordinator",
      "evidence": "Anonymised outcome register, calibration review and pilot go/hold decision.",
      "dependencies": [
        "P11.2",
        "P08.3",
        "P15.3",
        "D07.3"
      ],
      "steps": [
        "Record accepted scope/version and actual hours by role using anonymised job IDs.",
        "Separate extra approved scope, waiting time and rework from estimate error.",
        "Compare reviewed reference quotes with actual delivery and quality outcomes.",
        "Propose adjustments through candidate review instead of automatic price edits.",
        "Present evidence, unresolved blockers and a go/hold decision to the pilot owner."
      ],
      "reviewer": "Finance owner, QA and practice lead",
      "inputs": [
        "P11.2",
        "P08.3",
        "P15 operational readiness"
      ],
      "blocker": "If actual job evidence or launch readiness is absent, label results provisional and keep expansion approval on hold. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P11. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P11.2",
        "P08.3",
        "P15.3",
        "D07.3"
      ],
      "features": [
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P12",
      "anchor": "p12",
      "title": "Approve the broader-launch backlog after pilot evidence",
      "group": "P",
      "parent": null,
      "result": "Each expansion has an approved owner, prerequisite, measurable acceptance and decision to proceed; future integrations do not become blockers for today's cloud demo deployment.",
      "owner": "Product owner / business analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "P11.3",
        "P14",
        "P12.1",
        "P12.2"
      ],
      "steps": [
        "Select remaining journeys/services toward10journeys,10packages and36servicecards after pilot review.",
        "Plan WhatsApp andLINE, one calendar provider and one documented Babylon jobs/directory adapter.",
        "Define one durable document/approval/reminder lifecycle and its recovery/duplicate-action tests.",
        "Approve expanded language coverage, specialist capacity, outcome analytics and load tests before committing dates."
      ],
      "reviewer": "Business decision maker, product owner and technical lead",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "P12.1",
        "P12.2",
        "P12.3"
      ],
      "prerequisites": [
        "P11.3",
        "P14"
      ],
      "features": [
        "portal.1",
        "specialists.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P12.1",
      "anchor": "p12-1",
      "title": "Prioritise broader catalogue and language expansion",
      "group": "P",
      "parent": "P12",
      "result": "A prioritised expansion brief has explicit scope, acceptance and approvals; it authorises planning only.",
      "owner": "Product owner / business analyst",
      "evidence": "Expansion decision log and scoped acceptance briefs.",
      "dependencies": [
        "P11.3"
      ],
      "steps": [
        "Review pilot errors, demand and operational workload.",
        "Select remaining journeys/services toward the proposed broader catalogue.",
        "Identify VAT/payroll/inventory/foreign-founder review boundaries.",
        "Define English/Filipino/Taglish acceptance examples and reviewer capacity.",
        "Record proceed/defer choices, prerequisite owners and estimated evidence needs."
      ],
      "reviewer": "Practice lead and launch owner",
      "inputs": [
        "P11.3"
      ],
      "blocker": "Without pilot acceptance or reviewer capacity, retain each expansion as proposed and do not commit a launch date. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P12. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P11.3"
      ],
      "features": [
        "specialists.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P12.2",
      "anchor": "p12-2",
      "title": "Assess channel, calendar and Babylon integration options",
      "group": "P",
      "parent": "P12",
      "result": "Each option has a reviewed feasibility brief and explicit proceed/defer approval before implementation.",
      "owner": "Integration analyst",
      "evidence": "Provider/action inventory, compatibility questions and decision record.",
      "dependencies": [
        "P11.3",
        "P14"
      ],
      "steps": [
        "Select exact proposed WhatsApp/LINE, calendar and Babylon interface requirements.",
        "Confirm provider ownership, API access, consent and identity mappings.",
        "Define request/reschedule/cancel, callback and failure receipts to verify.",
        "Identify provider approvals, compatibility gaps and support responsibility.",
        "Submit a bounded proof/build decision; keep unavailable integrations manual."
      ],
      "reviewer": "Technical lead and operations owner",
      "inputs": [
        "P11.3",
        "P14 approved connector proof"
      ],
      "blocker": "If provider action or permission cannot be proven, record the gap and seek a scope decision rather than promise the integration. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P12. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P11.3",
        "P14"
      ],
      "features": [
        "portal.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P12.3",
      "anchor": "p12-3",
      "title": "Plan durable cases and larger launch acceptance",
      "group": "P",
      "parent": "P12",
      "result": "The broader-launch plan states validated need, bounded workflow, tests and decision owners without installing new infrastructure.",
      "owner": "Technical / operations analyst",
      "evidence": "Workflow brief, recovery scenarios, capacity assumptions and scope approval.",
      "dependencies": [
        "P12.1",
        "P12.2"
      ],
      "steps": [
        "Define one proposed document/approval/reminder lifecycle and system-of-record boundaries.",
        "Specify action receipts, retry limits, reassignment and worker-recovery scenarios.",
        "Identify the measured need for Temporal or another approved recovery choice.",
        "Define broader load, capacity, retention and recovery acceptance tests.",
        "Obtain a separate implementation decision and keep optional engines deferred."
      ],
      "reviewer": "Technical lead, QA and product owner",
      "inputs": [
        "P11.3",
        "P12.1",
        "P12.2"
      ],
      "blocker": "If autonomous recovery is not an approved need, keep supervised follow-up and request a separate architecture/scope decision. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P12. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.1",
        "P12.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P13",
      "anchor": "p13",
      "title": "Deliver reproducible reports, consent and account history",
      "group": "P",
      "parent": null,
      "result": "A founder’s report reproduces the saved scope, quote, assumptions and evidence version; sharing is consented and authorised; chat deletion follows an approved policy without silently deleting an active case.",
      "owner": "Frontend/backend engineer and privacy owner",
      "evidence": "A founder’s report reproduces the saved scope, quote, assumptions and evidence version; sharing is consented and authorised; chat deletion follows an approved policy without silently deleting an active case. — attach child acceptance records and the feature-level test result.",
      "dependencies": [
        "P04",
        "P06",
        "P16"
      ],
      "steps": [
        "Accept P13.1: Approve report contents, sharing consent and retention boundaries",
        "Accept P13.2: Generate and verify reports from saved decision versions",
        "Accept P13.3: Verify authorised recall, consented sharing and deletion"
      ],
      "reviewer": "Product owner and privacy / records reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Production pilot work from the feature sweep dated 8 Oct 2026. This does not require the active cloud demonstration to adopt the proposed production stack. Approve unresolved policies/technology choices before implementation.",
      "required_children": [
        "P13.1",
        "P13.2",
        "P13.3"
      ],
      "prerequisites": [
        "P04",
        "P06",
        "P16"
      ],
      "features": [
        "handoff.2",
        "history.1",
        "history.2",
        "report.1",
        "report.2",
        "start.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P13.1",
      "anchor": "p13-1",
      "title": "Approve report contents, sharing consent and retention boundaries",
      "group": "P",
      "parent": "P13",
      "result": "Approved field/access and retention matrices cover each operation; unknown policy decisions block affected implementation.",
      "owner": "Frontend/backend engineer and privacy owner",
      "evidence": "Approved field matrix, consent wording, data-lifecycle decisions and reviewer record",
      "dependencies": [
        "P01",
        "P16.1"
      ],
      "steps": [
        "Inventory report fields and identify founder-visible versus restricted fields",
        "Specify recipient, purpose, scope and revocation behavior for sharing contact details and summaries",
        "Define chat, case, submission, document and audit retention/deletion behavior separately",
        "Define authorised history search, download, recall and deletion operations",
        "Record unresolved decisions and obtain product/privacy approval"
      ],
      "reviewer": "Product owner and privacy reviewer",
      "inputs": [
        "P01 pilot scope",
        "P16.1 role/data-access decisions"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P13. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01",
        "P16.1"
      ],
      "features": [
        "report.1",
        "handoff.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P13.2",
      "anchor": "p13-2",
      "title": "Generate and verify reports from saved decision versions",
      "group": "P",
      "parent": "P13",
      "result": "Downloaded and on-screen reports exactly reproduce the saved amounts/assumptions and never disclose restricted internal costs.",
      "owner": "Frontend/backend engineer and privacy owner",
      "evidence": "Saved input snapshot, report samples, exact-total comparison and authorisation test results",
      "dependencies": [
        "P13.1",
        "P04",
        "P06"
      ],
      "steps": [
        "Map saved facts, scope lines, quantities, quote/rule version and source references to the report",
        "Generate HTML/print/download formats from the same saved snapshot",
        "Display assumptions, conditional additions, fees, currency and estimate status consistently",
        "Compare report totals and line items to the saved quote without recalculating under current rules",
        "Test long text, missing optional fields, repeat downloads and cross-account access",
        "Attach a reviewed sample report and replay result"
      ],
      "reviewer": "Product owner and privacy reviewer",
      "inputs": [
        "P13.1",
        "approved saved quote and source versions"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P13. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P13.1",
        "P04",
        "P06"
      ],
      "features": [
        "report.1",
        "report.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P13.3",
      "anchor": "p13-3",
      "title": "Verify authorised recall, consented sharing and deletion",
      "group": "P",
      "parent": "P13",
      "result": "An authorised sharing/history/deletion scenario and an unauthorised scenario match the approved policy; retained cases remain traceable.",
      "owner": "Frontend/backend engineer and privacy owner",
      "evidence": "Consent/audit records, before/after history results and denied-access evidence",
      "dependencies": [
        "P13.1",
        "P16.2"
      ],
      "steps": [
        "Search and reopen only the signed-in founder’s allowed history",
        "Require and record approved consent before sharing a summary/contact details",
        "Verify intended recipients and restrict shared file/document access",
        "Delete a test chat and check its search, recall, caches and delayed-save behavior",
        "Confirm active case retention and explain the resulting state to the founder",
        "Record policy exceptions, revocation behavior and reviewer acceptance"
      ],
      "reviewer": "Product owner and privacy reviewer",
      "inputs": [
        "P13.1 policy",
        "saved records and authorised files"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P13. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P13.1",
        "P16.2"
      ],
      "features": [
        "start.3",
        "report.2",
        "handoff.2",
        "history.1",
        "history.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P14",
      "anchor": "p14",
      "title": "Approve and prove conversation, model routing and scoped tool actions",
      "group": "P",
      "parent": null,
      "result": "Approved conversation/model/tool policies preserve confirmed facts, isolate sessions, enforce business rules, cap spend and escalate safely; any proposed production engines pass a scoped proof before adoption.",
      "owner": "AI/backend engineer and platform owner",
      "evidence": "Approved conversation/model/tool policies preserve confirmed facts, isolate sessions, enforce business rules, cap spend and escalate safely; any proposed production engines pass a scoped proof before adoption. — attach child acceptance records and the feature-level test result.",
      "dependencies": [
        "P01",
        "P04",
        "P16.1"
      ],
      "steps": [
        "Accept P14.1: Approve conversation states, task profiles and runtime decisions",
        "Accept P14.2: Prove streaming, context isolation, routing and failure behavior",
        "Accept P14.3: Prove scoped MCP connections and duplicate-safe actions"
      ],
      "reviewer": "AI evaluation and security reviewers",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Production pilot work from the feature sweep dated 8 Oct 2026. This does not require the active cloud demonstration to adopt the proposed production stack. Approve unresolved policies/technology choices before implementation.",
      "required_children": [
        "P14.1",
        "P14.2",
        "P14.3"
      ],
      "prerequisites": [
        "P01",
        "P04",
        "P16.1"
      ],
      "features": [
        "history.1",
        "sources.1",
        "start.1",
        "start.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P14.1",
      "anchor": "p14-1",
      "title": "Approve conversation states, task profiles and runtime decisions",
      "group": "P",
      "parent": "P14",
      "result": "A versioned policy states the allowed model/tool path for every pilot task and distinguishes current deployment from future runtime work.",
      "owner": "AI/backend engineer and platform owner",
      "evidence": "Approved runtime decision, state diagram/table, model policy and tool-permission matrix",
      "dependencies": [
        "P01"
      ],
      "steps": [
        "Document current cloud runtime versus proposed production components and obtain a decision before introducing engines",
        "Define new/resume/reset/interrupt/correction states and shared confirmed-fact ownership",
        "Define economical, balanced and reasoning task profiles with minimum risk/capability requirements",
        "Approve exact provider/model versions, budgets, timeouts, retries and fallback paths",
        "Define permission-checked tools and which actions require explicit founder approval",
        "Record missing provider/privacy/edition decisions as blockers"
      ],
      "reviewer": "AI evaluation and security reviewers",
      "inputs": [
        "Pilot scope and current cloud architecture evidence"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P14. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01"
      ],
      "features": [
        "start.1",
        "start.3",
        "sources.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P14.2",
      "anchor": "p14-2",
      "title": "Prove streaming, context isolation, routing and failure behavior",
      "group": "P",
      "parent": "P14",
      "result": "The scenario preserves latest facts and single action receipts; failure/budget cases take the approved fallback or human path.",
      "owner": "AI/backend engineer and platform owner",
      "evidence": "State/streaming fixtures, expected/actual logs, redacted traces and policy-version review",
      "dependencies": [
        "P14.1",
        "P04.1",
        "D04.1"
      ],
      "steps": [
        "Implement or adapt the approved runtime without duplicating gateway responsibilities",
        "Test streaming, reconnect/cancel and new-chat isolation without duplicate messages/actions",
        "Interrupt an estimate with a cited question, correct a fact and resume with the latest confirmed state",
        "Switch task profiles and verify confirmed facts persist while unrelated personal data is excluded",
        "Test spend/time/retry caps, provider outage and unapproved cheap-model fallback refusal",
        "Capture redacted versioned traces and obtain evaluation/security review"
      ],
      "reviewer": "AI evaluation and security reviewers",
      "inputs": [
        "P14.1 policy",
        "approved knowledge and cloud AI connection"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P14. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P14.1",
        "P04.1",
        "D04.1"
      ],
      "features": [
        "start.1",
        "start.3",
        "sources.1",
        "history.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P14.3",
      "anchor": "p14-3",
      "title": "Prove scoped MCP connections and duplicate-safe actions",
      "group": "P",
      "parent": "P14",
      "result": "The bounded approved actions work with least necessary scope, isolation and replay safety; failed compatibility yields an explicit replacement/manual decision.",
      "owner": "AI/backend engineer and platform owner",
      "evidence": "Scoped compatibility matrix, real-provider receipts, denied-action/retry tests and adoption decision",
      "dependencies": [
        "P14.1",
        "P16.1"
      ],
      "steps": [
        "Approve chosen providers/actions and record read/write scopes before enabling them",
        "Prove the chosen client/gateway transport against pinned versions; keep one credential owner",
        "Validate per-founder connection isolation, allowlists and encrypted credential storage",
        "Test OAuth expiry/refresh, revocation, unauthorised actions and timeouts",
        "Require consent for write actions and persist receipts so retries cannot repeat the action",
        "Record real-provider success separately from catalogue claims and keep manual fulfilment for failed proof"
      ],
      "reviewer": "AI evaluation and security reviewers",
      "inputs": [
        "Approved implementation path and two bounded existing-provider proof selections"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P14. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P14.1",
        "P16.1"
      ],
      "features": [
        "sources.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P15",
      "anchor": "p15",
      "title": "Prove pilot alerts, observability and operating capacity",
      "group": "P",
      "parent": null,
      "result": "Real alerts have visible delivery results, operators can detect and diagnose service failures without leaking private data, and the approved pilot traffic envelope has measured capacity and failure evidence.",
      "owner": "Integration/platform engineer and operations lead",
      "evidence": "Real alerts have visible delivery results, operators can detect and diagnose service failures without leaking private data, and the approved pilot traffic envelope has measured capacity and failure evidence. — attach child acceptance records and the feature-level test result.",
      "dependencies": [
        "P08",
        "P09",
        "P14",
        "P16"
      ],
      "steps": [
        "Accept P15.1: Implement consented email alerts with visible delivery receipts",
        "Accept P15.2: Set up redacted traces, service health and incident ownership",
        "Accept P15.3: Measure pilot capacity and approve operating limits"
      ],
      "reviewer": "Service operations, platform and performance QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Production pilot work from the feature sweep dated 8 Oct 2026. This does not require the active cloud demonstration to adopt the proposed production stack. Approve unresolved policies/technology choices before implementation.",
      "required_children": [
        "P15.1",
        "P15.2",
        "P15.3"
      ],
      "prerequisites": [
        "P08",
        "P09",
        "P14",
        "P16"
      ],
      "features": [
        "booking.2",
        "portal.3",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P15.1",
      "anchor": "p15-1",
      "title": "Implement consented email alerts with visible delivery receipts",
      "group": "P",
      "parent": "P15",
      "result": "One approved real email flow succeeds; duplicate retries do not create another case/alert and failures remain actionable to staff.",
      "owner": "Integration/platform engineer and operations lead",
      "evidence": "Event/template matrix, redacted provider receipt and duplicate/failure test log",
      "dependencies": [
        "P08.1",
        "P17.2",
        "P09.2"
      ],
      "steps": [
        "Map case, appointment and staff-action events to allowed recipients and consent requirements",
        "Approve email connector, sender identity and template content",
        "Persist event/delivery IDs before send and bound retries",
        "Test duplicate events, provider failure, rejection and unavailable recipients",
        "Show staff delivery state while retaining the underlying case/ticket",
        "Attach one real delivery proof and label all simulated paths"
      ],
      "reviewer": "QA and service operations",
      "inputs": [
        "Approved case/appointment events and notification recipients"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P15. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P08.1",
        "P17.2",
        "P09.2"
      ],
      "features": [
        "booking.2",
        "portal.3",
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P15.2",
      "anchor": "p15-2",
      "title": "Set up redacted traces, service health and incident ownership",
      "group": "P",
      "parent": "P15",
      "result": "An operator can detect, locate and triage a deliberate failure using the guide and approved traces without accessing unnecessary private data.",
      "owner": "Integration/platform engineer and operations lead",
      "evidence": "Redaction checks, correlated trace sample, tested alert and incident runbook",
      "dependencies": [
        "P14.1",
        "D01.1"
      ],
      "steps": [
        "Define correlation IDs across answer, quote, source fetch, case and external action",
        "Record model/prompt/rule/source versions, latency, spend and handoff outcome with redaction",
        "Verify secrets, private documents and unnecessary personal data are excluded",
        "Define health/error signals and thresholds for source/provider/storage/channel failures",
        "Assign incident contacts and escalation/fallback steps; send one test operational alert",
        "Trace a test failure from the user’s visible message to the relevant redacted evidence"
      ],
      "reviewer": "QA and service operations",
      "inputs": [
        "Approved runtime and test deployment"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P15. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P14.1",
        "D01.1"
      ],
      "features": [
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P15.3",
      "anchor": "p15-3",
      "title": "Measure pilot capacity and approve operating limits",
      "group": "P",
      "parent": "P15",
      "result": "Measured results support an approved capacity envelope or explicitly limit launch; no untested sizing assumption is reported as capacity.",
      "owner": "Integration/platform engineer and operations lead",
      "evidence": "Approved workload/threshold plan, result graphs/logs and launch-limit decision",
      "dependencies": [
        "P14.2",
        "P15.2",
        "P16"
      ],
      "steps": [
        "Confirm the pilot sizing assumption and agree response/failure/spending thresholds before testing",
        "Prepare representative chat, source, save and handoff workloads using fictional data",
        "Measure 20 simultaneous sessions and the expected pilot traffic mix rather than only empty-page requests",
        "Exercise rate limits, slow provider/source responses and recovery within bounded retry budgets",
        "Record throughput, latency, error rates, successful-answer cost and capacity bottlenecks",
        "Review results, set practical operating limits and create defects for unmet thresholds"
      ],
      "reviewer": "QA and service operations",
      "inputs": [
        "Stable pilot functions, monitoring and approved test traffic"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P15. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P14.2",
        "P15.2",
        "P16"
      ],
      "features": [
        "workshop.3"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P16",
      "anchor": "p16",
      "title": "Approve business roles and secure document collection",
      "group": "P",
      "parent": null,
      "result": "Founder, specialist, manager and expert roles have explicit business membership and access rules; private files can be collected and retrieved only by authorised parties under approved retention rules.",
      "owner": "Backend/platform engineer and privacy operations owner",
      "evidence": "Founder, specialist, manager and expert roles have explicit business membership and access rules; private files can be collected and retrieved only by authorised parties under approved retention rules. — attach child acceptance records and the feature-level test result.",
      "dependencies": [
        "P01",
        "D02",
        "D03"
      ],
      "steps": [
        "Accept P16.1: Approve business membership, role permissions and account recovery",
        "Accept P16.2: Implement private document upload, preparation and access checks",
        "Accept P16.3: Verify retention, revocation and private-data handling"
      ],
      "reviewer": "Security / privacy reviewer and business membership owner",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Production pilot work from the feature sweep dated 8 Oct 2026. This does not require the active cloud demonstration to adopt the proposed production stack. Approve unresolved policies/technology choices before implementation.",
      "required_children": [
        "P16.1",
        "P16.2",
        "P16.3"
      ],
      "prerequisites": [
        "P01",
        "D02",
        "D03"
      ],
      "features": [
        "access.1",
        "access.2",
        "handoff.1",
        "history.1",
        "history.2",
        "portal.1",
        "portal.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P16.1",
      "anchor": "p16-1",
      "title": "Approve business membership, role permissions and account recovery",
      "group": "P",
      "parent": "P16",
      "result": "Every pilot operation has an approved role/membership rule and recovery/revocation path; edition gaps have a decision rather than an assumed permission.",
      "owner": "Backend/platform engineer and privacy operations owner",
      "evidence": "Approved access matrix, membership fixtures and recovery/edition decisions",
      "dependencies": [
        "P01",
        "D02"
      ],
      "steps": [
        "Define person/account/business identifiers and allowed memberships for the pilot organisation",
        "Specify founder, assigned specialist, manager and expert reviewer actions with deny-by-default access",
        "Choose invite/onboarding, access revocation and password/account recovery behavior",
        "Define who administers access and where privileged credentials are held",
        "Write same-business, other-business, revoked-role and unauthenticated test expectations",
        "Approve the access matrix and identify any selected software-edition limitations"
      ],
      "reviewer": "Security/QA and business owner",
      "inputs": [
        "Pilot organisation and role decisions",
        "cloud identity baseline"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P16. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P01",
        "D02"
      ],
      "features": [
        "access.1",
        "access.2",
        "handoff.1",
        "portal.1",
        "portal.2",
        "history.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P16.2",
      "anchor": "p16-2",
      "title": "Implement private document upload, preparation and access checks",
      "group": "P",
      "parent": "P16",
      "result": "Founders receive source-approved preparation requirements and authorised upload/retrieval; direct-link and cross-business attempts cannot bypass permissions.",
      "owner": "Backend/platform engineer and privacy operations owner",
      "evidence": "Document requirement mapping, upload fixtures, access-denial logs and private-storage proof",
      "dependencies": [
        "P16.1",
        "P01"
      ],
      "steps": [
        "Map each service’s approved required documents and preparation instructions without inventing requirements",
        "Define allowed file types/sizes and storage location; reject unsupported/malformed uploads",
        "Authorise upload, listing, download/export and deletion against business/case membership",
        "Prevent public/static links from exposing confidential files and test direct URL access",
        "Test retries/interrupted uploads and retain a clear pending/missing-document state",
        "Verify two businesses and an assigned/unassigned specialist against file permissions"
      ],
      "reviewer": "Security/QA and business owner",
      "inputs": [
        "P16.1 access matrix",
        "approved service-document requirements"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P16. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P16.1",
        "P01"
      ],
      "features": [
        "handoff.1",
        "portal.1",
        "portal.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P16.3",
      "anchor": "p16-3",
      "title": "Verify retention, revocation and private-data handling",
      "group": "P",
      "parent": "P16",
      "result": "Revocation and data-lifecycle tests match approved policy, including retained-case exceptions and provider boundaries.",
      "owner": "Backend/platform engineer and privacy operations owner",
      "evidence": "Revocation/lifecycle test matrix, redacted trace checks and privacy owner acceptance",
      "dependencies": [
        "P16.1",
        "P16.2",
        "P13.1"
      ],
      "steps": [
        "Apply the approved separate retention rules to chats, cases, submissions, files and traces",
        "Revoke a user or assignment and test existing sessions/links and new requests",
        "Verify document/identity data stays out of public source searches and unnecessary model context",
        "Exercise approved deletion/export request paths and record retained active-case exceptions",
        "Review provider/data-handling and backup access decisions with the responsible owner",
        "Publish the reviewed handling/revocation checklist for operators"
      ],
      "reviewer": "Security/QA and business owner",
      "inputs": [
        "Approved lifecycle policy and implemented roles/files"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P16. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P16.1",
        "P16.2",
        "P13.1"
      ],
      "features": [
        "handoff.1",
        "portal.1",
        "portal.2",
        "history.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P17",
      "anchor": "p17",
      "title": "Complete the consultation and calendar lifecycle",
      "group": "P",
      "parent": null,
      "result": "A founder can request, receive staff confirmation, reschedule and cancel a consultation in the Philippine time zone; duplicates and conflicting confirmed specialist slots are prevented; calendar downloads never imply an unaccepted meeting.",
      "owner": "Booking integration engineer and booking operations",
      "evidence": "A founder can request, receive staff confirmation, reschedule and cancel a consultation in the Philippine time zone; duplicates and conflicting confirmed specialist slots are prevented; calendar downloads never imply an unaccepted meeting. — attach child acceptance records and the feature-level test result.",
      "dependencies": [
        "P07",
        "P16.1",
        "P08.1"
      ],
      "steps": [
        "Accept P17.1: Approve consultation states and validate request inputs",
        "Accept P17.2: Verify staff confirmation, conflicts, rescheduling and cancellation",
        "Accept P17.3: Verify calendar files and confirmed-appointment reminders"
      ],
      "reviewer": "Booking operations manager and QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Production pilot work from the feature sweep dated 8 Oct 2026. This does not require the active cloud demonstration to adopt the proposed production stack. Approve unresolved policies/technology choices before implementation.",
      "required_children": [
        "P17.1",
        "P17.2",
        "P17.3"
      ],
      "prerequisites": [
        "P07",
        "P16.1",
        "P08.1"
      ],
      "features": [
        "booking.1",
        "booking.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P17.1",
      "anchor": "p17-1",
      "title": "Approve consultation states and validate request inputs",
      "group": "P",
      "parent": "P17",
      "result": "An approved state/validation matrix and fixtures distinguish a saved request from specialist acceptance.",
      "owner": "Booking integration engineer and booking operations",
      "evidence": "Approved state matrix; valid and boundary fixture results with exact expected/actual states",
      "dependencies": [
        "P07.2",
        "P16.1"
      ],
      "steps": [
        "Define request, awaiting confirmation, confirmed, rescheduled, cancelled and declined state transitions with authorised actors",
        "Specify Philippine time zone, future-time bounds, allowed 30/60-minute durations and formats from current requirements",
        "Specify missing/invalid specialist, time, duration and format validation responses",
        "Verify a valid request saves the founder, selected specialist, time, format and request key",
        "Test invalid boundary cases and show field-specific correction guidance"
      ],
      "reviewer": "QA and operations manager",
      "inputs": [
        "Specialist roster and appointment-state requirements"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P17. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P07.2",
        "P16.1"
      ],
      "features": [
        "booking.1",
        "booking.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P17.2",
      "anchor": "p17-2",
      "title": "Verify staff confirmation, conflicts, rescheduling and cancellation",
      "group": "P",
      "parent": "P17",
      "result": "Each allowed transition has one durable result; conflicting bookings and unauthorised or repeated actions cannot change the wrong record.",
      "owner": "Booking integration engineer and booking operations",
      "evidence": "Transition matrix execution log, duplicate/conflict proof and role-access test results",
      "dependencies": [
        "P17.1",
        "P07.3"
      ],
      "steps": [
        "Retry a request with the same key and verify one request/receipt",
        "Attempt a different account’s request and reject read/write/calendar access",
        "Confirm one specialist slot and attempt a conflicting confirmation",
        "Reschedule through the allowed state transition and release the old slot",
        "Cancel through the authorised transition and verify it persists after refresh",
        "Record rejected/unsupported transitions and client/staff notifications as real or simulated"
      ],
      "reviewer": "QA and operations manager",
      "inputs": [
        "P17.1 approved states",
        "authorised staff access"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P17. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P17.1",
        "P07.3"
      ],
      "features": [
        "booking.1",
        "booking.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "P17.3",
      "anchor": "p17-3",
      "title": "Verify calendar files and confirmed-appointment reminders",
      "group": "P",
      "parent": "P17",
      "result": "Calendar files reproduce the saved appointment state, reminders have real delivery evidence, and no download implies an unaccepted booking.",
      "owner": "Booking integration engineer and booking operations",
      "evidence": "Sanitised calendar examples, saved-state comparison, reminder receipts and reviewed journey log",
      "dependencies": [
        "P17.2",
        "P15.1"
      ],
      "steps": [
        "Export authorised calendar data and compare specialist, time zone, start/end, format and duration to the saved request",
        "Label an unaccepted request/calendar invitation tentative and a confirmed meeting accurately",
        "Check download MIME, escaping, cancellation/reschedule behavior and ownership",
        "Send the approved reminder only for the intended state, recipient and consent",
        "Retry delivery and verify saved receipts prevent duplicate alerts",
        "Run founder and staff consultation journeys and obtain review acceptance"
      ],
      "reviewer": "QA and operations manager",
      "inputs": [
        "P17.2 states",
        "P15.1 real alert path when required for the pilot"
      ],
      "blocker": "If an input, approval, provider or expected result is missing, record the exact gap and decision/action owner; keep the relevant step open. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within P17. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P17.2",
        "P15.1"
      ],
      "features": [
        "booking.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D01",
      "anchor": "d01",
      "title": "Verify and accept the deployed Beth cloud release",
      "group": "D",
      "parent": null,
      "result": "All agreed paths work at beth2.top, persist records in cloud storage and do not rely on the Mac being online.",
      "owner": "Deployment engineer in the original chat",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D01.1",
        "D01.2",
        "D02.1",
        "D02.2",
        "D02.3",
        "D03.1",
        "D03.2",
        "D03.3",
        "D04.2",
        "D04.3",
        "D06.1",
        "D06.2",
        "D06.3",
        "D07.1"
      ],
      "steps": [
        "Complete cloud build and database migrations",
        "Publish a verified cloud release",
        "Connect beth2.top through Cloudflare",
        "Verify HTTPS and /chat, /interview, /docs and /cases",
        "Record the release URL and rollback steps"
      ],
      "reviewer": "Technical release reviewer and product QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D01.1",
        "D01.2",
        "D01.3"
      ],
      "prerequisites": [
        "D02.1",
        "D02.2",
        "D02.3",
        "D03.1",
        "D03.2",
        "D03.3",
        "D04.2",
        "D04.3",
        "D06.1",
        "D06.2",
        "D06.3",
        "D07.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D01.1",
      "anchor": "d01-1",
      "title": "Verify the cloud build, migrations and hosted preview evidence",
      "group": "D",
      "parent": "D01",
      "result": "A hosted preview serves all four entrances and its API reaches the cloud database.",
      "owner": "Deployment engineer in the original chat",
      "evidence": "Build/migration result and release revision.; Preview URL with route checks and redacted storage-status response.",
      "dependencies": [],
      "steps": [
        "Confirm the current deployment revision and four required paths.",
        "Verify the reported page-loader routing repair against the published revision.",
        "Build through the existing hosting workflow without starting a second deployment.",
        "Apply pending cloud schema migrations once in the preview environment.",
        "Open the hosted preview and record its revision, URL and storage status."
      ],
      "reviewer": "Technical reviewer",
      "inputs": [
        "Active cloud source and the existing registered private project."
      ],
      "blocker": "If build, routing or database setup fails, record the failing step and owner; do not connect the live domain. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D01.2",
      "anchor": "d01-2",
      "title": "Verify uploaded guide assets, captions and access",
      "group": "D",
      "parent": "D01",
      "result": "All promised guide assets work in preview and their access matches the approved inventory.",
      "owner": "Deployment engineer and documentation editor",
      "evidence": "Asset inventory and upload receipts without publishing credentials.; Link/media checks including seeking and gated-download results.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "List required guide pages, videos, captions and downloads with public/private classification.",
        "Confirm the reported hosted uploads match approved guide versions; upload only an identified missing or changed approved asset.",
        "Verify links, content types, video seeking and downloads in preview.",
        "Check protected guides remain gated and public guides remain reachable.",
        "Record missing or intentionally deferred files in the release notes."
      ],
      "reviewer": "Product reviewer",
      "inputs": [
        "Working cloud preview, approved public/private asset inventory and guide files."
      ],
      "blocker": "Missing required assets or incorrect exposure blocks this package; optional omissions need a visible limitation and reviewer agreement. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D01.3",
      "anchor": "d01-3",
      "title": "Verify beth2.top routing and record release acceptance",
      "group": "D",
      "parent": "D01",
      "result": "The agreed cloud demo is live on beth2.top and its required journeys work without the Mac.",
      "owner": "Deployment engineer in the original chat",
      "evidence": "Preview acceptance sign-off and release revision.; Live hostname checks and redacted domain configuration change.; Rollback instructions tied to the published revision.",
      "dependencies": [
        "D01.1",
        "D01.2",
        "D02.1",
        "D02.2",
        "D02.3",
        "D03.1",
        "D03.2",
        "D03.3",
        "D04.2",
        "D04.3",
        "D06.1",
        "D06.2",
        "D06.3",
        "D07.1"
      ],
      "steps": [
        "Confirm the exact accepted revision and unresolved limitations.",
        "Save current domain/route configuration and identify the last working release.",
        "Inspect the reported live revision/domain configuration and verify it matches the accepted release; change it only to resolve a verified mismatch.",
        "Check HTTPS, canonical paths, legacy redirects and authenticated saves on the live hostname.",
        "Record the live URL, revision and the rollback result or verified procedure."
      ],
      "reviewer": "Release reviewer",
      "inputs": [
        "Preview acceptance evidence, release brief, configured domain and working rollback plan."
      ],
      "blocker": "Do not connect live traffic if required preview checks fail; recover the prior route/release if live checks fail. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1",
        "D01.2",
        "D02.1",
        "D02.2",
        "D02.3",
        "D03.1",
        "D03.2",
        "D03.3",
        "D04.2",
        "D04.3",
        "D06.1",
        "D06.2",
        "D06.3",
        "D07.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D02",
      "anchor": "d02",
      "title": "Verify cloud account and commercial-data access",
      "group": "D",
      "parent": null,
      "result": "Cross-account access is rejected; commercial costing requires separate access; credentials never appear in user responses or browser assets.",
      "owner": "QA engineer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "Register and sign in with two separate test accounts",
        "Confirm each account can access only its own interviews, chats, cases and requests",
        "Verify logout, expiry and invalid login handling",
        "Confirm costing stays locked without decision-maker access",
        "Check origin enforcement and secret handling"
      ],
      "reviewer": "Security and access-control reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D02.1",
        "D02.2",
        "D02.3"
      ],
      "prerequisites": [
        "D01.1"
      ],
      "features": [
        "access.1",
        "access.2",
        "report.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D02.1",
      "anchor": "d02-1",
      "title": "Prove accounts cannot access one another’s records",
      "group": "D",
      "parent": "D02",
      "result": "Every tested private read, mutation and record download is tied to the current account; logout revokes access.",
      "owner": "QA engineer",
      "evidence": "Account-isolation test matrix with statuses and no personal credentials.; Redacted denial and logout results.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "Create account A and account B with distinct interviews, cases and requests.",
        "Attempt A’s record IDs while signed in as B for reads and writes.",
        "Check signed-out access to private API routes and record downloads.",
        "Log out and verify the former session no longer authorizes requests.",
        "Record expected denials and delete disposable test data where supported."
      ],
      "reviewer": "Security-minded technical reviewer",
      "inputs": [
        "Cloud preview and two disposable accounts containing different records."
      ],
      "blocker": "Any cross-account exposure or unauthorized mutation blocks release until corrected and rechecked. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1"
      ],
      "features": [
        "access.1",
        "access.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D02.2",
      "anchor": "d02-2",
      "title": "Check private files, exports and media publishing permissions",
      "group": "D",
      "parent": "D02",
      "result": "Private commercial assets and account exports remain protected across direct URLs; only the publishing credential authorizes guide uploads.",
      "owner": "QA engineer",
      "evidence": "Public/private asset map with no commercial amounts.; Direct-route, export/calendar and upload-denial test results.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "Inventory decision pages, guide media, posters, captions and alternative/static file paths.",
        "Attempt direct asset and legacy URLs without decision access; verify every private format is denied.",
        "Attempt another account’s interview export and consultation calendar download.",
        "Call publishing endpoints without a token and with an invalid token; check neither can alter assets.",
        "Confirm approved public files work and document any intentional public information."
      ],
      "reviewer": "Access-control reviewer",
      "inputs": [
        "Preview, asset classification, decision access, publishing endpoint and two test accounts."
      ],
      "blocker": "Unintended private exposure or unauthorized publishing blocks release; do not attach leaked content to the shared task. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1"
      ],
      "features": [
        "report.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D02.3",
      "anchor": "d02-3",
      "title": "Verify login abuse handling and secret-safe sessions",
      "group": "D",
      "parent": "D02",
      "result": "Authentication and credential errors fail safely; configured limits work; secrets remain server-side and rotation steps are documented.",
      "owner": "Backend engineer or QA engineer",
      "evidence": "Abuse/error test results with expected statuses.; Cookie/header checks and redacted secret-exposure review.; Rotation procedure containing credential names, never values.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "Test invalid login, duplicate registration, malformed form and oversized request responses.",
        "Check repeated failed login and decision-unlock attempts trigger the configured limits.",
        "Confirm HTTPS session cookies use HttpOnly, Secure and expected expiry; reject cross-origin mutations.",
        "Inspect public assets, API responses and error logs for accidental credential or token exposure.",
        "Verify a safe credential-rotation procedure is available for AI encryption and publishing access."
      ],
      "reviewer": "Security-minded technical reviewer",
      "inputs": [
        "Preview with test credentials and authorized redacted configuration inspection."
      ],
      "blocker": "Credential exposure, broken expiry, ineffective hosted login limits or accepted foreign-origin writes blocks release. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1"
      ],
      "features": [
        "access.1"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D03",
      "anchor": "d03",
      "title": "Verify cloud saves, conflicts and submission snapshots",
      "group": "D",
      "parent": null,
      "result": "Hosted storage passes persistence, idempotency, conflict and immutable-snapshot checks with recorded results.",
      "owner": "QA engineer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D01.1",
        "D03.1",
        "D02.2"
      ],
      "steps": [
        "Save and reopen an interview from a fresh session",
        "Submit twice with the same request key and check for one receipt",
        "Confirm stale concurrent edits produce a clear conflict",
        "Confirm deleted chats cannot reappear through delayed saves",
        "Confirm submission snapshots remain unchanged after later edits"
      ],
      "reviewer": "Data reliability and product QA reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D03.1",
        "D03.2",
        "D03.3"
      ],
      "prerequisites": [
        "D01.1",
        "D02.2"
      ],
      "features": [
        "history.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D03.1",
      "anchor": "d03-1",
      "title": "Prove account data persists in cloud storage",
      "group": "D",
      "parent": "D03",
      "result": "Records persist correctly across cloud sessions and devices, with no dependence on the Mac database.",
      "owner": "QA engineer",
      "evidence": "Create/reopen result matrix and redacted record IDs.; Cloud storage status and fresh-account behavior notes.",
      "dependencies": [
        "D01.1"
      ],
      "steps": [
        "Create an interview draft, saved chat and consultation request.",
        "Sign out and reopen them in a new authenticated session.",
        "Repeat from a second browser/device without relying on local draft storage.",
        "Check record counts and values using account-scoped responses.",
        "Record that existing local accounts remain separate and are not silently imported."
      ],
      "reviewer": "Backend reviewer",
      "inputs": [
        "Preview with applied schema and a disposable account."
      ],
      "blocker": "Data loss, duplicate records or accidental local-data transfer blocks release and requires an explicit correction. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D03.2",
      "anchor": "d03-2",
      "title": "Test concurrent edits and interrupted-save recovery",
      "group": "D",
      "parent": "D03",
      "result": "Stale changes never overwrite newer data; retries do not duplicate work; deleted chats stay deleted and drafts can be recovered.",
      "owner": "QA engineer",
      "evidence": "Conflict/retry/delete replay results with revisions.; Screenshots or recordings of draft-preservation messages.",
      "dependencies": [
        "D03.1"
      ],
      "steps": [
        "Open the same study in two tabs and save a newer change in one.",
        "Submit the stale tab and verify a visible conflict without overwriting newer data.",
        "Interrupt a save and retry with the same request key.",
        "Delete a test chat and replay a delayed save for its old client key.",
        "Confirm unsaved text remains recoverable and record the recovery path."
      ],
      "reviewer": "Backend reviewer",
      "inputs": [
        "Persisted test interview/chat and two tabs signed into the same account."
      ],
      "blocker": "Silent overwrite, duplicate mutation or resurrected deletion blocks release; preserve a sanitized reproduction. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D03.1"
      ],
      "features": [
        "history.2"
      ],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D03.3",
      "anchor": "d03-3",
      "title": "Verify submission receipts and export accuracy",
      "group": "D",
      "parent": "D03",
      "result": "Receipts are idempotent, submitted snapshots remain immutable and exports accurately represent only the authorized account’s data.",
      "owner": "QA engineer",
      "evidence": "Submission retry and snapshot comparison results.; Redacted sample export with field-completeness checks.",
      "dependencies": [
        "D03.1",
        "D02.2"
      ],
      "steps": [
        "Submit a test interview and save its receipt and revision.",
        "Retry the identical submission key and verify one receipt/snapshot.",
        "Edit the draft and verify the earlier submitted snapshot is unchanged.",
        "Export the review pack and compare owner, answers, revisions and submitted history.",
        "Confirm exports identify inputs as candidates requiring review rather than approved training/publication.",
        "Test missing consent, incomplete context and illustrative model-answer submissions; confirm rejection rather than real-evidence recording."
      ],
      "reviewer": "Research operations reviewer",
      "inputs": [
        "Account-owned interview with a draft and an existing submitted snapshot."
      ],
      "blocker": "Mutable submissions, duplicate receipts, missing answers or incorrect ownership blocks release. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D03.1",
        "D02.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D04",
      "anchor": "d04",
      "title": "Connect and verify cloud AI",
      "group": "D",
      "parent": null,
      "result": "Beth returns a valid cited cloud reply without the Mac, keeps AI credentials private and explains provider failures clearly.",
      "owner": "AI integration engineer with account owner",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D01.1",
        "D02.3",
        "D04.1"
      ],
      "steps": [
        "Choose and document the approved cloud AI connection and model",
        "Configure credentials and encryption through protected settings",
        "Run a business question requiring authoritative web sources",
        "Check source links, scope confirmation and estimate behavior",
        "Verify missing credentials, provider rejection and usage-limit messages"
      ],
      "reviewer": "AI integration and domain citation reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D04.1",
        "D04.2",
        "D04.3"
      ],
      "prerequisites": [
        "D01.1",
        "D02.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D04.1",
      "anchor": "d04-1",
      "title": "Choose and configure the cloud AI connection",
      "group": "D",
      "parent": "D04",
      "result": "The selected connection mode is verified and accurately presented; any guided-only demo limitation is approved and visible.",
      "owner": "AI integration engineer with account owner",
      "evidence": "Connection-mode decision and responsible role.; Redacted status/connect/disconnect results.",
      "dependencies": [
        "D01.1",
        "D02.3"
      ],
      "steps": [
        "Confirm whether the demo uses shared cloud AI, per-account AI or guided preview only.",
        "Record the approved model and who manages usage without storing credentials here.",
        "Configure the permitted credential and encryption secret through protected settings.",
        "Verify Connect AI, status and disconnect behavior for a test account.",
        "Record any unavailable live-AI capability as a visible release limitation."
      ],
      "reviewer": "Product owner",
      "inputs": [
        "Approved AI account/model and preview secret handling",
        "no secret values in task cards."
      ],
      "blocker": "If live AI is required but credentials or model access are unavailable, mark blocked and request the specific prerequisite; never imply AI is connected. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1",
        "D02.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D04.2",
      "anchor": "d04-2",
      "title": "Verify cited replies and confirmation before estimates",
      "group": "D",
      "parent": "D04",
      "result": "Accepted demo behavior is evidenced: live replies have usable authoritative sources when connected, and estimates follow scope confirmation; unavailable live AI is clearly limited.",
      "owner": "AI QA analyst",
      "evidence": "Redacted question/reply/citation examples and source-check notes.; Confirmation-before-estimate transcript and connection-mode label.",
      "dependencies": [
        "D04.1"
      ],
      "steps": [
        "Run one Philippine business compliance question that requires web grounding when live AI is enabled.",
        "Check returned citations point to allowed authoritative domains and support the reply.",
        "Run a profiling example and inspect captured facts and risk flags.",
        "Verify Beth asks for scope confirmation before showing an estimate.",
        "Record pass/fail examples; for guided-only mode label live grounding unavailable rather than passed."
      ],
      "reviewer": "Domain/content reviewer",
      "inputs": [
        "Verified AI mode, curated test questions and expected authoritative sources."
      ],
      "blocker": "Unsupported citations or premature estimates blocks live-AI acceptance; guided-only release requires a clearly approved limitation. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D04.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D04.3",
      "anchor": "d04-3",
      "title": "Check AI failures, limits and honest fallback messages",
      "group": "D",
      "parent": "D04",
      "result": "AI failures show useful recovery instructions, retain user work and accurately identify the active connection or fallback.",
      "owner": "AI integration engineer or QA engineer",
      "evidence": "Missing/rejected/timeout/model/limit response matrix.; Draft-preservation and shared-fallback status results.; Usage responsibility note without billing amounts.",
      "dependencies": [
        "D04.1"
      ],
      "steps": [
        "Test missing credential and rejected credential messages without exposing keys.",
        "Exercise unavailable model, timeout and provider-limit responses using safe test methods.",
        "Confirm drafts and conversation context remain recoverable after failure.",
        "Check whether disconnect reverts to shared AI and make its displayed status accurate.",
        "Record configured usage limits and who responds when they are reached."
      ],
      "reviewer": "Technical reviewer",
      "inputs": [
        "Preview AI configuration and safe simulations of provider failures."
      ],
      "blocker": "Secret-bearing errors, lost user work or misleading connection status blocks live-AI release. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D04.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D05",
      "anchor": "d05",
      "title": "Prove cloud data backup and recovery",
      "group": "D",
      "parent": null,
      "result": "A documented recovery drill restores representative records with their ownership and history intact.",
      "owner": "Operations lead with database engineer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D03.1",
        "D05.1",
        "D03.3",
        "D05.2",
        "D02.1"
      ],
      "steps": [
        "Define what must be recoverable and the acceptable recovery window",
        "Create an export or backup procedure for interviews and case records",
        "Restore test records into a separate environment",
        "Check record counts, ownership and submission snapshots",
        "Record restore steps and responsibility"
      ],
      "reviewer": "Operations owner and independent recovery reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D05.1",
        "D05.2",
        "D05.3"
      ],
      "prerequisites": [
        "D03.1",
        "D03.3",
        "D02.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D05.1",
      "anchor": "d05-1",
      "title": "Define recoverable records and name the backup owner",
      "group": "D",
      "parent": "D05",
      "result": "A reviewed recovery plan states records, recovery targets, authorized owner and protected backup location.",
      "owner": "Operations lead with database engineer",
      "evidence": "Recovery scope/owner/target checklist.; Access and retention decision, without credentials or personal records.",
      "dependencies": [
        "D03.1"
      ],
      "steps": [
        "List interview drafts, submissions, saved cases, accounts and requests that need recovery.",
        "Choose recoverable scope and maximum acceptable loss/downtime for the pilot.",
        "Name the person or role authorized to back up and restore these records.",
        "Separate credential recovery from ordinary review-pack exports.",
        "Record how long test backups are retained and where access is restricted."
      ],
      "reviewer": "Project owner",
      "inputs": [
        "Verified cloud data types and an identified operations contact."
      ],
      "blocker": "If no authorized owner or protected location is agreed, keep pilot recovery blocked; do not call cloud hosting a backup. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D03.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D05.2",
      "anchor": "d05-2",
      "title": "Create and verify a protected test backup",
      "group": "D",
      "parent": "D05",
      "result": "A protected test backup contains the required records and a validated completeness manifest.",
      "owner": "Database engineer",
      "evidence": "Backup timestamp/version and record-count manifest.; Protected-location confirmation and omitted-data list.",
      "dependencies": [
        "D05.1",
        "D03.3"
      ],
      "steps": [
        "Create representative interviews, submissions, cases and requests with known counts.",
        "Use the approved backup/export procedure and record its timestamp/version.",
        "Store the backup in the approved protected location.",
        "Check that intended record types and ownership links are included.",
        "Document missing items and rerun only after the procedure is corrected."
      ],
      "reviewer": "Operations lead",
      "inputs": [
        "Approved recovery plan and disposable cloud test records."
      ],
      "blocker": "Incomplete backup or unapproved access blocks recovery acceptance; never upload raw user backups into shared tasks. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D05.1",
        "D03.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D05.3",
      "anchor": "d05-3",
      "title": "Restore the test backup and demonstrate recovery",
      "group": "D",
      "parent": "D05",
      "result": "A reviewer observes successful restoration of the agreed records with correct ownership and a recorded recovery time.",
      "owner": "Database engineer",
      "evidence": "Restore log and before/after manifest without personal contents.; Restored-access and snapshot checks.; Updated recovery runbook and owner acceptance.",
      "dependencies": [
        "D05.2",
        "D02.1"
      ],
      "steps": [
        "Create an isolated restore destination without overwriting the current release.",
        "Restore using the written procedure and time the recovery.",
        "Compare record counts, ownership, drafts and immutable submission history.",
        "Verify restored-account access while keeping credentials protected.",
        "Record recovery results and update the operator instructions."
      ],
      "reviewer": "Operations lead",
      "inputs": [
        "Validated backup and an isolated recovery environment."
      ],
      "blocker": "Do not run destructive recovery against live data; failed restoration blocks production pilot recovery sign-off. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D05. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D05.2",
        "D02.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D06",
      "anchor": "d06",
      "title": "Complete Beth cloud user-journey acceptance",
      "group": "D",
      "parent": null,
      "result": "Recorded user journeys pass with no blocking issues; consultation requests and simulated communications are described accurately.",
      "owner": "Product QA reviewer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D01.1",
        "D01.2",
        "D03.3",
        "D04.2",
        "D03.2"
      ],
      "steps": [
        "Test home navigation and all four short paths on desktop and mobile",
        "Complete interview, save, submit and download the review pack",
        "Run a cited chat, confirm scope and inspect the indicative estimate",
        "Save and reopen the case and request a consultation",
        "Confirm simulation labels and retain drafts after recoverable failures"
      ],
      "reviewer": "Product QA and business acceptance owner",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D06.1",
        "D06.2",
        "D06.3"
      ],
      "prerequisites": [
        "D01.1",
        "D01.2",
        "D03.3",
        "D04.2",
        "D03.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D06.1",
      "anchor": "d06-1",
      "title": "Verify desktop/mobile navigation and guide journeys",
      "group": "D",
      "parent": "D06",
      "result": "Required entrances and guide journeys work at desktop/mobile sizes with correct links and usable media.",
      "owner": "Product QA reviewer",
      "evidence": "Route/link matrix with preview revision.; Desktop/mobile screenshots and required media results.",
      "dependencies": [
        "D01.1",
        "D01.2"
      ],
      "steps": [
        "Visit home, /chat, /interview, /docs and /cases on desktop and mobile.",
        "Follow guide and legacy links and verify their final destinations.",
        "Check text readability, form controls and downloads at a narrow viewport.",
        "Play the intended guide video, enable captions and inspect transcript access.",
        "Record any dead link, clipped control or inaccessible required guide."
      ],
      "reviewer": "Product owner",
      "inputs": [
        "Cloud preview with guide assets and route mapping."
      ],
      "blocker": "Broken required paths or unusable core controls blocks demo release; cosmetic issues may remain with explicit tracked scope. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1",
        "D01.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D06.2",
      "anchor": "d06-2",
      "title": "Run the interview-to-case demo end to end",
      "group": "D",
      "parent": "D06",
      "result": "One complete demo journey works, retains the right data and makes the boundary between saved requests and real delivery clear.",
      "owner": "Product QA analyst",
      "evidence": "Redacted journey recording or checklist.; Case/request IDs and simulation-label screenshots.; AI connection-mode note for the example.",
      "dependencies": [
        "D03.3",
        "D04.2"
      ],
      "steps": [
        "Complete the example interview and submit/export its answers.",
        "Ask Beth a business question using the accepted connection mode.",
        "Confirm the profiled scope and review the indicative estimate without treating it as a final quote.",
        "Generate, download and print the report; compare it with the confirmed facts, scope and displayed assumptions.",
        "Save/reopen the case and request a specialist consultation.",
        "Verify specialist acceptance, notifications and booking status remain correctly labeled as simulations or saved requests."
      ],
      "reviewer": "Project owner",
      "inputs": [
        "Preview, reviewed example, configured AI mode and disposable customer account."
      ],
      "blocker": "Data loss, an impossible promised action or a simulated action presented as real blocks demo acceptance. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D03.3",
        "D04.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D06.3",
      "anchor": "d06-3",
      "title": "Verify service failures preserve drafts and explain recovery",
      "group": "D",
      "parent": "D06",
      "result": "Recoverable failures preserve work and give clear next actions; unavailable services never appear as successful completion.",
      "owner": "QA engineer",
      "evidence": "Auth/storage/request/media failure matrix.; Draft-retention and recovery screenshots/notes.",
      "dependencies": [
        "D01.1",
        "D03.2",
        "D03.3"
      ],
      "steps": [
        "Exercise expired sign-in while editing and verify the draft remains recoverable.",
        "Simulate storage unavailability and an interrupted save without modifying live services.",
        "Check oversized and malformed requests produce clear messages.",
        "Exercise missing guide media and unknown paths; avoid misleading success screens.",
        "Verify retry/sign-in/reopen instructions return users to a usable state."
      ],
      "reviewer": "Product QA reviewer",
      "inputs": [
        "Preview and approved non-destructive fault tests."
      ],
      "blocker": "Lost drafts or false-success submission messages block demo release; only use isolated test faults. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D06. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.1",
        "D03.2",
        "D03.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D07",
      "anchor": "d07",
      "title": "Hand over Beth cloud release and operating guide",
      "group": "D",
      "parent": null,
      "result": "A named operator can access, support and recover the release using the guide; remaining work has explicit task links.",
      "owner": "Project coordinator",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "D06.1",
        "D06.2",
        "D06.3",
        "D01.3",
        "D05.3",
        "D07.2",
        "P11.2",
        "P15.1",
        "P15.3",
        "P16",
        "P17"
      ],
      "steps": [
        "Publish the verified path and account guide",
        "Explain fresh cloud accounts and how local records are retained",
        "List working functions, simulations and deferred integrations",
        "Document access administration, support and rollback responsibility",
        "Link release checks, recovery evidence and remaining tasks"
      ],
      "reviewer": "Service operations and release acceptance owner",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "D07.1",
        "D07.2",
        "D07.3"
      ],
      "prerequisites": [
        "D06.1",
        "D06.2",
        "D06.3",
        "D01.3",
        "D05.3",
        "P11.2",
        "P15.1",
        "P15.3",
        "P16",
        "P17"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D07.1",
      "anchor": "d07-1",
      "title": "Approve the cloud demo release brief",
      "group": "D",
      "parent": "D07",
      "result": "A reviewer can determine what the demo does, what remains simulated and exactly which verified revision may be released.",
      "owner": "Project coordinator",
      "evidence": "Demo release brief and acceptance record.; Links to preview QA evidence and tracked limitations.",
      "dependencies": [
        "D06.1",
        "D06.2",
        "D06.3"
      ],
      "steps": [
        "List working entrances and tested user journeys.",
        "Explain that cloud accounts are fresh and local records remain on the Mac.",
        "List guided/live AI mode, simulations and known omissions.",
        "Attach release checks and link unresolved work without private commercial details.",
        "Record reviewer acceptance for the demo and the revision to release."
      ],
      "reviewer": "Project owner",
      "inputs": [
        "Preview acceptance results and the agreed demo scope."
      ],
      "blocker": "No demo sign-off while required acceptance fails or scope is misleading; do not wait for every production pilot enhancement. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D06.1",
        "D06.2",
        "D06.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D07.2",
      "anchor": "d07-2",
      "title": "Set up release status checks and operator response steps",
      "group": "D",
      "parent": "D07",
      "result": "The operator can identify an unhealthy release and follow a tested response path without exposing user data or secrets.",
      "owner": "Operations lead",
      "evidence": "Status/check matrix and operator role.; Redacted manual check/rehearsal results and response guide.",
      "dependencies": [
        "D01.3"
      ],
      "steps": [
        "Identify the published version, required URLs and protected status endpoints.",
        "Define simple checks for routes, storage, sign-in and AI availability.",
        "Document where the operator sees errors using redacted logs.",
        "Record who responds to unavailable storage, AI limits and failed uploads.",
        "Run one manual status check and one safe response rehearsal; link the rollback guide."
      ],
      "reviewer": "Deployment engineer",
      "inputs": [
        "Live release and an agreed operator",
        "recurring automation only if separately authorized."
      ],
      "blocker": "Without an operator or a way to detect service failure, mark operational handoff pending; do not silently create recurring monitors. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "D07.3",
      "anchor": "d07-3",
      "title": "Review the separate production pilot go/no-go checklist",
      "group": "D",
      "parent": "D07",
      "result": "The pilot decision is supported by evidence and states allowed users/functions, operational owners and remaining blockers.",
      "owner": "Project owner with operations/domain leads",
      "evidence": "Pilot scope and go/no-go decision.; Recovery and operation evidence links.; Tracked unmet conditions with responsible roles.",
      "dependencies": [
        "D01.3",
        "D05.3",
        "D07.2",
        "P11.2",
        "P15.1",
        "P15.3",
        "P16",
        "P17"
      ],
      "steps": [
        "List which demo functions will be real or explicitly disabled for the pilot.",
        "Confirm reviewed knowledge/service rules, operator responsibilities and consultation follow-up expectations.",
        "Confirm participant notice, access and retention choices for actual customer data.",
        "Review backup recovery, AI usage responsibility and unresolved blocking defects.",
        "Record go/no-go and create a linked action for each unmet condition instead of claiming production readiness."
      ],
      "reviewer": "Pilot sponsor",
      "inputs": [
        "Verified demo, recovery evidence, operating guide and candidate pilot participants."
      ],
      "blocker": "Unreviewed domain advice, unowned customer follow-up or unproven required recovery blocks the relevant production pilot scope, not the labeled demo. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within D07. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "D01.3",
        "D05.3",
        "D07.2",
        "P11.2",
        "P15.1",
        "P15.3",
        "P16",
        "P17"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L01",
      "anchor": "l01",
      "title": "Expand approved journeys, catalogue and language coverage",
      "group": "L",
      "parent": null,
      "result": "The approved broader journeys/services/packages and supported language variants pass domain, scope, pricing and source tests before publication.",
      "owner": "Business analyst, domain reviewers and AI engineer",
      "evidence": "The approved broader journeys/services/packages and supported language variants pass domain, scope, pricing and source tests before publication. — required child reviews and feature-level acceptance evidence.",
      "dependencies": [
        "P12.1",
        "P11.3"
      ],
      "steps": [
        "Accept L01.1: Validate the broader service and package catalogue",
        "Accept L01.2: Implement reviewed advanced-founder routes and escalations",
        "Accept L01.3: Evaluate expanded languages and source/model versions"
      ],
      "reviewer": "Product owner and independent domain reviewers",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Do not start implementation until P12’s pilot review and broader scope/architecture decisions approve this feature and its provider/access requirements.",
      "required_children": [
        "L01.1",
        "L01.2",
        "L01.3"
      ],
      "prerequisites": [
        "P12.1",
        "P11.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L01.1",
      "anchor": "l01-1",
      "title": "Validate the broader service and package catalogue",
      "group": "L",
      "parent": "L01",
      "result": "Every newly included journey/service/package has reviewed evidence and a versioned inclusion decision; old quotes remain replayable.",
      "owner": "Business analyst, domain reviewers and AI engineer",
      "evidence": "Approved expansion register, service/package evidence and quote compatibility results",
      "dependencies": [
        "P12.1",
        "P11.3"
      ],
      "steps": [
        "Confirm the approved subset and target catalogue counts from the broader plan",
        "Complete source-backed service cards, units, prerequisites, exclusions and accountable owners",
        "Compose the approved expanded packages and remove overlapping shared work",
        "Define migration/version compatibility with saved pilot quotes and cases",
        "Review sample scopes and obtain domain/product approval before publishing draft entries"
      ],
      "reviewer": "Product owner and independent domain reviewers",
      "inputs": [
        "Approved P12.1 expansion list and pilot outcome evidence"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.1",
        "P11.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L01.2",
      "anchor": "l01-2",
      "title": "Implement reviewed advanced-founder routes and escalations",
      "group": "L",
      "parent": "L01",
      "result": "Each included advanced route has reviewed deterministic scope and safe human escalation; excluded cases are not priced as ordinary pilot work.",
      "owner": "Business analyst, domain reviewers and AI engineer",
      "evidence": "Approved route/risk matrix, source-linked rules and expected/actual route tests",
      "dependencies": [
        "L01.1",
        "P04.3",
        "P05.3",
        "P06.3"
      ],
      "steps": [
        "Define VAT, payroll, inventory, multiple-entity and foreign-founder route facts for the approved expansion",
        "Obtain domain/counsel decisions for consequential or unsupported scope boundaries",
        "Implement question, eligibility, service-unit and escalation rules from those decisions",
        "Test qualifying, missing-input, ambiguous and out-of-scope variants",
        "Verify estimates, specialist filters and source applicability against each approved route"
      ],
      "reviewer": "Product owner and independent domain reviewers",
      "inputs": [
        "L01.1 service scope and reviewed source applicability"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L01.1",
        "P04.3",
        "P05.3",
        "P06.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L01.3",
      "anchor": "l01-3",
      "title": "Evaluate expanded languages and source/model versions",
      "group": "L",
      "parent": "L01",
      "result": "Supported language variants preserve the approved business decisions and citations; every newly activated source/model passes the agreed regression gate.",
      "owner": "Business analyst, domain reviewers and AI engineer",
      "evidence": "Frozen language suite, reviewed comparison results and configuration/release record",
      "dependencies": [
        "L01.2",
        "P11.2"
      ],
      "steps": [
        "Approve English/Filipino/Taglish scenarios and domain terminology with reviewers",
        "Create held-out translated/paraphrased variants without changing the intended facts",
        "Compare citation support, question burden, scope and estimates across supported language variants",
        "Test each new source family and model version on the same labelled cases",
        "Publish only approved language/source/model configurations with rollback references"
      ],
      "reviewer": "Product owner and independent domain reviewers",
      "inputs": [
        "Approved language list and L01.2 routes"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L01.2",
        "P11.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L02",
      "anchor": "l02",
      "title": "Deliver broader channels, calendar and Babylon adapters",
      "group": "L",
      "parent": null,
      "result": "Approved WhatsApp/LINE channels, one calendar and one Babylon directory/jobs adapter preserve identity, consent, ownership and duplicate-safe action receipts.",
      "owner": "Integration engineer and service operations",
      "evidence": "Approved WhatsApp/LINE channels, one calendar and one Babylon directory/jobs adapter preserve identity, consent, ownership and duplicate-safe action receipts. — required child reviews and feature-level acceptance evidence.",
      "dependencies": [
        "P12.2",
        "P14.3",
        "P17"
      ],
      "steps": [
        "Accept L02.1: Connect WhatsApp and LINE through the approved shared inbox",
        "Accept L02.2: Connect one calendar with duplicate-safe booking synchronisation",
        "Accept L02.3: Implement the approved Babylon directory and job adapter"
      ],
      "reviewer": "Security / integration QA and provider operations owners",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Do not start implementation until P12’s pilot review and broader scope/architecture decisions approve this feature and its provider/access requirements.",
      "required_children": [
        "L02.1",
        "L02.2",
        "L02.3"
      ],
      "prerequisites": [
        "P12.2",
        "P14.3",
        "P17"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L02.1",
      "anchor": "l02-1",
      "title": "Connect WhatsApp and LINE through the approved shared inbox",
      "group": "L",
      "parent": "L02",
      "result": "Each approved real channel reaches the correct retained case, respects human ownership and exposes delivery failures without duplicate tickets.",
      "owner": "Integration engineer and service operations",
      "evidence": "Identity/event mapping, real-channel proof, takeover tests and redacted retry receipts",
      "dependencies": [
        "P12.2",
        "P09.3",
        "P16.3"
      ],
      "steps": [
        "Confirm provider approvals, channel permissions, credentials and allowed message types",
        "Configure the approved inbox integrations and map channel identities to authorised founders",
        "Route new and resumed messages to the correct case and staff owner",
        "Test duplicate/reordered webhooks, unavailable staff and delivery failure",
        "Verify takeover/return-to-Beth and consented sharing on each added channel"
      ],
      "reviewer": "Security/QA and integration owners",
      "inputs": [
        "Approved P12.2 provider/channel selections and account access"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.2",
        "P09.3",
        "P16.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L02.2",
      "anchor": "l02-2",
      "title": "Connect one calendar with duplicate-safe booking synchronisation",
      "group": "L",
      "parent": "L02",
      "result": "Accepted appointments and provider events agree; conflicts/retries cannot create extra reservations and a failed provider action remains recoverable.",
      "owner": "Integration engineer and service operations",
      "evidence": "Contract/state mapping, real provider receipts and conflict/replay/revocation test log",
      "dependencies": [
        "P12.2",
        "P17.3",
        "P14.3"
      ],
      "steps": [
        "Approve required availability/read/write permissions and per-user calendar connections",
        "Map appointment IDs, time zones, durations and accepted booking states to calendar events",
        "Recheck specialist availability before confirmation and store the provider receipt",
        "Synchronise approved reschedules/cancellations with recorded ownership and consent",
        "Test expiry/revocation, webhook replay, conflicts and provider outages with a manual fallback"
      ],
      "reviewer": "Security/QA and integration owners",
      "inputs": [
        "Approved calendar/provider actions and P17 appointment rules"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.2",
        "P17.3",
        "P14.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L02.3",
      "anchor": "l02-3",
      "title": "Implement the approved Babylon directory and job adapter",
      "group": "L",
      "parent": "L02",
      "result": "One approved real adapter transfers the correct authorised data exactly once and reconciles state; catalogue existence is not treated as working integration.",
      "owner": "Integration engineer and service operations",
      "evidence": "Approved contract/mapping, sandbox or real action receipts, reconciliation and failure results",
      "dependencies": [
        "P12.2",
        "P07.3",
        "P08.3",
        "P14.3"
      ],
      "steps": [
        "Approve directory/job identifiers, schema, version and system-of-record ownership",
        "Map specialist capability/capacity and accepted scope/job status without inferred defaults",
        "Authorise each read/write and save stable request/provider receipt identifiers",
        "Test incomplete/stale records, conflict updates, timeouts and duplicate requests",
        "Reconcile one end-to-end job and preserve an explicit manual path for unresolved integration gaps"
      ],
      "reviewer": "Security/QA and integration owners",
      "inputs": [
        "Approved Babylon API contract, access and sandbox data"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.2",
        "P07.3",
        "P08.3",
        "P14.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L03",
      "anchor": "l03",
      "title": "Implement and prove one durable multi-day case lifecycle",
      "group": "L",
      "parent": null,
      "result": "An approved document-wait → approval → reminder → fulfilment lifecycle resumes after failure without lost case state or repeated external actions.",
      "owner": "Workflow/backend engineer and case operations",
      "evidence": "An approved document-wait → approval → reminder → fulfilment lifecycle resumes after failure without lost case state or repeated external actions. — required child reviews and feature-level acceptance evidence.",
      "dependencies": [
        "P12.3",
        "P08",
        "L02"
      ],
      "steps": [
        "Accept L03.1: Approve durable case states, timers and action receipts",
        "Accept L03.2: Build the selected durable workflow and compatible workers",
        "Accept L03.3: Rehearse restart, replay and exception recovery"
      ],
      "reviewer": "Platform / workflow lead and recovery QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Do not start implementation until P12’s pilot review and broader scope/architecture decisions approve this feature and its provider/access requirements.",
      "required_children": [
        "L03.1",
        "L03.2",
        "L03.3"
      ],
      "prerequisites": [
        "P12.3",
        "P08",
        "L02"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L03.1",
      "anchor": "l03-1",
      "title": "Approve durable case states, timers and action receipts",
      "group": "L",
      "parent": "L03",
      "result": "An approved state/timer/receipt contract covers normal, no-response, rejected, cancelled and failed branches without unnamed decisions.",
      "owner": "Workflow/backend engineer and case operations",
      "evidence": "Reviewed state diagram/table, timer policies, action contract and exception ownership",
      "dependencies": [
        "P12.3",
        "P08.3",
        "P13.1"
      ],
      "steps": [
        "Select one bounded lifecycle and define state transitions and authorised actors",
        "Specify document waits, approval deadlines, reminder intervals, cancellation and exception rules",
        "Define stable case/workflow/action IDs, receipts and duplicate-handling behavior",
        "Separate fast conversational replies from the durable case execution path",
        "Approve retention, operator override, failure escalation and recovery expectations"
      ],
      "reviewer": "Workflow QA and operations owner",
      "inputs": [
        "P12.3 selected lifecycle and actual manual-case outcomes"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P12.3",
        "P08.3",
        "P13.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L03.2",
      "anchor": "l03-2",
      "title": "Build the selected durable workflow and compatible workers",
      "group": "L",
      "parent": "L03",
      "result": "The bounded workflow executes the contract with persisted receipts and version-compatible workers; chat remains on its intended fast path.",
      "owner": "Workflow/backend engineer and case operations",
      "evidence": "Pinned workflow/worker artefacts, state/receipt proof and upgrade test results",
      "dependencies": [
        "L03.1",
        "L02.2",
        "L02.3"
      ],
      "steps": [
        "Adopt the workflow platform selected in the approved broader architecture",
        "Implement waits, approvals, reminders and fulfilment activities against saved case versions",
        "Make each external activity consult/save its receipt before retrying",
        "Expose pending/failed work and permitted operator actions in the case portal",
        "Pin worker/workflow versions and test compatibility across a controlled upgrade"
      ],
      "reviewer": "Workflow QA and operations owner",
      "inputs": [
        "L03.1 approved contract",
        "approved workflow platform access"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L03.1",
        "L02.2",
        "L02.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L03.3",
      "anchor": "l03-3",
      "title": "Rehearse restart, replay and exception recovery",
      "group": "L",
      "parent": "L03",
      "result": "Reviewed failure drills restore the right case state without duplicate actions; unresolved exceptions retain an owner and a reproducible recovery path.",
      "owner": "Workflow/backend engineer and case operations",
      "evidence": "Fault/replay matrix, before/after states, receipts, measured recovery and operator review",
      "dependencies": [
        "L03.2",
        "D05.3"
      ],
      "steps": [
        "Stop a worker during document wait and an external action, then resume it",
        "Replay duplicate signals, callbacks and timed reminders",
        "Test approval rejection, cancellation, late documents and operator override",
        "Reconcile workflow state, provider receipts, case status and retained ownership",
        "Measure recovery against the approved target and have operations follow the written runbook"
      ],
      "reviewer": "Workflow QA and operations owner",
      "inputs": [
        "L03.2 implementation and isolated test environment"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L03.2",
        "D05.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L04",
      "anchor": "l04",
      "title": "Prove broader operating scale and release acceptance",
      "group": "L",
      "parent": null,
      "result": "Broader functions, traffic capacity, operational analytics and recovery have reviewed measurable results and a staged release/rollback decision.",
      "owner": "QA/AI evaluation, platform engineer and operations analyst",
      "evidence": "Broader functions, traffic capacity, operational analytics and recovery have reviewed measurable results and a staged release/rollback decision. — required child reviews and feature-level acceptance evidence.",
      "dependencies": [
        "L01",
        "L02",
        "L03",
        "P12.3"
      ],
      "steps": [
        "Accept L04.1: Extend quote-versus-actual and delivery outcome analytics",
        "Accept L04.2: Measure larger traffic, permission and failure capacity",
        "Accept L04.3: Review broader launch, staged rollout and rollback"
      ],
      "reviewer": "Business operations, quality and release reviewers",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Do not start implementation until P12’s pilot review and broader scope/architecture decisions approve this feature and its provider/access requirements.",
      "required_children": [
        "L04.1",
        "L04.2",
        "L04.3"
      ],
      "prerequisites": [
        "L01",
        "L02",
        "L03",
        "P12.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L04.1",
      "anchor": "l04-1",
      "title": "Extend quote-versus-actual and delivery outcome analytics",
      "group": "L",
      "parent": "L04",
      "result": "Reviewed analytics reproduce underlying job evidence and clearly distinguish measured, estimated and missing outcomes.",
      "owner": "QA/AI evaluation, platform engineer and operations analyst",
      "evidence": "Approved metric definitions, reconciliation results, permission checks and reviewed improvement proposals",
      "dependencies": [
        "P11.3",
        "L01.1",
        "L02.3"
      ],
      "steps": [
        "Approve metrics for quoted/actual effort, rework, scope changes, conversion and quality",
        "Link each outcome to saved case, quote/rule/source/release versions",
        "Implement authorised aggregation without exposing individual confidential records",
        "Reconcile dashboard totals against representative job records and missing-data cases",
        "Submit proposed rule/capacity changes for review rather than auto-editing prices"
      ],
      "reviewer": "Release owner and domain/operations leads",
      "inputs": [
        "P11.3 pilot outcome contract and approved broader metrics"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "P11.3",
        "L01.1",
        "L02.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L04.2",
      "anchor": "l04-2",
      "title": "Measure larger traffic, permission and failure capacity",
      "group": "L",
      "parent": "L04",
      "result": "Measured results support an approved broader capacity envelope, with unresolved limits explicitly gating the affected scope.",
      "owner": "QA/AI evaluation, platform engineer and operations analyst",
      "evidence": "Approved workload/threshold plan, measured results, defects/retests and capacity decision",
      "dependencies": [
        "L01.3",
        "L02.1",
        "L03.3",
        "P15.3"
      ],
      "steps": [
        "Confirm the proposed 2,000 monthly active founders and 100 simultaneous-session envelope or an approved replacement",
        "Approve meaningful latency/error/spend/recovery thresholds before testing",
        "Run representative chat, source, file, save, handoff and durable-case traffic",
        "Include cross-business permission attempts, provider/source failures and retry pressure",
        "Record bottlenecks, limits and corrective defects; retest only affected failures"
      ],
      "reviewer": "Release owner and domain/operations leads",
      "inputs": [
        "Stable broader candidate and approved test thresholds/workload"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L01.3",
        "L02.1",
        "L03.3",
        "P15.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "L04.3",
      "anchor": "l04-3",
      "title": "Review broader launch, staged rollout and rollback",
      "group": "L",
      "parent": "L04",
      "result": "A named release authority approves only the evidenced scope and operating limits; staged validation and rollback proof precede expansion.",
      "owner": "QA/AI evaluation, platform engineer and operations analyst",
      "evidence": "Signed release checklist/decision, scoped rollout record and rollback/recovery rehearsal",
      "dependencies": [
        "L04.1",
        "L04.2",
        "L03.3"
      ],
      "steps": [
        "Reconcile feature coverage, required approvals and all open blocking defects",
        "Review source/model regressions, role permissions, consent/retention and real channel/booking receipts",
        "Confirm incident, specialist follow-up, backups and provider/edition responsibilities",
        "Approve staged users/features, stop criteria and rollback/recovery versions",
        "Record launch decision and verify the first stage before expansion"
      ],
      "reviewer": "Release owner and domain/operations leads",
      "inputs": [
        "Broader feature, analytics, capacity and recovery evidence"
      ],
      "blocker": "P12 approval, missing provider permissions, unresolved policy or failed expected behavior blocks the affected implementation. Record the exact missing input, decision/action owner and next checkpoint. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within L04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "L04.1",
        "L04.2",
        "L03.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B01",
      "anchor": "b01",
      "title": "Build a backend conversation prototype",
      "group": "B",
      "parent": null,
      "result": "An independently reviewed deliverable meets the ordered checks below, with reproducible evidence and explicit remaining limitations.",
      "owner": "Backend / AI developer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "B01.1",
        "B01.2"
      ],
      "steps": [
        "Agree the request/response format with the interface developer",
        "Build the candidate Langflow conversation using fictional data",
        "Collect support requested, monthly order volume and record format",
        "Retain earlier answers and apply one corrected answer",
        "Publish setup instructions, sample requests/responses and limitations"
      ],
      "reviewer": "Backend / AI technical reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "B01.1",
        "B01.2",
        "B01.3"
      ],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B01.1",
      "anchor": "b01-1",
      "title": "Agree and prove the conversation API contract",
      "group": "B",
      "parent": "B01",
      "result": "Both developers use one versioned schema; all three prototype facts, corrections and errors have examples.",
      "owner": "Backend / AI developer",
      "evidence": "Versioned schema, four fixture request/response pairs and both developers’ review record",
      "dependencies": [],
      "steps": [
        "Write request fields for chat/session ID, message and prior confirmed facts",
        "Define response fields for reply, collected facts, missing fields and errors",
        "Use the fictional online-shop scenario to create complete and missing-field fixtures",
        "Confirm correction/reset/session isolation semantics with the interface developer",
        "Have both developers approve the schema and publish runnable example calls"
      ],
      "reviewer": "Interface developer and QA",
      "inputs": [
        "Existing backend prototype brief and interface consumer"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B01.2",
      "anchor": "b01-2",
      "title": "Implement retained facts and corrections in the candidate flow",
      "group": "B",
      "parent": "B01",
      "result": "Complete, missing-field, correction and reset fixtures return expected state without cross-session leakage.",
      "owner": "Backend / AI developer",
      "evidence": "Runnable flow export/code, fixture outputs and limitations log",
      "dependencies": [
        "B01.1"
      ],
      "steps": [
        "Build the bounded candidate flow and record its version",
        "Retain support requested, monthly order volume and record format per session",
        "Ask only for fields not already supplied",
        "Apply a corrected value without erasing other confirmed fields",
        "Reset one session and prove a second session is unaffected",
        "Return the agreed response schema and record candidate limitations"
      ],
      "reviewer": "Interface developer and QA",
      "inputs": [
        "Approved B01.1 schema",
        "candidate Langflow access"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B01.3",
      "anchor": "b01-3",
      "title": "Package and independently verify the backend prototype",
      "group": "B",
      "parent": "B01",
      "result": "A reviewer can reproduce the demonstration from the handoff and trace each result to the agreed schema.",
      "owner": "Backend / AI developer",
      "evidence": "Setup guide, version, test log, demo link and review outcome",
      "dependencies": [
        "B01.2"
      ],
      "steps": [
        "Write setup/version/configuration instructions without credentials",
        "Provide sample calls for all agreed fixture scenarios",
        "Run from a clean test setup with a second developer",
        "Record expected versus actual responses and defects",
        "Demonstrate the flow and obtain review against the parent card’s outcome"
      ],
      "reviewer": "Interface developer and QA",
      "inputs": [
        "B01.2 runnable build and fixtures"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B01. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B02",
      "anchor": "b02",
      "title": "Build a customer chat and information-panel prototype",
      "group": "B",
      "parent": null,
      "result": "An independently reviewed deliverable meets the ordered checks below, with reproducible evidence and explicit remaining limitations.",
      "owner": "Frontend developer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "B01.1",
        "B02.1",
        "B02.2",
        "B01.2"
      ],
      "steps": [
        "Agree the interface/backend request and response format",
        "Build accumulating chat and a visible collected-information panel",
        "Update the panel after a corrected answer",
        "Implement loading, response-error and reset behaviour",
        "Evaluate CopilotKit/AG-UI and publish setup instructions and a short demo"
      ],
      "reviewer": "Product / UX reviewer and integration QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "B02.1",
        "B02.2",
        "B02.3"
      ],
      "prerequisites": [
        "B01.1",
        "B01.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B02.1",
      "anchor": "b02-1",
      "title": "Prove the chat adapter against the agreed contract",
      "group": "B",
      "parent": "B02",
      "result": "Selected adapter displays every fixture accurately; limitations and fallback choice are explicit.",
      "owner": "Frontend developer",
      "evidence": "Mapping, adapter proof, fixtures and reviewed transport decision",
      "dependencies": [
        "B01.1"
      ],
      "steps": [
        "Confirm message, fact-panel and error mappings to B01.1",
        "Create mock complete/missing/correction/reset responses",
        "Try the scoped CopilotKit / AG-UI candidate with the same fixtures",
        "Record transport limitations and select one adapter for this prototype",
        "Publish the adapter mapping and implementation decision"
      ],
      "reviewer": "Backend developer and QA",
      "inputs": [
        "B01.1 schema",
        "frontend assessment"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B02.2",
      "anchor": "b02-2",
      "title": "Build chat, information panel and recoverable states",
      "group": "B",
      "parent": "B02",
      "result": "The customer sees the latest three facts; loading/error/reset cases are predictable and do not lose unrelated data.",
      "owner": "Frontend developer",
      "evidence": "Runnable interface, fixture screenshots and expected/actual UI checklist",
      "dependencies": [
        "B02.1"
      ],
      "steps": [
        "Render accumulated messages with usable scrolling",
        "Display support requested, order volume and record format in the customer panel",
        "Update only the corrected fact and preserve the remaining facts",
        "Show loading and prevent duplicate sends",
        "Show response errors while retaining input and prior conversation",
        "Reset conversation and panel together and check desktop/mobile usability"
      ],
      "reviewer": "Backend developer and QA",
      "inputs": [
        "B02.1 selected adapter and fixture mapping"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B02.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B02.3",
      "anchor": "b02-3",
      "title": "Verify the interface with mocks and the backend",
      "group": "B",
      "parent": "B02",
      "result": "All prototype UI cases have reproducible results; mock demonstrations are never reported as live integration success.",
      "owner": "Frontend developer",
      "evidence": "Versioned setup, test log with environment, defects and demo/reviewer decision",
      "dependencies": [
        "B02.2",
        "B01.2"
      ],
      "steps": [
        "Run the four agreed scenarios with mocks",
        "Connect B01.2 when available and repeat the same scenarios",
        "Record whether each result is mock-backed or backend-backed",
        "Reproduce and log defects with environment and input",
        "Publish setup instructions and a short reviewed demonstration"
      ],
      "reviewer": "Backend developer and QA",
      "inputs": [
        "B02.2",
        "real backend if available"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B02. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B02.2",
        "B01.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B03",
      "anchor": "b03",
      "title": "Implement a structured intake example",
      "group": "B",
      "parent": null,
      "result": "An independently reviewed deliverable meets the ordered checks below, with reproducible evidence and explicit remaining limitations.",
      "owner": "Intake / backend developer",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "B01.1",
        "B03.1",
        "B03.2"
      ],
      "steps": [
        "Assess the RFQ logic and agree the summary format",
        "Implement missing-field questions for the three prototype fields",
        "Retain supplied information across messages",
        "Allow a prior answer to be corrected",
        "Demonstrate a complete structured summary and document adapted logic"
      ],
      "reviewer": "Business analyst and domain / intake reviewer",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "B03.1",
        "B03.2",
        "B03.3"
      ],
      "prerequisites": [
        "B01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B03.1",
      "anchor": "b03-1",
      "title": "Select reusable intake logic and define summary fields",
      "group": "B",
      "parent": "B03",
      "result": "There is one reviewed summary schema and a documented reuse decision without importing Alpha pricing or eligibility rules.",
      "owner": "Intake / backend developer",
      "evidence": "Assessment notes, schema, fixtures and reviewed reuse decision",
      "dependencies": [
        "B01.1"
      ],
      "steps": [
        "Inspect the assessment for retained-state and missing-field patterns",
        "Choose adapt/rebuild for each pattern and record the reason",
        "Define support requested, monthly order volume and record format with explicit unknowns",
        "Agree the structured summary with the backend developer",
        "Label the fields as prototype examples rather than approved service rules"
      ],
      "reviewer": "Backend lead and QA",
      "inputs": [
        "RFQ Alpha assessment and prototype brief"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B03.2",
      "anchor": "b03-2",
      "title": "Implement incomplete and corrected intake paths",
      "group": "B",
      "parent": "B03",
      "result": "Incomplete and corrected requests produce the expected latest facts with no fabricated field values.",
      "owner": "Intake / backend developer",
      "evidence": "Runnable code/configuration and scenario inputs/outputs",
      "dependencies": [
        "B03.1"
      ],
      "steps": [
        "Load known answers and preserve unknown fields explicitly",
        "Ask for one missing field without repeating supplied information",
        "Update the relevant field when the customer corrects an answer",
        "Preserve the rest of the summary after a correction",
        "Return the latest structured summary and implement a clean reset"
      ],
      "reviewer": "Backend lead and QA",
      "inputs": [
        "B03.1 approved schema"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B03.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B03.3",
      "anchor": "b03-3",
      "title": "Handoff a reproducible intake example",
      "group": "B",
      "parent": "B03",
      "result": "Another person can reproduce the example and determine the latest answers without relying on the author’s explanation.",
      "owner": "Intake / backend developer",
      "evidence": "Version, instructions, result log and QA review",
      "dependencies": [
        "B03.2"
      ],
      "steps": [
        "Write setup and execution instructions",
        "Run complete, missing-field, correction and reset cases",
        "Check outputs against the approved summary schema",
        "Record adapted versus rebuilt logic and known gaps",
        "Have QA reproduce the cases and record acceptance or defects"
      ],
      "reviewer": "Backend lead and QA",
      "inputs": [
        "B03.2 runnable example"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B03. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B03.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B04",
      "anchor": "b04",
      "title": "Build a source-backed service record and verify the intake example",
      "group": "B",
      "parent": null,
      "result": "An independently reviewed deliverable meets the ordered checks below, with reproducible evidence and explicit remaining limitations.",
      "owner": "Service knowledge / QA analyst",
      "evidence": "Required child acceptance records plus evidence that the parent’s feature outcome and original checklist pass. Use retrievable redacted links, exact versions and expected/actual results.",
      "dependencies": [
        "B01.1",
        "B03.1",
        "B01.3",
        "B02.3",
        "B03.3",
        "B04.2"
      ],
      "steps": [
        "Select one service and record source references for each populated field",
        "Record required customer details, scope, exclusions and handoff destination",
        "Flag missing/conflicting information without inventing business rules",
        "Run complete, missing-field, corrected-answer and reset scenarios",
        "Record expected/actual results and reproducible defects"
      ],
      "reviewer": "Domain / knowledge reviewer and prototype QA",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [
        "B04.1",
        "B04.2",
        "B04.3"
      ],
      "prerequisites": [
        "B01.1",
        "B03.1",
        "B01.3",
        "B02.3",
        "B03.3"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B04.1",
      "anchor": "b04-1",
      "title": "Extract one service record with field-level sources",
      "group": "B",
      "parent": "B04",
      "result": "Every populated service field has a retrievable source; inferred and disputed requirements are clearly marked unapproved.",
      "owner": "Service knowledge / QA analyst",
      "evidence": "Structured service record, source locator table and gap/review log",
      "dependencies": [],
      "steps": [
        "Select one service from existing catalogue/interview material",
        "Record source ID, version/date and exact location for each populated field",
        "Extract required customer information, scope, exclusions and handoff destination",
        "Separate stated facts from inference and unresolved gaps",
        "Ask the service owner to review missing or conflicting material"
      ],
      "reviewer": "Service owner and prototype developers",
      "inputs": [
        "Source access from the project’s source-material owner"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B04.2",
      "anchor": "b04-2",
      "title": "Write expected results for the four prototype scenarios",
      "group": "B",
      "parent": "B04",
      "result": "Each test has fixed input, pre-state, expected reply/state and pass/fail criterion; actual results cannot redefine the expectation.",
      "owner": "Service knowledge / QA analyst",
      "evidence": "Reviewed test matrix with complete/missing/correction/reset fixtures",
      "dependencies": [
        "B01.1",
        "B03.1"
      ],
      "steps": [
        "Prepare a fictional request with all three prototype fields",
        "Prepare a request missing one field and identify the required follow-up",
        "Prepare a corrected earlier answer and the expected retained state",
        "Prepare a reset case with an explicit empty-session expectation",
        "Review expected outputs with the developers before running tests"
      ],
      "reviewer": "Service owner and prototype developers",
      "inputs": [
        "B01.1 and B03.1 schemas"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.1",
        "B03.1"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "B04.3",
      "anchor": "b04-3",
      "title": "Run available prototypes and report reproducible defects",
      "group": "B",
      "parent": "B04",
      "result": "Every available prototype has recorded results; missing builds and unresolved failures are visible and reproducible.",
      "owner": "Service knowledge / QA analyst",
      "evidence": "Test log, defects, retest evidence and reviewer decision",
      "dependencies": [
        "B01.3",
        "B02.3",
        "B03.3",
        "B04.2"
      ],
      "steps": [
        "Record backend, frontend and intake build versions and availability",
        "Run each scenario against each available prototype",
        "Record expected and actual output with evidence",
        "Mark unavailable builds as blocked/not tested rather than passed",
        "Give each defect reproduction steps, severity and proposed owner",
        "Retest fixes and publish the reviewed result summary"
      ],
      "reviewer": "Service owner and prototype developers",
      "inputs": [
        "B04.2 expected results",
        "developer runnable handoffs"
      ],
      "blocker": "Record the unavailable input/build/decision, exact failing step, responsible role and next action. Unavailable or not-run checks cannot pass. Set Stage to Blocked and record the exact failing step, missing decision/input, responsible role and next action in Blocker / decision needed.",
      "boundary": "A bounded deliverable within B04. Changes to adjacent work require the accountable scope owner’s decision.",
      "required_children": [],
      "prerequisites": [
        "B01.3",
        "B02.3",
        "B03.3",
        "B04.2"
      ],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "G01",
      "anchor": "g01",
      "title": "Assign ownership and use the delivery reporting rules",
      "group": "G",
      "parent": null,
      "result": "Project tasks state accepted feature outcomes. Work packages are independently assigned and reviewed. Their numbered native checklists are the execution steps. Parent checklists record high-level deliverables; they do not auto-sync with child checklists.",
      "owner": "Project lead / delivery coordinator",
      "evidence": "Responsibility register, agreed checkpoint plan and one reviewed sample work-package report.",
      "dependencies": [],
      "steps": [
        "Assign one accountable worker and designated reviewer per work package",
        "Agree prerequisite evidence and target checkpoint before moving a package to To Do",
        "Use the structured Latest report and actual Last reported time",
        "Record blockers with an exact decision/action and responsible role",
        "Test one evidence-backed reviewer handoff",
        "Accept parent features only after required package and feature acceptance"
      ],
      "reviewer": "Delivery manager / accountable project owner",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    },
    {
      "code": "G02",
      "anchor": "g02",
      "title": "Review feature coverage and acceptance traceability",
      "group": "G",
      "parent": null,
      "result": "Sweep dated 8 Oct 2026. Source: Beth 2.0 project scope (6 Oct revision), learning/interview plans and current deployment evidence. Covers all 12 mapped screens and 28 visible feature hotspots, shared release functions and the approved/planned broader-release requirements. This is a coverage plan, not proof that the features are accepted.",
      "owner": "Project lead / feature reviewers",
      "evidence": "Dated project-owner review of the feature inventory, package mappings and unresolved scope decisions.",
      "dependencies": [],
      "steps": [
        "Inventory the 12 mapped screens and 28 visible features",
        "Map required outcomes and acceptance tests to valid work-package codes",
        "Check package requirements and dependency graph for cycles",
        "Record project-owner review and reconcile any scope changes"
      ],
      "reviewer": "Product owner and technical / feature acceptance leads",
      "inputs": [
        "Current approved scope and relevant existing artifacts.",
        "Prerequisite outcomes and evidence listed below; confirm applicability before starting."
      ],
      "blocker": "Keep the affected step open, record the exact missing input or decision, identify its accountable owner and agree the next checkpoint.",
      "boundary": "Parent task owns the stated feature outcome. Child packages are delegated and reviewed separately.",
      "required_children": [],
      "prerequisites": [],
      "features": [],
      "assignment_gate": "Confirm a named worker, a named reviewer, the source revision, available inputs, a validated effort estimate and an agreed checkpoint before starting.",
      "estimate": "Owner to validate at assignment. Existing workstream allocations remain the planning basis; do not count this package again as extra effort.",
      "done_gate": "Attach the exact artifact/version, expected-versus-actual results and evidence links. The designated reviewer records a dated acceptance decision. Checked boxes alone do not establish completion."
    }
  ],
  "schema_version": 2,
  "blueprint_id": "beth-delegation",
  "revision": "2026-10-09.1",
  "approval_status": "Draft — requires product and reviewer approval",
  "authority": "Define and revise work in this source blueprint; StartInfinity tracks assignment, execution and acceptance.",
  "authoring_basis": "Existing scope, feature coverage and granular work plans, reconciled with current task definitions. Earlier board-first references have been consolidated into this source revision.",
  "features": [
    {
      "code": "start.1",
      "title": "Ask Beth a question",
      "requirement": "Let a founder describe a problem in their own words and receive a useful next step.",
      "acceptance": "An interrupted reply can resume without losing confirmed facts or repeating an action.",
      "packages": [
        "P14.1",
        "P14.2",
        "P05.2",
        "P11.2"
      ],
      "screen_url": "/scope#view-start-1"
    },
    {
      "code": "start.2",
      "title": "Choose a starting situation",
      "requirement": "Use a recognisable concern to start relevant questions, without asking for documents immediately.",
      "acceptance": "An online seller and a foreign founder receive the relevant follow-up questions.",
      "packages": [
        "P05.1",
        "P05.2",
        "P05.3",
        "P01.1"
      ],
      "screen_url": "/scope#view-start-2"
    },
    {
      "code": "start.3",
      "title": "Start a new conversation",
      "requirement": "Keep unrelated issues separate while retaining each conversation for later.",
      "acceptance": "A new concern does not inherit the previous conversation’s unconfirmed facts.",
      "packages": [
        "P14.1",
        "P14.2",
        "P13.3"
      ],
      "screen_url": "/scope#view-start-3"
    },
    {
      "code": "access.1",
      "title": "Sign in",
      "requirement": "Associate saved chats, interview answers and cases with the correct account.",
      "acceptance": "A different founder cannot read this account’s conversation or case.",
      "packages": [
        "P16.1",
        "D02.1",
        "D02.3"
      ],
      "screen_url": "/scope#view-access-1"
    },
    {
      "code": "access.2",
      "title": "Create an account",
      "requirement": "Let a first-time founder register before saving their journey.",
      "acceptance": "A new verified account can save and recall its own work.",
      "packages": [
        "P16.1",
        "D02.1"
      ],
      "screen_url": "/scope#view-access-2"
    },
    {
      "code": "sources.1",
      "title": "Read the cited guidance",
      "requirement": "Explain an answer with supporting evidence and the limits of that evidence.",
      "acceptance": "Every material compliance claim points to a supporting approved passage.",
      "packages": [
        "P04.1",
        "P04.2",
        "P04.3",
        "P14.1",
        "P14.2",
        "P14.3"
      ],
      "screen_url": "/scope#view-sources-1"
    },
    {
      "code": "sources.2",
      "title": "Open the original source",
      "requirement": "Let the founder verify the original reference rather than rely only on Beth’s summary.",
      "acceptance": "A superseded rule is flagged instead of presented as current advice.",
      "packages": [
        "P04.1",
        "P04.3"
      ],
      "screen_url": "/scope#view-sources-2"
    },
    {
      "code": "profile.1",
      "title": "Review the business facts",
      "requirement": "Turn a conversation into understandable facts: business type, location, workload and registration status.",
      "acceptance": "Changing monthly entries updates the correct workload band and retains an audit trail.",
      "packages": [
        "P05.1",
        "P05.2",
        "P05.3",
        "P06.2"
      ],
      "screen_url": "/scope#view-profile-1"
    },
    {
      "code": "profile.2",
      "title": "Confirm the proposed scope",
      "requirement": "Get the founder’s agreement that Beth has identified the right problem before preparing an estimate.",
      "acceptance": "No estimate treats an unconfirmed guess as a verified business fact.",
      "packages": [
        "P05.3",
        "P06.3"
      ],
      "screen_url": "/scope#view-profile-2"
    },
    {
      "code": "quote.1",
      "title": "Indicative range and billing period",
      "requirement": "Show what the founder may pay, whether the work is one-off or recurring, and how certain the estimate is.",
      "acceptance": "The same facts and price version reproduce the same range; missing facts widen or block the estimate.",
      "packages": [
        "P06.1",
        "P06.2",
        "P06.3",
        "P01.2"
      ],
      "screen_url": "/scope#view-quote-1"
    },
    {
      "code": "quote.2",
      "title": "What the package includes",
      "requirement": "Translate service codes into clear line items and their purpose, without charging twice for shared work.",
      "acceptance": "Two services sharing setup work include that setup cost only once.",
      "packages": [
        "P06.2",
        "P06.3",
        "P01.3"
      ],
      "screen_url": "/scope#view-quote-2"
    },
    {
      "code": "report.1",
      "title": "Babylon 2k report and scope",
      "requirement": "Give the founder a branded record of the situation, recommendation and estimate.",
      "acceptance": "The report matches the quote version the founder reviewed, even after price rules change.",
      "packages": [
        "P13.1",
        "P13.2",
        "P06.3",
        "P08.1"
      ],
      "screen_url": "/scope#view-report-1"
    },
    {
      "code": "report.2",
      "title": "Download, print or save",
      "requirement": "Allow the founder to retain or share the recommendation without repeating the interview.",
      "acceptance": "Only an authorised user can retrieve the saved report.",
      "packages": [
        "P13.2",
        "P13.3",
        "D02.2"
      ],
      "screen_url": "/scope#view-report-2"
    },
    {
      "code": "specialists.1",
      "title": "Compare suitability",
      "requirement": "Explain why a specialist fits the location, service and complexity of this business.",
      "acceptance": "A nearby profile lacking the required verified skill does not outrank a qualified specialist.",
      "packages": [
        "P07.1",
        "P07.2",
        "P07.3",
        "P12.1"
      ],
      "screen_url": "/scope#view-specialists-1"
    },
    {
      "code": "specialists.2",
      "title": "Select this specialist",
      "requirement": "Carry the selected specialist and business brief into booking or case assignment.",
      "acceptance": "The appointment and case retain the selected eligible specialist.",
      "packages": [
        "P07.3",
        "P08.1",
        "P08.3"
      ],
      "screen_url": "/scope#view-specialists-2"
    },
    {
      "code": "booking.1",
      "title": "Preferred date and time",
      "requirement": "Collect a convenient time and meeting format without suggesting the specialist has accepted it.",
      "acceptance": "A request remains pending until confirmed, and conflicting confirmed slots are prevented.",
      "packages": [
        "P17.1",
        "P17.2"
      ],
      "screen_url": "/scope#view-booking-1"
    },
    {
      "code": "booking.2",
      "title": "Save appointment request",
      "requirement": "Persist the request, brief and selected specialist so the founder can follow up.",
      "acceptance": "A retried save creates one appointment request, not two.",
      "packages": [
        "P17.1",
        "P17.2",
        "P17.3",
        "P15.1"
      ],
      "screen_url": "/scope#view-booking-2"
    },
    {
      "code": "handoff.1",
      "title": "Live / Not live indicator",
      "requirement": "Show whether a verified specialist is available and switch conversation ownership when they accept.",
      "acceptance": "A stale presence signal is marked unavailable; Beth cannot talk over an active human specialist.",
      "packages": [
        "P09.1",
        "P09.2",
        "P09.3",
        "P07.2",
        "P16.1",
        "P16.2",
        "P16.3"
      ],
      "screen_url": "/scope#view-handoff-1"
    },
    {
      "code": "handoff.2",
      "title": "Consent to share the brief",
      "requirement": "Let the founder decide whether the specialist receives the conversation summary and contact details.",
      "acceptance": "The handoff cannot expose a summary the founder has not agreed to share.",
      "packages": [
        "P13.1",
        "P13.3",
        "P09.1",
        "P09.3"
      ],
      "screen_url": "/scope#view-handoff-2"
    },
    {
      "code": "handoff.3",
      "title": "Create a case and request a human",
      "requirement": "Keep a task with the chosen specialist even if nobody replies immediately.",
      "acceptance": "An offline specialist still receives an assigned case, with queued delivery tracked separately.",
      "packages": [
        "P09.1",
        "P09.3",
        "P08.1"
      ],
      "screen_url": "/scope#view-handoff-3"
    },
    {
      "code": "portal.1",
      "title": "Case status and owner",
      "requirement": "Show the founder who is responsible and what happens next.",
      "acceptance": "The founder and assigned staff see the correct case; unrelated staff cannot access its files.",
      "packages": [
        "P08.1",
        "P08.2",
        "P08.3",
        "P16.1",
        "P16.2",
        "P16.3",
        "P12.2"
      ],
      "screen_url": "/scope#view-portal-1"
    },
    {
      "code": "portal.2",
      "title": "Approve scope and budget",
      "requirement": "Require the founder’s approval before a specialist begins additional work.",
      "acceptance": "A specialist cannot start extra work without approval of that exact scope and fee.",
      "packages": [
        "P08.2",
        "P06.3",
        "P16.1",
        "P16.2",
        "P16.3"
      ],
      "screen_url": "/scope#view-portal-2"
    },
    {
      "code": "portal.3",
      "title": "Notification delivery status",
      "requirement": "Make staff and founder alerts traceable rather than assume a message was delivered.",
      "acceptance": "One case event produces one notification; a failed delivery is visible and can be retried.",
      "packages": [
        "P15.1",
        "P09.3"
      ],
      "screen_url": "/scope#view-portal-3"
    },
    {
      "code": "history.1",
      "title": "Search previous conversations",
      "requirement": "Save time by finding an earlier business issue and its recommendation.",
      "acceptance": "Search returns this founder’s records without exposing another account’s data.",
      "packages": [
        "P13.3",
        "P14.2",
        "P16.1"
      ],
      "screen_url": "/scope#view-history-1"
    },
    {
      "code": "history.2",
      "title": "Recall or delete",
      "requirement": "Resume context or remove the chat with a clear explanation of what is retained in an open case.",
      "acceptance": "Deletion removes the intended chat and does not silently delete an active case obligation.",
      "packages": [
        "P13.3",
        "D03.2",
        "P16.3"
      ],
      "screen_url": "/scope#view-history-2"
    },
    {
      "code": "workshop.1",
      "title": "Role interviews and service effort cards",
      "requirement": "Collect expert decisions, effort drivers and cost inputs that explain a founder question or quotation rule.",
      "acceptance": "An answer with no decision consumer is removed; unapproved answers cannot alter production prices.",
      "packages": [
        "P02.1",
        "P02.2",
        "P02.3",
        "P03.1",
        "P03.2",
        "P03.3",
        "P10.1",
        "P10.2",
        "P10.3"
      ],
      "screen_url": "/scope#view-workshop-1"
    },
    {
      "code": "workshop.2",
      "title": "Package composition and draft comparison",
      "requirement": "Show which service items and cost inputs create each package before a manager approves them.",
      "acceptance": "Publishing a new price version changes future quotes while preserving previous ones.",
      "packages": [
        "P06.1",
        "P06.2",
        "P06.3",
        "P01.3",
        "P10.2",
        "P10.3"
      ],
      "screen_url": "/scope#view-workshop-2"
    },
    {
      "code": "workshop.3",
      "title": "Readiness and evidence check",
      "requirement": "Separate completing the survey from proving that Beth quotes and advises accurately.",
      "acceptance": "A complete survey with zero job evidence is not reported as a proven accurate quotation engine.",
      "packages": [
        "P11.1",
        "P11.2",
        "P11.3",
        "P10.2",
        "P10.3",
        "P15.1",
        "P15.2",
        "P15.3"
      ],
      "screen_url": "/scope#view-workshop-3"
    }
  ],
  "card_translation": {
    "parent": "Parent task → one feature-outcome card",
    "package": "Sub-package → one independently assigned and reviewed work-package card",
    "steps": "Ordered source steps → native card checklist",
    "source_link": "Stable code anchor and source revision → card description",
    "execution_owned_by_infinity": [
      "Assignees",
      "Reviewer",
      "Stage",
      "Due Date",
      "Completed",
      "Checklist completion",
      "Latest report",
      "Blocker / decision needed",
      "Evidence attachments",
      "Comments"
    ],
    "change_control": "Review source changes first. Compare affected card definitions before applying them. Preserve existing execution fields; retire removed work explicitly instead of deleting it. Publication is not scope approval.",
    "sync_status": "Explicit source-reference update for this revision; no background automatic sync."
  }
}