{
 "version": "1.8.0",
 "slug": "fema-public-assistance-recovery-engine",
 "title": "FEMA Public Assistance Recovery & Appeals Engine",
 "vertical": "FEMA disaster-recovery grant documentation & appeals compliance",
 "seed": {
  "s": "fema-public-assistance-recovery-engine",
  "t": "Reoblige — FEMA Public Assistance documentation, recovery & appeals engine",
  "v": "FEMA disaster-recovery grant documentation & appeals compliance",
  "r": "High",
  "m": "M"
 },
 "product": {
  "slug": "fema-public-assistance-recovery-engine",
  "project_name": "FEMA Public Assistance Recovery & Appeals Engine",
  "project_type": "done-for-you FEMA Public Assistance documentation & appeals managed service",
  "vertical": "FEMA disaster-recovery grant compliance",
  "audience": "Recovery coordinators, grants managers, controllers, and CFOs at mid-market FEMA PA applicants: private nonprofit hospitals, private colleges, electric & water co-ops, special districts, fire/EMS districts, school districts, and small municipalities",
  "geography": "United States — any county under a FEMA major disaster declaration",
  "scale_expectation": "Sublinear headcount: an AI/automation pipeline gated by two human chokepoints (senior PA specialist review + authorized-representative certification)",
  "core_workflows": [
   "Aggregate and normalize reimbursable cost records into a canonical cost-line schema",
   "Map every cost line to PAPPG V5 eligibility and 2 CFR 200 cost principles, then run insurance-offset and procurement checks",
   "Draft Project Worksheets, RFI responses, and first/second appeals with correct policy citations",
   "Assemble the certification-ready Recovery File and track the 60-day appeal clock through submission"
  ],
  "discovery": {
   "one_line_purpose": "Keep obligated FEMA Public Assistance dollars from being deobligated at closeout, and win back denied dollars on appeal, for applicants too small for the national consultancies.",
   "primary_users": [
    "Recovery coordinator / grants manager assembling the file",
    "CFO / Finance Director accountable for surviving the Single Audit",
    "Senior PA specialist validating eligibility and appeal strategy"
   ],
   "jobs_to_be_done": [
    "Turn messy disaster cost records into a FEMA-defensible file so every eligible dollar survives closeout",
    "File a winning first or second appeal before the 60-day clock runs out",
    "Stay clean for the Single Audit and any DHS OIG review that follows the grant"
   ],
   "value_prop": "A defended, closeout-ready outcome — not software the recovery office has to operate — priced per deliverable and reimbursable inside the management-cost pool.",
   "competitors": [
    "National PA consultancies (ICF, Hagerty, Thompson) focused on large state/county programs",
    "Boutique and regional FEMA consultants",
    "General grant accountants and one-time consultants who leave the evidence file half-built"
   ],
   "differentiation": "AI-native production engine + senior PA judgment at the chokepoint, sold to the under-served mid-market at fixed reimbursable per-deliverable fees, with contingency legally excluded.",
   "positioning_statement": "For mid-market FEMA PA applicants facing deobligation and hard appeal deadlines, Reoblige is the documentation, recovery & appeals engine that builds the PAPPG-grade evidence file and drafts the appeal — fixed fee, reimbursable — because deobligation is a documentation problem, and documentation at volume is exactly what frontier models do best."
  },
  "assumptions": [
   {
    "id": "fema-public-assistance-recovery-engine-a1",
    "statement": "CA recovery-ops companies will pay a fixed per-disaster event fee for done-for-you documentation production over doing it in-house with software templates.",
    "confidence": "medium",
    "impact_if_wrong": "severe",
    "revisit_trigger": "First 5 discovery calls + Gap Scan conversion — reject if willingness-to-pay signal is absent."
   },
   {
    "id": "fema-public-assistance-recovery-engine-a2",
    "statement": "A current cost record (or professional cost-documentation retest) and a manager-attested known records are obtainable per disaster event inside the intake window.",
    "confidence": "medium",
    "impact_if_wrong": "high",
    "revisit_trigger": "Pilot intake — if more than 2 of 8 disaster events stall on inputs, harden the intake gate and partner path."
   },
   {
    "id": "fema-public-assistance-recovery-engine-a3",
    "statement": "Extraction accuracy on the top cost-documentation-study vendor formats reaches reproject grade after gold-pack calibration.",
    "confidence": "medium",
    "impact_if_wrong": "high",
    "revisit_trigger": "Field-level F1 on gold packs before the Week-5 first reprojects."
   },
   {
    "id": "fema-public-assistance-recovery-engine-a4",
    "statement": "Buyers accept the licensing boundary in writing — analysts draft, the disaster event’s counsel decides legal questions, the owner adopts and distributes.",
    "confidence": "high",
    "impact_if_wrong": "severe",
    "revisit_trigger": "Any prospect who insists we resolve counsel-flag items — decline and log."
   },
   {
    "id": "fema-public-assistance-recovery-engine-a5",
    "statement": "The peak recovery months recovery-year-end concentration is schedulable with retainer priority, batch intake, and capacity-gated rush pricing.",
    "confidence": "medium",
    "impact_if_wrong": "high",
    "revisit_trigger": "Week-8 batch production — median cycle time above 5 business days triggers the capacity plan."
   }
  ],
  "unknowns": [
   {
    "id": "fema-public-assistance-recovery-engine-u1",
    "question": "Which disaster event profiles (variable assessments, phased communities, mixed condo/PD interests) push packs above the price band?",
    "blocks": "Locking list prices after the founding cohort.",
    "resolution_path": "Complexity scoring across the 8-disaster event pilot."
   },
   {
    "id": "fema-public-assistance-recovery-engine-u2",
    "question": "Do managers attest known cost-documentation recordss promptly, or does attestation become the cycle-time bottleneck?",
    "blocks": "The 5-business-day SLA.",
    "resolution_path": "Track stale-balance exceptions per pack through the pilot."
   },
   {
    "id": "fema-public-assistance-recovery-engine-u3",
    "question": "Which cost-documentation-study vendor PDF formats resist table extraction and need manual copy?",
    "blocks": "Day-90 automation targets (65% extract-to-draft).",
    "resolution_path": "Log exotic-format exceptions per vendor; templatize the top 2 formats by Week 10."
   },
   {
    "id": "fema-public-assistance-recovery-engine-u4",
    "question": "Is the completeness guarantee (redo + 50% refund) sufficient risk reversal for firms burned by software templates?",
    "blocks": "Founding-cohort close rate.",
    "resolution_path": "Offer 50%-on-reproject pilot terms and measure objection frequency."
   },
   {
    "id": "fema-public-assistance-recovery-engine-u5",
    "question": "How often is 2 CFR 200(b)(5) affirmative across a real disaster event, and does the insurance-offset add-on attach as modeled?",
    "blocks": "Add-on launch (gated to post-pilot by blueprint rule).",
    "resolution_path": "Count (b)(5)-affirmative packs and add-on interest in the pilot readout."
   }
  ],
  "expert_panel": [
   {
    "role": "Product Strategy",
    "key_concern": "Is the ICP narrow enough to earn a first pilot cohort?",
    "recommendation": "Constrain v1 to CA recovery-ops firms managing 40–400 disaster events; self-managed owners and national megas stay out until the day-90 readout.",
    "dissent": "May under-price total addressable market and slow the disaster event-retainer narrative."
   },
   {
    "role": "Software Architecture",
    "key_concern": "Does the pipeline stay boring enough to run through the peak-recovery peak?",
    "recommendation": "Drive + Airtable + versioned prompts + a coded validator suite; no custom portal before the 20-pack checkpoint.",
    "dissent": "A thin upload portal earlier could cut intake friction on multi-disaster event batches."
   },
   {
    "role": "Frontend / UX",
    "key_concern": "Analysts need a checklist view, not a dashboard.",
    "recommendation": "Field-by-field verification against the cited page with green/yellow/red states and a signed reproject checkbox; pre-highlight low-confidence fields.",
    "dissent": "Airtable interfaces may cap reviewer speed once volume passes the pilot."
   },
   {
    "role": "Backend / Data",
    "key_concern": "Every numeric must carry file-and-page provenance end-to-end.",
    "recommendation": "Store provenance on every extracted table; a required field without a source is a hard exception, never an estimate.",
    "dissent": "Provenance-first storage adds intake latency on exotic PDF formats."
   },
   {
    "role": "AI / ML",
    "key_concern": "Extraction accuracy varies sharply by cost-documentation-study vendor format.",
    "recommendation": "Build gold packs per major vendor format; run field-level F1 regressions before any prompt reproject; keep prompts provider-portable.",
    "dissent": "Gold-pack curation is slow until the pilot supplies real studies."
   },
   {
    "role": "Security",
    "key_concern": "Disaster-event financials are confidential even where they are not statutory PII.",
    "recommendation": "NDA before any intake; least-privilege per-PM/per-disaster event/per-FY folders; no bank-feed scraping; business-tier no-training API terms.",
    "dissent": "Folder-level ACL discipline may feel heavy at pilot scale."
   },
   {
    "role": "Privacy / Compliance",
    "key_concern": "UPL drift — administrative drafting edging into legal conclusions.",
    "recommendation": "Maintain the banned-acts list; make the counsel-flag memo a first-class deliverable; use the decline-and-refer template on lawfulness questions.",
    "dissent": "Strict flagging may frustrate buyers who want one-stop answers."
   },
   {
    "role": "DevOps / Reliability",
    "key_concern": "Seasonal load lands almost entirely in one quarter.",
    "recommendation": "Capacity-gate rush orders, run the retainer priority queue, and freeze SOP changes weekly so nothing lands mid-peak.",
    "dissent": "Weekly SOP freezes slow learning-loop fixes during the season."
   },
   {
    "role": "Data / Analytics",
    "key_concern": "Unit economics must be measured, not asserted.",
    "recommendation": "Time-motion log per step from pack 1; track analyst minutes, rework rate, and per-pack token spend against the blueprint bands.",
    "dissent": "Instrumentation overhead falls on the founder during launch."
   },
   {
    "role": "Accessibility",
    "key_concern": "The authorized representative FAQ must actually read at a grade-8 level.",
    "recommendation": "Enforce reading-level checks on FAQ drafts; WCAG AA on the Gap Scan page and any delivery surface.",
    "dissent": "No material dissent recorded."
   },
   {
    "role": "SEO / Content",
    "key_concern": "AEO pages must cite leginfo primary text, not aggregators.",
    "recommendation": "Publish the ten statute-fluent posts as canonical pages with primary-source citations and change-log timestamps.",
    "dissent": "Content payoff lags the first recovery season."
   },
   {
    "role": "Executive Sponsor",
    "key_concern": "The early-demand trap: eager buyers past the pilot cap.",
    "recommendation": "Hold the 8-disaster event / ≤2-firm cap until the Week-12 readout; no analyst #2 before the 20-pack checkpoint metrics run 4 weeks.",
    "dissent": "Capping demand risks losing founding logos to a slower but hungrier competitor."
   }
  ],
  "strategy": {
   "business_model": "Productized managed service billed per deliverable (Recovery File, Project Worksheet, appeal) or fixed monthly retainer per disaster event; fees scoped to the reimbursable management-cost pool.",
   "revenue_streams": [
    "Per-appeal Deobligation Defense packages ($6K–$18K) and second appeals ($10K–$30K)",
    "Per-project Closeout Documentation Packages ($2.5K–$9K)",
    "Managed Recovery retainers ($4K–$15K/mo per disaster event)"
   ],
   "moat": [
    "Deep PAPPG V5 / 44 CFR 206 / 2 CFR 200 policy-citation knowledge encoded in the engine",
    "A growing corpus of FEMA first/second-appeal decisions for precedent retrieval",
    "A learning loop where every FEMA outcome sharpens gap detection and templates"
   ],
   "gtm": [
    "Free Deobligation-Risk Scan as the lead magnet and qualification trap",
    "Founder-led content answering real applicant objections; answer-engine visibility on PAPPG/appeal queries",
    "Targeted outbound to applicants in freshly declared counties and those holding Determination Memos"
   ],
   "pricing_hypothesis": "Applicants pay $6K–$30K per appeal and $2.5K–$9K per closeout project, low-friction because the fee is reimbursable within the 5% management-cost pool.",
   "kill_criteria": [
    "FEMA reclassifies documentation-preparation fees as unallowable management costs",
    "A rule change lets the national consultancies profitably serve sub-$1M applicants at scale",
    "Appeal win-rates on documented files prove too low to sell a defensible outcome",
    "Frontier-model eligibility drafting cannot reach specialist-review quality at viable cost"
   ]
  },
  "security": {
   "stride": [
    {
     "threat": "Spoofing",
     "scenario": "Attacker attempts to impersonate a reviewer to sign off on a fabricated artifact.",
     "mitigation": "SSO with MFA; reviewer signatures bound to a cryptographic session claim, not a form field."
    },
    {
     "threat": "Tampering",
     "scenario": "Historical evidence entries edited after the fact to hide a bad claim.",
     "mitigation": "Append-only audit log; hash-chained artifact snapshots; diff view on every reviewer surface."
    },
    {
     "threat": "Repudiation",
     "scenario": "Reviewer denies signing off on a delivered artifact.",
     "mitigation": "Signed attestations with server-side timestamp + reviewer identity; export bundle includes signature manifest."
    },
    {
     "threat": "Information Documentation",
     "scenario": "Cross-recipient leak of Regulated-documentation, PII, Internal-audit through shared indices, logs, or prompts.",
     "mitigation": "Recipient-scoped row-level auth; PII scrubbing in logs; retrieval indices partitioned per recipient."
    },
    {
     "threat": "Denial of Service",
     "scenario": "Runaway AI job or export exhausts shared workers.",
     "mitigation": "Per-recipient concurrency + recovery caps; circuit breaker on model calls; degrade-gracefully queue."
    },
    {
     "threat": "Elevation of Privilege",
     "scenario": "Standard user acquires reviewer or admin capability via a workflow shortcut.",
     "mitigation": "Roles stored in a separate table; capability checks server-side; no client-only role checks."
    }
   ],
   "privacy_posture": "Data-minimization by default; per-PM, per-disaster event folder isolation under NDA; owner PII rejected or redacted unless strictly necessary; business-tier no-training API terms; no bank-feed scraping.",
   "compliance_targets": [
    "2 CFR Part 200 (Uniform Guidance) cost, procurement, and audit requirements",
    "Stafford Act §312 anti-duplication (insurance offset)",
    "DHS OIG / Single Audit (2 CFR 200 Subpart F) defensibility"
   ],
   "data_classifications": [
    "Regulated-documentation",
    "PII",
    "Internal-audit"
   ]
  },
  "devops": {
   "ci_cd": "PR → typecheck + unit + snapshot tests → preview deploy → main auto-deploys to a single production region; migrations gated on review.",
   "environments": [
    "local",
    "preview (per-PR)",
    "staging (shared)",
    "production (single region + multi-AZ)"
   ],
   "observability": [
    "Structured logs with recipient + request IDs",
    "RED metrics per workflow",
    "Error tracking with source maps",
    "Model-call spans with cost + latency",
    "Weekly SLO review"
   ],
   "testing_pyramid": [
    "Unit tests on derivation + validation modules",
    "Component tests on reviewer surfaces",
    "Contract tests on integrations",
    "End-to-end smoke test on the intake→signoff→delivery path"
   ],
   "accessibility_tests": [
    "axe-core in CI on reviewer surfaces",
    "Keyboard-only walkthrough per workflow",
    "Prefers-reduced-motion honored"
   ],
   "performance_budget": "p95 workflow latency published per module; artifact-generation cold-path under 30s or shown as background job."
  },
  "accessibility_i18n_ethics": {
   "wcag_target": "AA",
   "locales": [
    "en-US"
   ],
   "rtl_support": false,
   "ethical_risks": [
    "Documentation prepared without human review",
    "Cross-disaster event claim leakage",
    "Disaster-event counsel-facing errors attributed to AI"
   ],
   "ethical_guardrails": [
    "Human reviewer required before the applicant's counsel submission",
    "Per-disaster event prompt + template isolation",
    "AI-usage documentation in documentation metadata where required"
   ]
  },
  "governance": {
   "ownership": [
    {
     "area": "Product + roadmap",
     "owner": "Executive Sponsor"
    },
    {
     "area": "Architecture + platform",
     "owner": "Engineering Lead"
    },
    {
     "area": "Evidence + reviewer workflow",
     "owner": "Named licensed reviewer"
    },
    {
     "area": "Compliance + privacy",
     "owner": "Compliance Lead"
    },
    {
     "area": "Design system",
     "owner": "Design Lead"
    },
    {
     "area": "SEO + content",
     "owner": "Content Lead"
    }
   ],
   "docs_required": [
    "ADR log (checked in)",
    "Owner-action ledger",
    "Evidence register",
    "STRIDE threat model",
    "Runbook: incident, restore, breach notification",
    "Reviewer playbook + signature policy"
   ],
   "naming_conventions": [
    "kebab-case slugs for blueprints and routes",
    "camelCase for TypeScript identifiers",
    "SCREAMING_SNAKE_CASE for environment variables",
    "Verb-first action names (e.g., generate-blueprint-docs)"
   ],
   "change_control": "ADR-per-major-decision; migrations require review; production deploys gated on green CI + owner-action ledger check."
  },
  "risk_register": [
   {
    "id": "fema-public-assistance-recovery-engine-r1",
    "risk": "A reprojectd pack misstates a 2 CFR 200 field (percent funded, projections, or balances)",
    "likelihood": "medium",
    "impact": "severe",
    "mitigation": "Deterministic math checks (V-MATH-PF, V-MATH-5YR) + 100% numeric verification at launch + citation-required rule",
    "contingency": "Redo + 50% refund per the completeness guarantee; correction notice to the recovery-ops firm; root cause coded in the rewrite taxonomy within 7 days",
    "owner": "operations"
   },
   {
    "id": "fema-public-assistance-recovery-engine-r2",
    "risk": "Unauthorized-practice-of-law drift — drafting edges into legal conclusions",
    "likelihood": "low",
    "impact": "severe",
    "mitigation": "Banned-acts list; counsel-flag routing on any assessment-authority or governing-document question",
    "contingency": "Written decline; referral to the applicant's counsel; incident logged and SOP updated",
    "owner": "legal"
   },
   {
    "id": "fema-public-assistance-recovery-engine-r3",
    "risk": "peak recovery months capacity overload breaks the 5-business-day SLA",
    "likelihood": "high",
    "impact": "high",
    "mitigation": "Pilot caps, retainer priority queue, capacity-gated rush pricing",
    "contingency": "Waitlist with dated slots; never quietly extend the SLA",
    "owner": "operations"
   },
   {
    "id": "fema-public-assistance-recovery-engine-r4",
    "risk": "Stale or missing cost record at intake",
    "likelihood": "high",
    "impact": "medium",
    "mitigation": "Intake gate blocks the pack; cost-documentation-study partner referral",
    "contingency": "Slot held 10 business days; pack resumes after the study or update lands",
    "owner": "operations"
   },
   {
    "id": "fema-public-assistance-recovery-engine-r5",
    "risk": "Civil Code amendment invalidates the statute field map",
    "likelihood": "low",
    "impact": "high",
    "mitigation": "Quarterly leginfo diff review of §2 CFR 200–5610; versioned YAML field map",
    "contingency": "Field-map version bump + gold-pack re-validation before the next reproject",
    "owner": "legal"
   },
   {
    "id": "fema-public-assistance-recovery-engine-r6",
    "risk": "Extraction errors on exotic cost-documentation-study PDF formats",
    "likelihood": "medium",
    "impact": "medium",
    "mitigation": "Gold packs per major vendor; manual table copy as the accepted fallback",
    "contingency": "Format flagged at intake; vendor template added to the backlog",
    "owner": "engineering"
   }
  ],
  "roadmap": [
   {
    "phase": "Phase 0 — Foundations + first calls",
    "weeks": "Weeks 1-2",
    "outcomes": [
     "Statute field map (2 CFR 200 items 1–7, the 2 CFR 200 known-records elements) versioned against leginfo text",
     "Gap Scan landing page live with upload intake",
     "40-firm CA recovery-ops outreach list built with project signings noted"
    ],
    "exit_criteria": [
     "5 discovery calls booked",
     "Field map reviewed against current statute text",
     "NDA/MSA templates ready for signature"
    ],
    "kill_criteria": [
     "No discovery calls after two outreach waves",
     "Field map cannot be grounded in current statute text"
    ]
   },
   {
    "phase": "Phase 1 — Engine v0 + first revenue",
    "weeks": "Weeks 3-5",
    "outcomes": [
     "Extraction + PA cost documentation recovery file prompts wired with citation-required outputs",
     "Validator suite (V-803A, V-803B, V-MATH, V-CITE) coded and seeded-omission tested",
     "First 3 founding packs reprojectd with founder reviewing 100% of fields"
    ],
    "exit_criteria": [
     "Validators catch 100% of seeded omissions",
     "At least 2 paid or founding packs in intake",
     "No more than 1 material rewrite across the first 3 packs"
    ],
    "kill_criteria": [
     "Validator escapes on seeded omissions",
     "Founding buyers reject the licensing boundary in writing"
    ]
   },
   {
    "phase": "Phase 2 — Pilot cohort at cap",
    "weeks": "Weeks 6-10",
    "outcomes": [
     "Pilot filled to cap: 8 disaster events across ≤2 recovery-ops firms at founding price",
     "Exception queues (missing study, stale balance, math mismatch) live in the tracker",
     "SOP freeze after the 10-pack hardening"
    ],
    "exit_criteria": [
     "Median cycle time ≤5 business days",
     "Rework below 12% and analyst minutes ≤60 median",
     "Recovery Season Clinic run with ≥15 attendees or ≥3 Gap Scans generated"
    ],
    "kill_criteria": [
     "Fewer than 6 of 8 packs accepted",
     "Material rewrites uncoded or repeating after SOP fixes"
    ]
   },
   {
    "phase": "Phase 3 — Readout + season prep",
    "weeks": "Weeks 11-13",
    "outcomes": [
     "Pilot scorecard: cycle time, rewrite rate, field-error rate, minutes per step, expansion willingness",
     "Disaster-event MSA drafted and pitched to both pilot firms",
     "Gate D red team: seeded \"omit a required line\" tests pre-season"
    ],
    "exit_criteria": [
     "At least 6/8 packs accepted with ≤1 material rewrite each and NPS ≥8",
     "Zero validator escapes in the red team",
     "Go/no-go on scale-up documented"
    ],
    "kill_criteria": [
     "Pilot gates missed — run a second capped cohort, no hiring or expansion",
     "Red-team escapes unresolved before October 1"
    ]
   }
  ],
  "metrics": {
   "north_star": "Analyst-reprojectd, statute-complete packs per week with zero 2 CFR 200 field-defect escapes",
   "leading": [
    "Gap Scans requested → returned per week",
    "Discovery calls booked from the 40-firm list",
    "Packs in intake with green checklists first pass",
    "Median analyst minutes per pack",
    "Counsel-flag rate per pack"
   ],
   "lagging": [
    "Packs reprojectd per season",
    "Material rewrite rate",
    "Retention into the next recovery-year cycle",
    "Gross margin per pack"
   ],
   "guardrails": [
    "2 CFR 200 field-defect escapes = 0",
    "No pack reprojectd without a manager-attested known cost-documentation records",
    "No legal conclusion drafted — 100% routed to the counsel-flag memo",
    "SLA of 5 business days never quietly extended"
   ]
  },
  "executive_review": {
   "consensus": "Ship a thin, source-traced, analyst-gated production desk for CA applicant PA cost documentation packs; cap the pilot at 8 disaster events across ≤2 recovery-ops firms and measure minutes per pack before any hiring.",
   "dissent": "GTM and Operations disagree on launch tempo — GTM wants fall slots filled aggressively; Operations holds the pilot cap until the Week-12 readout to avoid the early-demand trap.",
   "go_no_go": "conditional-go",
   "top_3_risks": [
    "A 2 CFR 200 field defect escaping into a distributed recovery file",
    "UPL drift past the licensing boundary",
    "peak recovery months capacity crunch breaking the SLA"
   ],
   "first_10_steps": [
    "Version the statute field map (2 CFR 200 items 1–7, the 2 CFR 200 known-records elements) against leginfo text",
    "Annotate a sample PA cost documentation recovery file end-to-end with source-trace conventions",
    "Stand up the Gap Scan landing page with upload intake",
    "Build the 40-firm CA recovery-ops outreach list with project signings",
    "Send outbound touch 1 to the first 20 firms",
    "Wire extraction + PA cost documentation recovery file prompts; code validators V-803A/V-803B/V-MATH/V-CITE",
    "Run 2 public sample cost records end-to-end; seed omission tests",
    "Close 2–3 founding packs at $179–$349",
    "Reproject the first 3 packs with the founder reviewing 100% of fields",
    "Log time-motion per step and code every manager rewrite"
   ]
  }
 },
 "project_site": {
  "slug": "fema-public-assistance-recovery-engine",
  "app_name": "Reoblige",
  "archetype": "evidence-desk",
  "archetype_label": "Documentation & appeals desk",
  "reader_role": "recovery coordinator",
  "one_sentence_app": "Reoblige turns scattered disaster cost records into a certification-ready, PAPPG-grade Recovery File — and drafts the appeal — so obligated FEMA dollars survive deobligation.",
  "homepage_sequence": [
   "hero",
   "stat-strip",
   "pain-stakes",
   "deliverables",
   "how-it-works",
   "pricing",
   "proof",
   "faq-compliance"
  ],
  "hero": {
   "frame_label": "Deobligation-Defense Engine",
   "eyebrow": "For mid-market FEMA Public Assistance applicants",
   "interface_title": "Recovery File — status by cost category",
   "primary_panel_title": "Every cost line, mapped and defended",
   "primary_panel_body": "Labor, equipment, materials, contracts, and force-account costs mapped to PAPPG V5 and 2 CFR 200, insurance offset reconciled, gaps FEMA would cite flagged before you certify.",
   "side_panel_title": "Release gate",
   "side_panel_items": [
    "Eligibility mapped to PAPPG V5",
    "Insurance offset reconciled (§312)",
    "Specialist release before certification"
   ],
   "status_metric": "60-day",
   "status_label": "appeal clock tracked from the Determination Memo"
  },
  "language": {
   "problem_heading": "FEMA obligated the money. Keeping it is a documentation problem.",
   "mechanism_heading": "How Reoblige defends your dollars",
   "proof_heading": "What proof will look like",
   "offer_heading": "Fixed, reimbursable fees",
   "objection_heading": "What applicants ask before they start",
   "qualification_heading": "Who Reoblige is built for",
   "cta_close": "Start with a free Deobligation-Risk Scan"
  },
  "modules": [
   {
    "name": "Cost-line engine",
    "job": "Normalize and classify every reimbursable cost against PAPPG V5",
    "artifact": "Canonical cost ledger + eligibility map"
   },
   {
    "name": "Gap scan",
    "job": "Predict what FEMA will cite and fix it first",
    "artifact": "Deobligation-risk report"
   },
   {
    "name": "Appeal drafter",
    "job": "Draft PWs, RFI responses, and first/second appeals with citations",
    "artifact": "Certification-ready Recovery File"
   }
  ],
  "checkpoints": [
   {
    "label": "Eligibility edge cases",
    "pass": "Specialist confirms PAPPG basis for every flagged cost line",
    "fail": "Cost line held with a named owner until resolved"
   },
   {
    "label": "Insurance offset",
    "pass": "§312 duplication reconciled to settlement statements",
    "fail": "File blocked until settlements are provided"
   },
   {
    "label": "Authorized-rep certification",
    "pass": "Applicant official certifies and submits",
    "fail": "Nothing is filed — we never certify"
   }
  ],
  "signature_scene": "A recovery coordinator opens the Recovery File to a completeness checklist that is green across every cost category, with the drafted appeal and its citations attached, days before the 60-day clock expires."
 },
 "ddd": {
  "slug": "fema-public-assistance-recovery-engine",
  "project_name": "FEMA Public Assistance Recovery & Appeals Engine",
  "business_understanding": {
   "summary": "Reoblige — On Reoblige, CA recovery-ops teams stop assembling PA cost documentation recovery files and start rerecovery them: cost records and attested known recordss land at intake, every 2 CFR 200 field maps to a source page, and the Annual PA Cost Documentation Recovery File reprojects only on a named analyst’s signature.",
   "customer_profile": "recovery coordinators, recovery-ops recovery teams, and operations leads",
   "customer_pain": "Recovery-season PA cost documentation recovery file production scattered across email, spreadsheets, and management software; cost-documentation-records knowledge living in one manager’s head; percent-funded mismatches discovered after distribution, when the cure is public and expensive.",
   "paid_outcome": "Reliably delivered, analyst-reprojectd Annual PA Cost Documentation Recovery File — statute-complete, source-traced, and reconstructable on demand.",
   "value_creation": "AI compresses document extraction + drafting; humans own the reproject decision, the counsel flags, and the customer relationship.",
   "why_ai_native": "The extraction + deterministic-validation + analyst-reproject loop is only economical with AI doing the document work; the human reproject chokepoint is what keeps it defensible.",
   "operational_risks": [
    "Reviewer bottleneck",
    "Prompt injection via customer inputs",
    "Cross-recipient retrieval leak",
    "Premature public claim while owner actions open",
    "Silent delivery failure"
   ],
   "assumptions": [
    "The target audience will pay for evidence-linked, human-reviewed outputs over unverified AI generation.",
    "The workflow can be reconstructed from an owner-supplied evidence pack within one week per design partner.",
    "The vertical tolerates AI-assisted drafts when human review is explicit and audit-traceable.",
    "Single-recipient per customer is not required for the first cohort — logical isolation with row-level auth is acceptable.",
    "Manifest-backed blueprint reflects real customer workflow, not a synthetic scenario."
   ],
   "validation_questions": [
    "Which specific licensed professional will sign off on outbound artifacts?",
    "Which disaster event(s) are in scope for launch?",
    "What is the actual willingness-to-pay?",
    "Which existing systems must this integrate with day-one?",
    "Is there a data-residency or on-prem constraint?"
   ]
  },
  "domain_discovery": {
   "actors": [
    {
     "actor": "Customer operator",
     "role": "recovery coordinators, recovery-ops recovery teams, and operations leads",
     "goals": [
      "Deliver recovery files on schedule",
      "Reduce cycle time without losing defensibility"
     ],
     "decisions": [
      "Submit intake",
      "Accept or revise draft",
      "Approve outbound delivery"
     ],
     "pain_points": [
      "Scattered evidence across tools",
      "Manual re-typing",
      "Reviewer bottleneck"
     ]
    },
    {
     "actor": "Documentation analyst",
     "role": "Signs and takes accountability for outbound artifacts",
     "goals": [
      "Sign only what is defensible",
      "Keep audit trail intact"
     ],
     "decisions": [
      "Approve / reject / request revisions",
      "Escalate on ambiguity"
     ],
     "pain_points": [
      "Incomplete evidence",
      "Ambiguous AI outputs",
      "No visible source-of-truth"
     ]
    },
    {
     "actor": "Disaster-event counsel",
     "role": "Inspects artifacts on demand",
     "goals": [
      "Reconstruct decisions from evidence"
     ],
     "decisions": [
      "Accept, question, or reject the documentation"
     ],
     "pain_points": [
      "Missing citations",
      "Non-reconstructable state"
     ]
    },
    {
     "actor": "AI Orchestrator",
     "role": "Bounded AI agent that drafts + validates",
     "goals": [
      "Produce grounded, cited drafts",
      "Escalate on low confidence"
     ],
     "decisions": [
      "Draft vs escalate",
      "Which retrieval sources to cite"
     ],
     "pain_points": [
      "Ambiguous intake",
      "Sparse evidence"
     ]
    },
    {
     "actor": "Platform admin",
     "role": "Runs the recipient, manages users + integrations",
     "goals": [
      "Keep the system safe and observable"
     ],
     "decisions": [
      "Provision users",
      "Rotate secrets"
     ],
     "pain_points": [
      "Change management across recipients"
     ]
    }
   ],
   "glossary": [
    {
     "term": "pack order",
     "definition": "The unit of work a customer brings in for Reoblige to process.",
     "used_by": "Customer, Operator",
     "context": "Sales & Intake",
     "example": "\"Open a pack order for the December-FYE disaster event\"",
     "notes": "Do not confuse with 'engagement' in Billing (contract term)."
    },
    {
     "term": "control evidence",
     "definition": "Cited fact linked to a source, attached to a claim inside the recovery file.",
     "used_by": "Reviewer, Auditor",
     "context": "Service Fulfillment",
     "example": "\"Every rate quoted must carry control evidence\"",
     "notes": "Distinct from 'note' (internal, non-cited)."
    },
    {
     "term": "recovery file",
     "definition": "The reviewer-signed deliverable Reoblige produces.",
     "used_by": "Customer, Reviewer, Auditor",
     "context": "Client Delivery",
     "example": "\"Ship the recovery file once the reviewer signs\"",
     "notes": "Immutable once signed; corrections go through Retraction workflow."
    },
    {
     "term": "Reviewer signoff",
     "definition": "Cryptographically signed attestation by the licensed reviewer that the artifact is defensible.",
     "used_by": "Reviewer, Platform",
     "context": "Quality Assurance",
     "example": "\"Signoff bound to session + timestamp\"",
     "notes": "Not the same as customer approval."
    },
    {
     "term": "Owner action",
     "definition": "Discrete fact the business owner must supply before an artifact can be publicly claimed.",
     "used_by": "Owner, Platform",
     "context": "Compliance & Governance",
     "example": "\"Entity name, disaster event, privacy inbox\"",
     "notes": "Blocks reproject when open."
    },
    {
     "term": "Retraction",
     "definition": "Explicit correction of a previously delivered artifact with the applicant's counsel-facing notification.",
     "used_by": "Reviewer, Legal, Customer",
     "context": "Client Delivery",
     "example": "\"File a retraction within 24h\"",
     "notes": "Rare, but must always be possible."
    },
    {
     "term": "Confidence score",
     "definition": "AI-assigned probability that a drafted claim is grounded in retrieved evidence.",
     "used_by": "AI Orchestrator, Reviewer",
     "context": "AI Orchestration",
     "example": "\"Below 0.7 → escalate to reviewer\"",
     "notes": "Not a legal or clinical confidence measure."
    },
    {
     "term": "Escalation",
     "definition": "Automatic routing of a case from AI drafting to a named human role.",
     "used_by": "AI Orchestrator, Reviewer",
     "context": "AI Orchestration ↔ Human Review",
     "example": "\"Escalate on ambiguous disaster event\"",
     "notes": "Escalation ≠ rejection; it is a hand-off."
    }
   ],
   "decisions": [
    {
     "decision": "Accept intake",
     "who": "Sales & Intake context (rule + operator override)",
     "inputs": [
      "Customer identity",
      "Scope statement",
      "pack order completeness"
     ],
     "rule": "Reject if scope statement missing or customer not on-boarded",
     "output": "pack order accepted event",
     "risk": "Accepting out-of-scope work degrades reviewer trust."
    },
    {
     "decision": "Draft vs escalate",
     "who": "AI Orchestrator",
     "inputs": [
      "control evidence coverage",
      "Confidence score",
      "Prior-similar-case pattern"
     ],
     "rule": "Escalate below confidence threshold or on ambiguous disaster event",
     "output": "Draft-ready OR escalation event",
     "risk": "Silent low-confidence drafts erode reviewer trust."
    },
    {
     "decision": "Sign the recovery file",
     "who": "Documentation analyst",
     "inputs": [
      "Draft",
      "Full evidence trail",
      "Prior reviewer comments"
     ],
     "rule": "Sign only if all claims cite evidence AND scope matches engagement",
     "output": "Reviewer-signed event",
     "risk": "Over-broad signoff creates malpractice exposure."
    },
    {
     "decision": "Reproject publicly",
     "who": "Compliance & Governance",
     "inputs": [
      "Owner-action ledger status",
      "Evidence closure",
      "Legal review flag"
     ],
     "rule": "Blocked if any owner-action open OR unresolved reproject-blocker evidence",
     "output": "Public-reproject event OR blocked-reproject event",
     "risk": "Premature public claims are unretractable in perception."
    },
    {
     "decision": "Retract delivered artifact",
     "who": "Legal + Documentation analyst",
     "inputs": [
      "Newly discovered fact",
      "Impact assessment"
     ],
     "rule": "Retract if any signed claim is materially wrong OR unsupported by evidence",
     "output": "Retraction event + customer notification",
     "risk": "Delayed retraction compounds legal exposure."
    }
   ],
   "events": [
    {
     "event": "packOrderAccepted",
     "meaning": "Work is now committed to fulfillment",
     "trigger": "Operator or auto-rule accepts intake",
     "downstream": [
      "Onboarding kicked off",
      "AI orchestrator scheduled"
     ]
    },
    {
     "event": "EvidenceCollected",
     "meaning": "Enough evidence exists to draft",
     "trigger": "Retrieval + upload passes coverage rule",
     "downstream": [
      "Drafting authorized"
     ]
    },
    {
     "event": "DraftReady",
     "meaning": "AI draft with cited evidence is available for reviewer",
     "trigger": "AI orchestrator finishes drafting run",
     "downstream": [
      "Reviewer notification"
     ]
    },
    {
     "event": "EscalationRaised",
     "meaning": "AI could not complete safely",
     "trigger": "Confidence below threshold OR ambiguous input",
     "downstream": [
      "Reviewer queue"
     ]
    },
    {
     "event": "ReviewerSigned",
     "meaning": "Documentation analyst took accountability",
     "trigger": "Reviewer signature captured",
     "downstream": [
      "Delivery authorized",
      "Audit-log snapshot"
     ]
    },
    {
     "event": "ArtifactDelivered",
     "meaning": "recovery file handed to the customer / downstream party",
     "trigger": "Delivery adapter confirms transmit",
     "downstream": [
      "Billing event",
      "Customer notification"
     ]
    },
    {
     "event": "OwnerActionResolved",
     "meaning": "A blocking owner-supplied fact is now on file",
     "trigger": "Owner updates the ledger",
     "downstream": [
      "Reproject-decision recomputation"
     ]
    },
    {
     "event": "RetractionFiled",
     "meaning": "A delivered artifact is formally withdrawn or corrected",
     "trigger": "Reviewer + legal jointly file",
     "downstream": [
      "Customer notification",
      "Audit-log append"
     ]
    }
   ]
  },
  "subdomains": [
   {
    "name": "Service Fulfillment (evidence-linked drafting + review)",
    "type": "core",
    "description": "The end-to-end path from pack order to Documentation analyst-signed recovery file, with every claim cited.",
    "reason": "This is what customers pay for and what counsel and owners inspect.",
    "business_value": "Direct revenue and legal defensibility.",
    "recommendation": "build",
    "ai_involvement": "high",
    "human_involvement": "high",
    "risks": [
     "Hallucinated claims",
     "Reviewer bottleneck",
     "Un-reconstructable audit trail"
    ],
    "validation_questions": [
     "Can the reviewer sign in <5 business days?",
     "Can we reconstruct any past artifact on demand?"
    ]
   },
   {
    "name": "AI Orchestration (bounded agents + retrieval)",
    "type": "core",
    "description": "The bounded AI layer that drafts, cites, validates, and escalates — never authors final decisions unassisted.",
    "reason": "The AI-native competitive edge lives here; misuse here creates every high-severity risk.",
    "business_value": "Cycle-time and margin advantage.",
    "recommendation": "build",
    "ai_involvement": "high",
    "human_involvement": "medium",
    "risks": [
     "Prompt injection",
     "Grounding drift",
     "Silent low-confidence output"
    ],
    "validation_questions": [
     "What is the acceptance rate of AI drafts by reviewers?",
     "What percent of runs escalate correctly?"
    ]
   },
   {
    "name": "Quality Assurance (reviewer signoff + retraction)",
    "type": "core",
    "description": "Documentation analyst workflow, signature capture, retraction workflow, and audit-log snapshots.",
    "reason": "Signoff is the trust primitive of the whole business.",
    "business_value": "Defensibility; premium pricing.",
    "recommendation": "build",
    "ai_involvement": "medium",
    "human_involvement": "high",
    "risks": [
     "Signature spoofing",
     "Repudiation",
     "Delayed retraction"
    ],
    "validation_questions": [
     "Is every signature cryptographically bound?",
     "Can we replay any signoff on demand?"
    ]
   },
   {
    "name": "Sales & Intake",
    "type": "supporting",
    "description": "Lead capture through accepted engagement + scope statement.",
    "reason": "Feeds Fulfillment; not the differentiator, but if broken, nothing else runs.",
    "business_value": "Feeds pipeline.",
    "recommendation": "build",
    "ai_involvement": "medium",
    "human_involvement": "high",
    "risks": [
     "Out-of-scope acceptance"
    ],
    "validation_questions": [
     "Do we reject work outside the ICP?"
    ]
   },
   {
    "name": "Client Onboarding & Profile",
    "type": "supporting",
    "description": "Recipient provisioning, contact matrix, evidence-pack import, engagement letter.",
    "reason": "One-time high-touch step per customer.",
    "business_value": "Reduces first-artifact time.",
    "recommendation": "build",
    "ai_involvement": "low",
    "human_involvement": "high",
    "risks": [
     "Contract terms not represented in the system"
    ],
    "validation_questions": [
     "Is the reviewer named per recipient?"
    ]
   },
   {
    "name": "Client Delivery & Success",
    "type": "supporting",
    "description": "Delivery adapter, customer portal, revision loop, renewal signal.",
    "reason": "Customer-visible surface; drives retention.",
    "business_value": "Retention.",
    "recommendation": "build",
    "ai_involvement": "low",
    "human_involvement": "medium",
    "risks": [
     "Delivery failure not surfaced"
    ],
    "validation_questions": [
     "Do we alert the customer within 1h of any delivery failure?"
    ]
   },
   {
    "name": "Compliance & Governance",
    "type": "supporting",
    "description": "Owner-action ledger, reproject-decision engine, policy attestation, DSAR / retraction runbooks.",
    "reason": "Cross-cuts every context; owns 'can we publicly claim this?'.",
    "business_value": "Prevents category-level failure.",
    "recommendation": "build",
    "ai_involvement": "low",
    "human_involvement": "high",
    "risks": [
     "Premature public claim"
    ],
    "validation_questions": [
     "Are all owner actions closed before public reproject?"
    ]
   },
   {
    "name": "Billing & Revenue",
    "type": "generic",
    "description": "Subscription + usage-based invoicing, dunning, revenue reporting.",
    "reason": "Solved category; do not build.",
    "business_value": "Cash collection.",
    "recommendation": "buy",
    "ai_involvement": "low",
    "human_involvement": "low",
    "risks": [
     "Tax per-disaster event errors"
    ],
    "validation_questions": [
     "Is Stripe Tax sufficient for the launch disaster events?"
    ]
   },
   {
    "name": "Identity & Access",
    "type": "generic",
    "description": "SSO, MFA, RBAC, session management.",
    "reason": "Solved category.",
    "business_value": "Table stakes.",
    "recommendation": "integrate",
    "ai_involvement": "low",
    "human_involvement": "low",
    "risks": [
     "Role escalation"
    ],
    "validation_questions": [
     "Are roles stored in a dedicated table?"
    ]
   },
   {
    "name": "Knowledge Base & Retrieval",
    "type": "supporting",
    "description": "Per-recipient retrieval indices, source-of-truth documents, prompt library.",
    "reason": "Feeds AI Orchestration; poor retrieval = poor drafts.",
    "business_value": "Drives AI quality.",
    "recommendation": "build",
    "ai_involvement": "high",
    "human_involvement": "medium",
    "risks": [
     "Cross-recipient leakage",
     "Stale sources"
    ],
    "validation_questions": [
     "Is retrieval partitioned per recipient?"
    ]
   },
   {
    "name": "Analytics & Reporting",
    "type": "supporting",
    "description": "Activation, cycle time, acceptance rate, reviewer load, outcome reports.",
    "reason": "Drives every operational decision.",
    "business_value": "Feedback loop.",
    "recommendation": "build",
    "ai_involvement": "low",
    "human_involvement": "low",
    "risks": [
     "Vanity metrics"
    ],
    "validation_questions": [
     "Is the north-star wired?"
    ]
   },
   {
    "name": "External Integrations (Anti-Corruption Layer)",
    "type": "supporting",
    "description": "Adapters to recovery-ops management software, cost-documentation-study vendor formats, Airtable intake tracker and other tools with translation to internal domain terms.",
    "reason": "External schemas must never leak into the core.",
    "business_value": "Enables integration without corrupting the model.",
    "recommendation": "build",
    "ai_involvement": "low",
    "human_involvement": "medium",
    "risks": [
     "Silent schema drift"
    ],
    "validation_questions": [
     "Do all external calls pass through an ACL translator?"
    ]
   }
  ],
  "core_domain_analysis": {
   "primary_core": "Service Fulfillment (evidence-linked drafting + review)",
   "secondary_cores": [
    "AI Orchestration (bounded agents + retrieval)",
    "Quality Assurance (reviewer signoff + retraction)"
   ],
   "supporting_may_become_core": [
    "Knowledge Base & Retrieval (as vertical corpora accumulate)",
    "Compliance & Governance (as the applicant's counsel interactions increase)"
   ],
   "generic_do_not_distract": [
    "Billing & Revenue",
    "Identity & Access"
   ],
   "rationale": "The paid outcome (reviewer-signed, evidence-linked artifact) lives in Fulfillment, but its defensibility depends on AI Orchestration + QA behaving correctly. Treat all three as core; do not dilute engineering time on generic subdomains."
  },
  "bounded_contexts": [
   {
    "name": "Service Fulfillment",
    "purpose": "Turn accepted pack orders into reviewer-signed recovery files.",
    "subdomain": "Service Fulfillment (core)",
    "type": "core",
    "owned_language": [
     "pack order",
     "control evidence",
     "recovery file",
     "Draft",
     "Escalation",
     "Signoff"
    ],
    "owns": [
     "pack order lifecycle",
     "Draft state",
     "Evidence links",
     "Delivery recovery file composition"
    ],
    "does_not_own": [
     "Reviewer identity",
     "Billing",
     "Public claim decision"
    ],
    "primary_actors": [
     "Customer operator",
     "AI Orchestrator",
     "Documentation analyst"
    ],
    "entities": [
     "pack order",
     "Draft",
     "recovery file",
     "Delivery"
    ],
    "value_objects": [
     "Confidence score",
     "Evidence citation",
     "Delivery address"
    ],
    "aggregates": [
     "packOrderAggregate",
     "CompletenessPackAggregate"
    ],
    "domain_services": [
     "Draft composer",
     "Delivery adapter"
    ],
    "application_services": [
     "OpenPackOrder",
     "RequestDraft",
     "AttachEvidence",
     "RequestSignoff",
     "DeliverCompletenessPack"
    ],
    "commands": [
     "OpenIntake",
     "AttachEvidence",
     "RequestDraft",
     "SubmitForSignoff",
     "DeliverArtifact"
    ],
    "domain_events": [
     "PackOrderAccepted",
     "EvidenceCollected",
     "DraftReady",
     "ArtifactSigned",
     "ArtifactDelivered"
    ],
    "policies": [
     "Auto-request signoff when evidence coverage complete",
     "Auto-block delivery until signoff received"
    ],
    "specifications": [
     "EvidenceCoverageSpec",
     "DeliverabilitySpec"
    ],
    "invariants": [
     "A recovery file cannot be delivered without a valid Reviewer signoff",
     "Every claim in a delivered artifact cites at least one evidence item"
    ],
    "ai_agents": [
     "Drafter Agent"
    ],
    "human_roles": [
     "Customer operator",
     "Documentation analyst"
    ],
    "data_owned": [
     "pack order",
     "Draft",
     "recovery file",
     "Delivery"
    ],
    "inputs": [
     "Intake payload",
     "Uploaded evidence",
     "Retrieval hits"
    ],
    "outputs": [
     "Signed artifact recovery file",
     "Delivery confirmation"
    ],
    "external_integrations": [
     "PM management software",
     "cost-documentation-study vendor formats"
    ],
    "risks": [
     "Un-cited claim slips into delivery",
     "Delivery adapter fails silently"
    ],
    "interfaces": [
     "→ Quality Assurance (RequestSignoff)",
     "→ Client Delivery (ArtifactDelivered)",
     "← AI Orchestration (DraftProduced)"
    ]
   },
   {
    "name": "AI Orchestration",
    "purpose": "Run bounded AI agents that draft, validate, cite, and escalate.",
    "subdomain": "AI Orchestration (core)",
    "type": "core",
    "owned_language": [
     "Prompt version",
     "Confidence score",
     "Escalation",
     "Retrieval hit"
    ],
    "owns": [
     "Prompt registry",
     "Agent run log",
     "Confidence thresholds"
    ],
    "does_not_own": [
     "Evidence sourcing",
     "Reviewer signature",
     "Business decisions"
    ],
    "primary_actors": [
     "AI Orchestrator",
     "Ops (prompt owner)"
    ],
    "entities": [
     "AgentRun",
     "PromptVersion",
     "RetrievalHit"
    ],
    "value_objects": [
     "Confidence score",
     "Token recovery",
     "Model cost"
    ],
    "aggregates": [
     "AgentRunAggregate",
     "PromptRegistryAggregate"
    ],
    "domain_services": [
     "Retrieval router",
     "Output validator",
     "Escalation router"
    ],
    "application_services": [
     "StartAgentRun",
     "ValidateOutput",
     "PublishPromptVersion"
    ],
    "commands": [
     "StartAgentRun",
     "PublishPromptVersion",
     "SetConfidenceThreshold"
    ],
    "domain_events": [
     "DraftProduced",
     "EscalationRaised",
     "PromptVersionPublished"
    ],
    "policies": [
     "Escalate on confidence < threshold",
     "Never call model with cross-recipient retrieval context",
     "Reject output failing structured-output validator"
    ],
    "specifications": [
     "GroundedOutputSpec",
     "TokenBudgetSpec"
    ],
    "invariants": [
     "No AI output leaves this context without passing OutputValidator",
     "Prompt versions are immutable once published"
    ],
    "ai_agents": [
     "Drafter Agent",
     "Classifier Agent",
     "Evaluator Agent"
    ],
    "human_roles": [
     "Prompt owner (Ops)"
    ],
    "data_owned": [
     "Prompt registry",
     "Agent run logs",
     "Confidence thresholds"
    ],
    "inputs": [
     "Intake context",
     "Retrieval hits",
     "Prompt version"
    ],
    "outputs": [
     "Draft payload",
     "Escalation event",
     "Run trace"
    ],
    "external_integrations": [
     "frontier LLM API (portable)",
     "Retrieval index"
    ],
    "risks": [
     "Prompt injection via customer input",
     "Retrieval leakage across recipients",
     "Silent hallucination"
    ],
    "interfaces": [
     "→ Service Fulfillment (DraftProduced)",
     "→ Quality Assurance (EscalationRaised)",
     "← Knowledge Base (RetrievalHit)"
    ]
   },
   {
    "name": "Quality Assurance",
    "purpose": "Reviewer workflow, signature capture, retraction workflow, audit-log snapshots.",
    "subdomain": "Quality Assurance (core)",
    "type": "core",
    "owned_language": [
     "Signoff",
     "Retraction",
     "Reviewer session"
    ],
    "owns": [
     "Signature log",
     "Reviewer queue",
     "Retraction workflow"
    ],
    "does_not_own": [
     "recovery file content",
     "Public reproject decision"
    ],
    "primary_actors": [
     "Documentation analyst",
     "Legal"
    ],
    "entities": [
     "Signoff",
     "Retraction",
     "ReviewerSession"
    ],
    "value_objects": [
     "Signature manifest",
     "Retraction reason"
    ],
    "aggregates": [
     "SignoffAggregate",
     "RetractionAggregate"
    ],
    "domain_services": [
     "Signature service",
     "Retraction service"
    ],
    "application_services": [
     "ApproveArtifact",
     "RejectArtifact",
     "FileRetraction"
    ],
    "commands": [
     "ApproveArtifact",
     "RejectArtifact",
     "FileRetraction"
    ],
    "domain_events": [
     "ArtifactSigned",
     "ArtifactRejected",
     "RetractionFiled"
    ],
    "policies": [
     "Only Documentation analyst may sign",
     "Retraction requires legal co-signer"
    ],
    "specifications": [
     "ReviewerAuthoritySpec",
     "RetractionPreconditionsSpec"
    ],
    "invariants": [
     "A signature is bound to a live authenticated session, not a form field",
     "Signed artifacts are immutable; corrections go through Retraction"
    ],
    "ai_agents": [],
    "human_roles": [
     "Documentation analyst",
     "Legal"
    ],
    "data_owned": [
     "Signatures",
     "Retractions",
     "Reviewer sessions"
    ],
    "inputs": [
     "Draft ready",
     "Escalation payload"
    ],
    "outputs": [
     "Signoff event",
     "Retraction event"
    ],
    "external_integrations": [
     "IdP (Okta / Google)"
    ],
    "risks": [
     "Signature spoofing",
     "Repudiation"
    ],
    "interfaces": [
     "→ Service Fulfillment (ArtifactSigned)",
     "→ Compliance & Governance (RetractionFiled)"
    ]
   },
   {
    "name": "Compliance & Governance",
    "purpose": "Own the reproject decision, owner-action ledger, DSAR + retraction runbooks.",
    "subdomain": "Compliance & Governance (supporting)",
    "type": "supporting",
    "owned_language": [
     "Owner action",
     "Reproject decision",
     "DSAR"
    ],
    "owns": [
     "Owner-action ledger",
     "Reproject-decision policy",
     "DSAR queue"
    ],
    "does_not_own": [
     "recovery file content",
     "Reviewer identity"
    ],
    "primary_actors": [
     "Business owner",
     "Legal",
     "Documentation analyst"
    ],
    "entities": [
     "OwnerAction",
     "ReprojectDecision",
     "DSARRequest"
    ],
    "value_objects": [
     "Blocker reason",
     "Disaster-event"
    ],
    "aggregates": [
     "OwnerActionLedgerAggregate",
     "ReprojectDecisionAggregate"
    ],
    "domain_services": [
     "Reproject-decision engine",
     "DSAR fulfillment service"
    ],
    "application_services": [
     "ResolveOwnerAction",
     "RecomputeReprojectDecision",
     "ProcessDSAR"
    ],
    "commands": [
     "ResolveOwnerAction",
     "RaiseOwnerAction",
     "ProcessDSAR"
    ],
    "domain_events": [
     "OwnerActionResolved",
     "ReprojectDecisionChanged",
     "DSARFulfilled"
    ],
    "policies": [
     "Block public reproject while any owner action open",
     "DSAR SLA 30 days"
    ],
    "specifications": [
     "ReprojectReadinessSpec",
     "DSARSpec"
    ],
    "invariants": [
     "Reproject cannot flip to 'ready' with open blocking owner actions",
     "Every DSAR is auditable end-to-end"
    ],
    "ai_agents": [],
    "human_roles": [
     "Business owner",
     "Legal"
    ],
    "data_owned": [
     "Owner-action ledger",
     "Reproject decisions",
     "DSAR queue"
    ],
    "inputs": [
     "Owner input",
     "Legal review outcome"
    ],
    "outputs": [
     "Reproject-decision event",
     "DSAR confirmation"
    ],
    "external_integrations": [
     "Email inbox"
    ],
    "risks": [
     "Public reproject while blocker open"
    ],
    "interfaces": [
     "← Service Fulfillment",
     "← Quality Assurance (RetractionFiled)"
    ]
   },
   {
    "name": "Sales & Intake",
    "purpose": "Lead → qualified engagement → accepted intake.",
    "subdomain": "Sales & Intake (supporting)",
    "type": "supporting",
    "owned_language": [
     "Lead",
     "Engagement",
     "Scope statement"
    ],
    "owns": [
     "Lead pipeline",
     "Engagement letter",
     "Scope statement"
    ],
    "does_not_own": [
     "Fulfillment",
     "Billing"
    ],
    "primary_actors": [
     "Owner",
     "Customer"
    ],
    "entities": [
     "Lead",
     "Engagement"
    ],
    "value_objects": [
     "Scope statement",
     "Pricing offer"
    ],
    "aggregates": [
     "EngagementAggregate"
    ],
    "domain_services": [
     "Scope-fit evaluator"
    ],
    "application_services": [
     "QualifyLead",
     "AcceptEngagement"
    ],
    "commands": [
     "QualifyLead",
     "AcceptEngagement"
    ],
    "domain_events": [
     "EngagementAccepted"
    ],
    "policies": [
     "Reject out-of-ICP engagement",
     "Engagement letter required before intake"
    ],
    "specifications": [
     "ScopeFitSpec"
    ],
    "invariants": [
     "Cannot open an intake without an accepted engagement"
    ],
    "ai_agents": [
     "Qualifier Copilot (assist only)"
    ],
    "human_roles": [
     "Owner",
     "Sales lead"
    ],
    "data_owned": [
     "Leads",
     "Engagements"
    ],
    "inputs": [
     "Lead form",
     "Discovery notes"
    ],
    "outputs": [
     "Accepted engagement event"
    ],
    "external_integrations": [
     "CRM",
     "Email inbox"
    ],
    "risks": [
     "Accepting out-of-scope engagement"
    ],
    "interfaces": [
     "→ Client Onboarding",
     "→ Service Fulfillment (intake enablement)"
    ]
   },
   {
    "name": "Client Onboarding & Profile",
    "purpose": "Provision recipient, capture reviewer identity, import evidence pack.",
    "subdomain": "Client Onboarding & Profile (supporting)",
    "type": "supporting",
    "owned_language": [
     "Recipient",
     "Reviewer identity",
     "Evidence pack"
    ],
    "owns": [
     "Recipient provisioning",
     "Reviewer identity record",
     "Evidence pack import"
    ],
    "does_not_own": [
     "Signature capture",
     "Delivery"
    ],
    "primary_actors": [
     "Onboarding lead",
     "Customer admin"
    ],
    "entities": [
     "Recipient",
     "ReviewerIdentity",
     "EvidencePackImport"
    ],
    "value_objects": [
     "Contact matrix",
     "Disaster-event set"
    ],
    "aggregates": [
     "RecipientAggregate"
    ],
    "domain_services": [
     "Recipient provisioner"
    ],
    "application_services": [
     "ProvisionRecipient",
     "RegisterReviewer",
     "ImportEvidencePack"
    ],
    "commands": [
     "ProvisionRecipient",
     "RegisterReviewer",
     "ImportEvidencePack"
    ],
    "domain_events": [
     "RecipientProvisioned",
     "ReviewerRegistered"
    ],
    "policies": [
     "No fulfillment starts until a Reviewer is registered per recipient"
    ],
    "specifications": [
     "ReviewerCredentialSpec"
    ],
    "invariants": [
     "Every recipient has at least one named reviewer with a valid credential on file"
    ],
    "ai_agents": [],
    "human_roles": [
     "Onboarding lead"
    ],
    "data_owned": [
     "Recipients",
     "Reviewer identities",
     "Evidence pack imports"
    ],
    "inputs": [
     "Engagement",
     "Customer-supplied evidence pack"
    ],
    "outputs": [
     "Provisioned recipient"
    ],
    "external_integrations": [
     "IdP",
     "Google Drive / S3"
    ],
    "risks": [
     "Reviewer credential expired"
    ],
    "interfaces": [
     "→ Service Fulfillment"
    ]
   },
   {
    "name": "Client Delivery & Success",
    "purpose": "Deliver signed artifacts, own the customer surface, drive renewal.",
    "subdomain": "Client Delivery & Success (supporting)",
    "type": "supporting",
    "owned_language": [
     "Delivery",
     "Revision request",
     "Renewal signal"
    ],
    "owns": [
     "Customer portal",
     "Delivery log",
     "Revision workflow"
    ],
    "does_not_own": [
     "Signed content",
     "Billing"
    ],
    "primary_actors": [
     "Customer operator",
     "Success lead"
    ],
    "entities": [
     "DeliveryReceipt",
     "RevisionRequest"
    ],
    "value_objects": [
     "Delivery method",
     "NPS signal"
    ],
    "aggregates": [
     "DeliveryAggregate"
    ],
    "domain_services": [
     "Delivery adapter"
    ],
    "application_services": [
     "ConfirmDelivery",
     "RecordRevisionRequest"
    ],
    "commands": [
     "ConfirmDelivery",
     "RecordRevisionRequest"
    ],
    "domain_events": [
     "DeliveryConfirmed",
     "RevisionRequested"
    ],
    "policies": [
     "Alert customer within 1h of any delivery failure"
    ],
    "specifications": [
     "DeliveryAcknowledgmentSpec"
    ],
    "invariants": [
     "Every DeliveryConfirmed has a linked Signoff"
    ],
    "ai_agents": [
     "Success Copilot (assist only)"
    ],
    "human_roles": [
     "Success lead"
    ],
    "data_owned": [
     "Deliveries",
     "Revision requests"
    ],
    "inputs": [
     "Signed artifact",
     "Customer feedback"
    ],
    "outputs": [
     "Delivery confirmation",
     "Revision request"
    ],
    "external_integrations": [
     "Email",
     "Customer portal"
    ],
    "risks": [
     "Silent delivery failure"
    ],
    "interfaces": [
     "← Service Fulfillment",
     "→ Billing"
    ]
   },
   {
    "name": "Knowledge Base & Retrieval",
    "purpose": "Own per-recipient retrieval indices, source-of-truth documents, prompt library refs.",
    "subdomain": "Knowledge Base & Retrieval (supporting)",
    "type": "supporting",
    "owned_language": [
     "Source document",
     "Retrieval index",
     "Chunk"
    ],
    "owns": [
     "Source docs",
     "Retrieval indices",
     "Chunk metadata"
    ],
    "does_not_own": [
     "Prompt versions",
     "Model calls"
    ],
    "primary_actors": [
     "Knowledge ops"
    ],
    "entities": [
     "SourceDoc",
     "IndexShard"
    ],
    "value_objects": [
     "Chunk",
     "SourceCitation"
    ],
    "aggregates": [
     "SourceDocAggregate",
     "IndexShardAggregate"
    ],
    "domain_services": [
     "Ingestion pipeline",
     "Reindex service"
    ],
    "application_services": [
     "IngestDoc",
     "Reindex",
     "PurgeSource"
    ],
    "commands": [
     "IngestDoc",
     "Reindex",
     "PurgeSource"
    ],
    "domain_events": [
     "DocIngested",
     "IndexRebuilt"
    ],
    "policies": [
     "Retrieval indices partitioned per recipient",
     "Purge cascades to indices within SLA"
    ],
    "specifications": [
     "RecipientIsolationSpec"
    ],
    "invariants": [
     "A retrieval call is always scoped to a single recipient partition"
    ],
    "ai_agents": [],
    "human_roles": [
     "Knowledge ops"
    ],
    "data_owned": [
     "Source docs",
     "Indices"
    ],
    "inputs": [
     "Uploaded docs",
     "External source pulls"
    ],
    "outputs": [
     "Retrieval hits with citations"
    ],
    "external_integrations": [
     "Blob storage",
     "Search API"
    ],
    "risks": [
     "Cross-recipient retrieval leak",
     "Stale index"
    ],
    "interfaces": [
     "→ AI Orchestration"
    ]
   },
   {
    "name": "Billing & Revenue",
    "purpose": "Invoicing, subscription management, dunning, revenue reporting.",
    "subdomain": "Billing (generic)",
    "type": "generic",
    "owned_language": [
     "Invoice",
     "Subscription",
     "Usage record"
    ],
    "owns": [
     "Invoices",
     "Subscriptions",
     "Usage records"
    ],
    "does_not_own": [
     "Fulfillment",
     "Signoff"
    ],
    "primary_actors": [
     "Finance",
     "Customer admin"
    ],
    "entities": [
     "Subscription",
     "Invoice",
     "UsageRecord"
    ],
    "value_objects": [
     "Line item",
     "Tax disaster event"
    ],
    "aggregates": [
     "SubscriptionAggregate"
    ],
    "domain_services": [
     "Billing adapter"
    ],
    "application_services": [
     "ChargeSubscription",
     "RecordUsage"
    ],
    "commands": [
     "ChargeSubscription",
     "RecordUsage"
    ],
    "domain_events": [
     "InvoicePaid",
     "SubscriptionCanceled"
    ],
    "policies": [
     "Meter artifact delivery for usage pricing"
    ],
    "specifications": [
     "ChargeabilitySpec"
    ],
    "invariants": [
     "No charge without a delivered artifact when priced per artifact"
    ],
    "ai_agents": [],
    "human_roles": [
     "Finance"
    ],
    "data_owned": [
     "Subscriptions",
     "Invoices"
    ],
    "inputs": [
     "Delivery events"
    ],
    "outputs": [
     "Invoice records"
    ],
    "external_integrations": [
     "Stripe"
    ],
    "risks": [
     "Tax per-disaster event errors"
    ],
    "interfaces": [
     "← Client Delivery"
    ]
   },
   {
    "name": "Identity & Access",
    "purpose": "SSO, MFA, RBAC, session management.",
    "subdomain": "Identity (generic)",
    "type": "generic",
    "owned_language": [
     "User",
     "Role",
     "Session"
    ],
    "owns": [
     "Users",
     "Roles table",
     "Sessions"
    ],
    "does_not_own": [
     "Business capability decisions"
    ],
    "primary_actors": [
     "Platform admin",
     "User"
    ],
    "entities": [
     "User",
     "RoleAssignment",
     "Session"
    ],
    "value_objects": [
     "Role",
     "Claim"
    ],
    "aggregates": [
     "UserAggregate"
    ],
    "domain_services": [
     "Auth service"
    ],
    "application_services": [
     "SignIn",
     "AssignRole"
    ],
    "commands": [
     "SignIn",
     "AssignRole"
    ],
    "domain_events": [
     "UserSignedIn",
     "RoleAssigned"
    ],
    "policies": [
     "Roles in a dedicated table, checked server-side"
    ],
    "specifications": [
     "RoleAuthoritySpec"
    ],
    "invariants": [
     "No role check runs client-only"
    ],
    "ai_agents": [],
    "human_roles": [
     "Platform admin"
    ],
    "data_owned": [
     "Users",
     "Roles",
     "Sessions"
    ],
    "inputs": [
     "Auth events"
    ],
    "outputs": [
     "Sessions"
    ],
    "external_integrations": [
     "IdP (Google / Okta)"
    ],
    "risks": [
     "Role escalation"
    ],
    "interfaces": [
     "→ every other context"
    ]
   },
   {
    "name": "Analytics & Reporting",
    "purpose": "Operational + business metrics, outcome reports.",
    "subdomain": "Analytics (supporting)",
    "type": "supporting",
    "owned_language": [
     "Metric",
     "Dashboard",
     "Outcome report"
    ],
    "owns": [
     "Metric definitions",
     "Dashboards"
    ],
    "does_not_own": [
     "Raw write models"
    ],
    "primary_actors": [
     "Ops lead",
     "Owner"
    ],
    "entities": [
     "MetricDefinition",
     "Dashboard"
    ],
    "value_objects": [
     "Window",
     "Target"
    ],
    "aggregates": [
     "MetricDefinitionAggregate"
    ],
    "domain_services": [
     "Rollup service"
    ],
    "application_services": [
     "PublishMetric",
     "PublishDashboard"
    ],
    "commands": [
     "PublishMetric",
     "PublishDashboard"
    ],
    "domain_events": [
     "DashboardPublished"
    ],
    "policies": [
     "North-star must be wired before Phase 2 launch"
    ],
    "specifications": [
     "MetricDefinedSpec"
    ],
    "invariants": [
     "Metrics have a definition, a target, and an owner"
    ],
    "ai_agents": [],
    "human_roles": [
     "Ops lead"
    ],
    "data_owned": [
     "Metric definitions",
     "Read-model rollups"
    ],
    "inputs": [
     "Domain events (as read-only consumer)"
    ],
    "outputs": [
     "Dashboards",
     "Outcome reports"
    ],
    "external_integrations": [
     "BI tool"
    ],
    "risks": [
     "Vanity metrics dominating"
    ],
    "interfaces": [
     "← every context (read-only)"
    ]
   }
  ],
  "context_map": [
   {
    "upstream": "Sales & Intake",
    "downstream": "Service Fulfillment",
    "pattern": "customer-supplier",
    "business_reason": "Fulfillment cannot start without an accepted engagement.",
    "data_exchanged": [
     "Engagement",
     "Scope statement"
    ],
    "events_exchanged": [
     "EngagementAccepted"
    ],
    "contract_type": "Published language (Engagement record)",
    "failure_risks": [
     "Silent scope mismatch"
    ],
    "acl_notes": "Fulfillment consumes only fields it needs; no direct DB coupling.",
    "ownership_boundary": "Sales owns engagement lifecycle."
   },
   {
    "upstream": "Service Fulfillment",
    "downstream": "Quality Assurance",
    "pattern": "customer-supplier",
    "business_reason": "Signoff is a hard gate on delivery.",
    "data_exchanged": [
     "Draft",
     "Evidence trail"
    ],
    "events_exchanged": [
     "DraftReady",
     "ArtifactSigned"
    ],
    "contract_type": "Published language",
    "failure_risks": [
     "Reviewer bottleneck"
    ],
    "acl_notes": "QA never mutates draft content; only appends signoff.",
    "ownership_boundary": "QA owns signature log."
   },
   {
    "upstream": "AI Orchestration",
    "downstream": "Service Fulfillment",
    "pattern": "customer-supplier",
    "business_reason": "Draft is produced by AI; Fulfillment consumes it.",
    "data_exchanged": [
     "Draft payload",
     "Confidence score"
    ],
    "events_exchanged": [
     "DraftProduced",
     "EscalationRaised"
    ],
    "contract_type": "Published language (validated schema)",
    "failure_risks": [
     "Draft failing OutputValidator reaches Fulfillment"
    ],
    "acl_notes": "OutputValidator sits inside AI Orchestration.",
    "ownership_boundary": "AI owns run log; Fulfillment owns draft state."
   },
   {
    "upstream": "Knowledge Base & Retrieval",
    "downstream": "AI Orchestration",
    "pattern": "open-host-service",
    "business_reason": "Retrieval is a stable interface used by all agents.",
    "data_exchanged": [
     "Retrieval hits",
     "Source citations"
    ],
    "events_exchanged": [
     "DocIngested",
     "IndexRebuilt"
    ],
    "contract_type": "Open-host published API",
    "failure_risks": [
     "Cross-recipient leak"
    ],
    "acl_notes": "Every call carries recipient + partition claim.",
    "ownership_boundary": "Knowledge owns indices."
   },
   {
    "upstream": "Client Onboarding & Profile",
    "downstream": "Service Fulfillment",
    "pattern": "customer-supplier",
    "business_reason": "No intake without a provisioned recipient + reviewer.",
    "data_exchanged": [
     "Recipient profile",
     "Reviewer identity"
    ],
    "events_exchanged": [
     "RecipientProvisioned",
     "ReviewerRegistered"
    ],
    "contract_type": "Published language",
    "failure_risks": [
     "Expired reviewer credential"
    ],
    "acl_notes": "Fulfillment reads a projection; does not query Onboarding tables.",
    "ownership_boundary": "Onboarding owns recipient + reviewer records."
   },
   {
    "upstream": "Service Fulfillment",
    "downstream": "Client Delivery & Success",
    "pattern": "customer-supplier",
    "business_reason": "Delivery is downstream of signoff.",
    "data_exchanged": [
     "Signed artifact"
    ],
    "events_exchanged": [
     "ArtifactDelivered",
     "DeliveryConfirmed"
    ],
    "contract_type": "Published language",
    "failure_risks": [
     "Silent delivery failure"
    ],
    "acl_notes": "Delivery adapter is inside Fulfillment; Delivery context tracks the receipt.",
    "ownership_boundary": "Delivery context owns receipts."
   },
   {
    "upstream": "Quality Assurance",
    "downstream": "Compliance & Governance",
    "pattern": "customer-supplier",
    "business_reason": "Retractions feed compliance workflows.",
    "data_exchanged": [
     "Retraction record"
    ],
    "events_exchanged": [
     "RetractionFiled"
    ],
    "contract_type": "Published language",
    "failure_risks": [
     "Retraction not surfaced"
    ],
    "acl_notes": "Compliance subscribes to the event stream.",
    "ownership_boundary": "QA owns retraction record; Compliance owns downstream runbook."
   },
   {
    "upstream": "Compliance & Governance",
    "downstream": "Service Fulfillment",
    "pattern": "conformist",
    "business_reason": "Fulfillment must respect reproject decisions.",
    "data_exchanged": [
     "Reproject decision"
    ],
    "events_exchanged": [
     "ReprojectDecisionChanged"
    ],
    "contract_type": "Read-only projection consumed by Fulfillment",
    "failure_risks": [
     "Fulfillment ignoring a blocked reproject"
    ],
    "acl_notes": "Fulfillment conforms to Compliance's reproject model.",
    "ownership_boundary": "Compliance owns reproject model."
   },
   {
    "upstream": "Client Delivery & Success",
    "downstream": "Billing & Revenue",
    "pattern": "customer-supplier",
    "business_reason": "Delivery is the meter for per-artifact pricing.",
    "data_exchanged": [
     "Delivery receipt"
    ],
    "events_exchanged": [
     "DeliveryConfirmed"
    ],
    "contract_type": "Published language",
    "failure_risks": [
     "Missed usage record"
    ],
    "acl_notes": "Billing subscribes to delivery events.",
    "ownership_boundary": "Billing owns invoicing."
   },
   {
    "upstream": "Identity & Access",
    "downstream": "every other context",
    "pattern": "shared-kernel",
    "business_reason": "Auth primitives are shared.",
    "data_exchanged": [
     "Session claim",
     "Role"
    ],
    "events_exchanged": [],
    "contract_type": "Shared kernel (tiny, versioned)",
    "failure_risks": [
     "Kernel bloat"
    ],
    "acl_notes": "Kernel kept intentionally small.",
    "ownership_boundary": "Identity owns the primitives."
   },
   {
    "upstream": "every context",
    "downstream": "Analytics & Reporting",
    "pattern": "conformist",
    "business_reason": "Analytics conforms to whatever events contexts publish.",
    "data_exchanged": [
     "Domain events (read-only)"
    ],
    "events_exchanged": [
     "all"
    ],
    "contract_type": "Read-only event subscription",
    "failure_risks": [
     "Event schema drift"
    ],
    "acl_notes": "Analytics stores its own read model.",
    "ownership_boundary": "Analytics owns rollups."
   }
  ],
  "external_integrations": [
   {
    "system": "PM management software (Vantaca / CINC / AppFolio / TOPS)",
    "risk": "Export-format drift; unparseable PDF tables; per-vendor quirks",
    "internal_model": "source document record",
    "acl_strategy": "Adapter in External Integrations context translates external schema → internal domain term; upstream schema never leaks past the adapter.",
    "owner_context": "External Integrations",
    "data_in": [
     "External record"
    ],
    "data_out": [
     "Ack or receipt"
    ],
    "trigger": "api",
    "failure_strategy": "Exponential backoff with jitter; circuit breaker on repeated failure; dead-letter with owner-visible alert.",
    "audit_need": "Every call logged with recipient, request id, cost, and payload hash (no PII in logs)."
   },
   {
    "system": "Cost-documentation-study vendor formats (major + regional preparers)",
    "risk": "Layout drift between study vintages; scanned-only PDFs",
    "internal_model": "extracted study fields with page provenance",
    "acl_strategy": "Adapter in External Integrations context translates external schema → internal domain term; upstream schema never leaks past the adapter.",
    "owner_context": "External Integrations",
    "data_in": [
     "External record"
    ],
    "data_out": [
     "Ack or receipt"
    ],
    "trigger": "api",
    "failure_strategy": "Exponential backoff with jitter; circuit breaker on repeated failure; dead-letter with owner-visible alert.",
    "audit_need": "Every call logged with recipient, request id, cost, and payload hash (no PII in logs)."
   },
   {
    "system": "Airtable intake tracker + Drive folder tree",
    "risk": "Manual mis-filing; permission sprawl across per-PM/per-disaster event folders",
    "internal_model": "pack order status record",
    "acl_strategy": "Adapter in External Integrations context translates external schema → internal domain term; upstream schema never leaks past the adapter.",
    "owner_context": "External Integrations",
    "data_in": [
     "External record"
    ],
    "data_out": [
     "Ack or receipt"
    ],
    "trigger": "api",
    "failure_strategy": "Exponential backoff with jitter; circuit breaker on repeated failure; dead-letter with owner-visible alert.",
    "audit_need": "Every call logged with recipient, request id, cost, and payload hash (no PII in logs)."
   },
   {
    "system": "Frontier LLM APIs (provider-portable)",
    "risk": "Model drift; rate limits; silent quality regression",
    "internal_model": "extraction run with confidence scores",
    "acl_strategy": "OutputValidator + prompt-injection scrubber + per-recipient retrieval scope inside AI Orchestration.",
    "owner_context": "AI Orchestration",
    "data_in": [
     "Prompt + retrieval context"
    ],
    "data_out": [
     "Draft + confidence"
    ],
    "trigger": "api",
    "failure_strategy": "Exponential backoff with jitter; circuit breaker on repeated failure; dead-letter with owner-visible alert.",
    "audit_need": "Every call logged with recipient, request id, cost, and payload hash (no PII in logs)."
   }
  ],
  "event_storm": [
   {
    "seq": 1,
    "command": "QualifyLead",
    "event": "LeadQualified",
    "actor": "Sales / Qualifier Copilot",
    "context": "Sales & Intake",
    "aggregate": "EngagementAggregate",
    "policy": "Reject out-of-ICP",
    "downstream": "Engagement offer",
    "risk": "Out-of-scope acceptance"
   },
   {
    "seq": 2,
    "command": "AcceptEngagement",
    "event": "EngagementAccepted",
    "actor": "Owner",
    "context": "Sales & Intake",
    "aggregate": "EngagementAggregate",
    "policy": "Engagement letter required",
    "downstream": "Onboarding starts",
    "risk": "Missing engagement letter"
   },
   {
    "seq": 3,
    "command": "ProvisionRecipient",
    "event": "RecipientProvisioned",
    "actor": "Onboarding lead",
    "context": "Client Onboarding",
    "aggregate": "RecipientAggregate",
    "policy": "Named reviewer required",
    "downstream": "Reviewer registration",
    "risk": "Reviewer credential expired"
   },
   {
    "seq": 4,
    "command": "OpenIntake",
    "event": "PackOrderAccepted",
    "actor": "Customer operator",
    "context": "Service Fulfillment",
    "aggregate": "PackOrderAggregate",
    "policy": "Scope-fit spec",
    "downstream": "AI drafting scheduled",
    "risk": "Scope drift"
   },
   {
    "seq": 5,
    "command": "AttachEvidence",
    "event": "EvidenceCollected",
    "actor": "Customer + Retrieval",
    "context": "Service Fulfillment",
    "aggregate": "PackOrderAggregate",
    "policy": "Evidence coverage spec",
    "downstream": "Drafting authorized",
    "risk": "Insufficient evidence"
   },
   {
    "seq": 6,
    "command": "StartAgentRun",
    "event": "DraftProduced",
    "actor": "AI Orchestrator",
    "context": "AI Orchestration",
    "aggregate": "AgentRunAggregate",
    "policy": "Confidence threshold",
    "downstream": "Reviewer queue OR escalation",
    "risk": "Prompt injection"
   },
   {
    "seq": 7,
    "command": "SubmitForSignoff",
    "event": "DraftReady",
    "actor": "Service Fulfillment",
    "context": "Service Fulfillment",
    "aggregate": "CompletenessPackAggregate",
    "policy": "Coverage complete",
    "downstream": "Reviewer notified",
    "risk": "Reviewer overload"
   },
   {
    "seq": 8,
    "command": "ApproveArtifact",
    "event": "ArtifactSigned",
    "actor": "Documentation analyst",
    "context": "Quality Assurance",
    "aggregate": "SignoffAggregate",
    "policy": "Reviewer authority spec",
    "downstream": "Delivery authorized",
    "risk": "Signature spoof"
   },
   {
    "seq": 9,
    "command": "DeliverCompletenessPack",
    "event": "ArtifactDelivered",
    "actor": "Delivery adapter",
    "context": "Service Fulfillment",
    "aggregate": "CompletenessPackAggregate",
    "policy": "Deliverability spec",
    "downstream": "Billing meter, customer notified",
    "risk": "Silent delivery failure"
   },
   {
    "seq": 10,
    "command": "ConfirmDelivery",
    "event": "DeliveryConfirmed",
    "actor": "Client Delivery",
    "context": "Client Delivery & Success",
    "aggregate": "DeliveryAggregate",
    "policy": "Ack within SLA",
    "downstream": "Success cadence",
    "risk": "Missed ack"
   },
   {
    "seq": 11,
    "command": "RecordUsage",
    "event": "InvoicePaid",
    "actor": "Billing",
    "context": "Billing & Revenue",
    "aggregate": "SubscriptionAggregate",
    "policy": "Chargeability spec",
    "downstream": "Revenue rollup",
    "risk": "Tax misapplication"
   },
   {
    "seq": 12,
    "command": "ResolveOwnerAction",
    "event": "OwnerActionResolved",
    "actor": "Business owner",
    "context": "Compliance & Governance",
    "aggregate": "OwnerActionLedgerAggregate",
    "policy": "Reproject readiness spec",
    "downstream": "Reproject-decision recompute",
    "risk": "Public claim while blocker open"
   },
   {
    "seq": 13,
    "command": "FileRetraction",
    "event": "RetractionFiled",
    "actor": "Legal + Documentation analyst",
    "context": "Quality Assurance",
    "aggregate": "RetractionAggregate",
    "policy": "Retraction preconditions",
    "downstream": "Customer notification, audit log",
    "risk": "Delayed retraction"
   }
  ],
  "critical_path": [
   "PackOrderAccepted → EvidenceCollected → DraftReady → ArtifactSigned → ArtifactDelivered → DeliveryConfirmed"
  ],
  "exception_flows": [
   "DraftProduced with low confidence → EscalationRaised → reviewer manual draft → ArtifactSigned",
   "DeliverArtifact blocked by open owner action → DeliveryBlocked → owner resolves → retry",
   "DeliveryFailed at adapter → customer alert within 1h → Success ticket → retry with backoff"
  ],
  "escalation_flows": [
   "AI Orchestration escalates to Reviewer",
   "Reviewer escalates ambiguous artifact to Legal",
   "Success lead escalates silent delivery failure to Owner",
   "Owner escalates the applicant's counsel inquiry to external counsel"
  ],
  "retry_flows": [
   "External API failure → exponential backoff with jitter, then dead-letter with owner-visible alert",
   "Model timeout → retry once, then EscalationRaised",
   "Delivery adapter failure → retry with backoff, then customer alert"
  ],
  "manual_override_flows": [
   "Reviewer may override AI classification and re-route",
   "Owner may force-block a delivery via Compliance ledger",
   "Ops may pull a prompt version at any time (feature flag)"
  ],
  "commands": [
   {
    "name": "OpenIntake",
    "issued_by": "Customer operator",
    "preconditions": [
     "Engagement accepted",
     "Recipient provisioned"
    ],
    "aggregate": "PackOrderAggregate",
    "success_event": "PackOrderAccepted",
    "failure_event": "IntakeRejected",
    "authorization": "Recipient recipient with Operator role",
    "validation": "Scope statement present; no duplicate open intake",
    "audit": "Command + payload hash logged with recipient + user"
   },
   {
    "name": "AttachEvidence",
    "issued_by": "Customer operator / Retrieval",
    "preconditions": [
     "Intake open",
     "File type allowed"
    ],
    "aggregate": "PackOrderAggregate",
    "success_event": "EvidenceCollected",
    "failure_event": "EvidenceRejected",
    "authorization": "Same recipient",
    "validation": "Virus scan clean; PII policy respected",
    "audit": "Every attachment hashed and logged"
   },
   {
    "name": "StartAgentRun",
    "issued_by": "AI Orchestrator",
    "preconditions": [
     "Evidence coverage complete",
     "Prompt version active"
    ],
    "aggregate": "AgentRunAggregate",
    "success_event": "DraftProduced",
    "failure_event": "EscalationRaised",
    "authorization": "Service role",
    "validation": "OutputValidator schema passes",
    "audit": "Prompt version + retrieval hits + cost captured"
   },
   {
    "name": "ApproveArtifact",
    "issued_by": "Documentation analyst",
    "preconditions": [
     "Draft ready",
     "Reviewer session live",
     "No unresolved escalation"
    ],
    "aggregate": "SignoffAggregate",
    "success_event": "ArtifactSigned",
    "failure_event": "ArtifactRejected",
    "authorization": "Reviewer role bound to recipient",
    "validation": "Every claim cites evidence",
    "audit": "Signature manifest + timestamp"
   },
   {
    "name": "DeliverCompletenessPack",
    "issued_by": "Delivery adapter",
    "preconditions": [
     "Artifact signed",
     "Compliance reproject allows delivery"
    ],
    "aggregate": "CompletenessPackAggregate",
    "success_event": "ArtifactDelivered",
    "failure_event": "DeliveryFailed",
    "authorization": "Service role",
    "validation": "Delivery method valid; receipt captured",
    "audit": "Delivery receipt archived"
   },
   {
    "name": "ResolveOwnerAction",
    "issued_by": "Business owner",
    "preconditions": [
     "Owner-action open"
    ],
    "aggregate": "OwnerActionLedgerAggregate",
    "success_event": "OwnerActionResolved",
    "failure_event": "OwnerActionRejected",
    "authorization": "Owner role",
    "validation": "Supplied fact matches action schema",
    "audit": "Actor + before/after captured"
   },
   {
    "name": "FileRetraction",
    "issued_by": "Legal + Documentation analyst",
    "preconditions": [
     "Artifact previously delivered",
     "Impact statement present"
    ],
    "aggregate": "RetractionAggregate",
    "success_event": "RetractionFiled",
    "failure_event": "RetractionRejected",
    "authorization": "Legal AND Reviewer co-sign",
    "validation": "Retraction preconditions spec",
    "audit": "Full retraction recovery file archived"
   }
  ],
  "policies": [
   {
    "name": "Auto-request signoff on coverage complete",
    "trigger": "EvidenceCollected",
    "condition": "Evidence coverage spec passes",
    "action": "Enqueue SubmitForSignoff",
    "context": "Service Fulfillment",
    "ai_involvement": "none",
    "human_approval": false
   },
   {
    "name": "Escalate on low confidence",
    "trigger": "DraftProduced",
    "condition": "Confidence < threshold OR OutputValidator warning",
    "action": "Emit EscalationRaised, route to reviewer queue",
    "context": "AI Orchestration",
    "ai_involvement": "author",
    "human_approval": false
   },
   {
    "name": "Block delivery on open compliance blocker",
    "trigger": "DeliverArtifact command",
    "condition": "Compliance reproject decision != 'ready-with-owner-actions' or 'ready'",
    "action": "Reject delivery, emit DeliveryBlocked",
    "context": "Service Fulfillment ↔ Compliance",
    "ai_involvement": "none",
    "human_approval": true
   },
   {
    "name": "Retract on material finding",
    "trigger": "MaterialFindingReported",
    "condition": "Signed claim materially wrong",
    "action": "Open Retraction workflow with legal co-sign",
    "context": "Quality Assurance",
    "ai_involvement": "assist",
    "human_approval": true
   },
   {
    "name": "Alert on delivery failure",
    "trigger": "DeliveryFailed",
    "condition": "Any",
    "action": "Notify customer within 1h + open Success ticket",
    "context": "Client Delivery & Success",
    "ai_involvement": "none",
    "human_approval": false
   }
  ],
  "aggregates": [
   {
    "name": "PackOrderAggregate",
    "root": "PackOrder",
    "context": "Service Fulfillment",
    "purpose": "Guard intake + evidence + draft state transitions.",
    "entities": [
     "PackOrder",
     "EvidenceLink",
     "Draft"
    ],
    "value_objects": [
     "ConfidenceScore",
     "EvidenceCitation"
    ],
    "invariants": [
     "Every claim in a delivered artifact cites evidence",
     "An pack order in state 'delivered' is immutable"
    ],
    "commands": [
     "OpenIntake",
     "AttachEvidence",
     "RequestDraft",
     "SubmitForSignoff"
    ],
    "events": [
     "PackOrderAccepted",
     "EvidenceCollected",
     "DraftReady"
    ],
    "repository": "PackOrderRepository",
    "transaction_boundary": "One pack order per transaction"
   },
   {
    "name": "CompletenessPackAggregate",
    "root": "Completeness pack",
    "context": "Service Fulfillment",
    "purpose": "Own the recovery file lifecycle from signed to delivered.",
    "entities": [
     "Completeness pack",
     "Delivery"
    ],
    "value_objects": [
     "DeliveryAddress"
    ],
    "invariants": [
     "A recovery file cannot be delivered without a valid Signoff"
    ],
    "commands": [
     "DeliverCompletenessPack"
    ],
    "events": [
     "ArtifactDelivered"
    ],
    "repository": "Completeness packRepository",
    "transaction_boundary": "One recovery file per transaction"
   },
   {
    "name": "SignoffAggregate",
    "root": "Signoff",
    "context": "Quality Assurance",
    "purpose": "Bind reviewer identity + timestamp + artifact hash immutably.",
    "entities": [
     "Signoff"
    ],
    "value_objects": [
     "SignatureManifest"
    ],
    "invariants": [
     "Signature bound to a live authenticated session, not a form field",
     "Signed artifacts are immutable"
    ],
    "commands": [
     "ApproveArtifact"
    ],
    "events": [
     "ArtifactSigned"
    ],
    "repository": "SignoffRepository",
    "transaction_boundary": "One signoff per transaction"
   },
   {
    "name": "RetractionAggregate",
    "root": "Retraction",
    "context": "Quality Assurance",
    "purpose": "Handle formal correction/withdrawal of a signed artifact.",
    "entities": [
     "Retraction"
    ],
    "value_objects": [
     "RetractionReason",
     "ImpactStatement"
    ],
    "invariants": [
     "A retraction requires Legal + Reviewer co-signature"
    ],
    "commands": [
     "FileRetraction"
    ],
    "events": [
     "RetractionFiled"
    ],
    "repository": "RetractionRepository",
    "transaction_boundary": "One retraction per transaction"
   },
   {
    "name": "AgentRunAggregate",
    "root": "AgentRun",
    "context": "AI Orchestration",
    "purpose": "Track a single bounded AI run with prompt version, cost, and output validation.",
    "entities": [
     "AgentRun",
     "RetrievalHit"
    ],
    "value_objects": [
     "ConfidenceScore",
     "TokenBudget",
     "ModelCost"
    ],
    "invariants": [
     "No output emitted without OutputValidator pass",
     "Retrieval scoped to a single recipient partition"
    ],
    "commands": [
     "StartAgentRun"
    ],
    "events": [
     "DraftProduced",
     "EscalationRaised"
    ],
    "repository": "AgentRunRepository",
    "transaction_boundary": "One run per transaction"
   },
   {
    "name": "OwnerActionLedgerAggregate",
    "root": "OwnerActionLedger",
    "context": "Compliance & Governance",
    "purpose": "Own the set of owner-supplied facts blocking public claims.",
    "entities": [
     "OwnerAction"
    ],
    "value_objects": [
     "BlockerReason",
     "Disaster-event"
    ],
    "invariants": [
     "Reproject cannot flip to 'ready' with open blocking owner actions"
    ],
    "commands": [
     "RaiseOwnerAction",
     "ResolveOwnerAction"
    ],
    "events": [
     "OwnerActionResolved",
     "ReprojectDecisionChanged"
    ],
    "repository": "OwnerActionRepository",
    "transaction_boundary": "One ledger per recipient"
   },
   {
    "name": "RecipientAggregate",
    "root": "Recipient",
    "context": "Client Onboarding & Profile",
    "purpose": "Own recipient provisioning + reviewer registration.",
    "entities": [
     "Recipient",
     "ReviewerIdentity"
    ],
    "value_objects": [
     "ContactMatrix",
     "Disaster-eventSet"
    ],
    "invariants": [
     "Every recipient has at least one named reviewer with valid credential"
    ],
    "commands": [
     "ProvisionRecipient",
     "RegisterReviewer"
    ],
    "events": [
     "RecipientProvisioned",
     "ReviewerRegistered"
    ],
    "repository": "RecipientRepository",
    "transaction_boundary": "One recipient per transaction"
   },
   {
    "name": "DeliveryAggregate",
    "root": "Delivery",
    "context": "Client Delivery & Success",
    "purpose": "Own delivery receipts and revision requests.",
    "entities": [
     "Delivery",
     "RevisionRequest"
    ],
    "value_objects": [
     "DeliveryMethod"
    ],
    "invariants": [
     "Every DeliveryConfirmed has a linked Signoff"
    ],
    "commands": [
     "ConfirmDelivery",
     "RecordRevisionRequest"
    ],
    "events": [
     "DeliveryConfirmed",
     "RevisionRequested"
    ],
    "repository": "DeliveryRepository",
    "transaction_boundary": "One delivery per transaction"
   }
  ],
  "invariants": [
   {
    "invariant": "A recovery file cannot be delivered without a valid Reviewer signoff.",
    "context": "Service Fulfillment ↔ Quality Assurance",
    "aggregate": "CompletenessPackAggregate",
    "why": "Legal defensibility; brand-risk",
    "enforcement": "Aggregate command handler rejects delivery without a signoff reference"
   },
   {
    "invariant": "Every claim in a delivered artifact cites at least one evidence item.",
    "context": "Service Fulfillment",
    "aggregate": "PackOrderAggregate",
    "why": "Audit reconstructability",
    "enforcement": "EvidenceCoverageSpec on submit-for-signoff"
   },
   {
    "invariant": "A signature is bound to a live authenticated session, not a form field.",
    "context": "Quality Assurance",
    "aggregate": "SignoffAggregate",
    "why": "Anti-spoofing, anti-repudiation",
    "enforcement": "Signature service validates session claim server-side"
   },
   {
    "invariant": "Signed artifacts are immutable; corrections go through Retraction.",
    "context": "Quality Assurance",
    "aggregate": "SignoffAggregate + RetractionAggregate",
    "why": "Preserves audit chain",
    "enforcement": "Repository denies mutation after signoff"
   },
   {
    "invariant": "No AI output leaves AI Orchestration without OutputValidator pass.",
    "context": "AI Orchestration",
    "aggregate": "AgentRunAggregate",
    "why": "Grounding + hallucination control",
    "enforcement": "AgentRun terminates as EscalationRaised on validator failure"
   },
   {
    "invariant": "Retrieval is scoped to a single recipient partition per call.",
    "context": "Knowledge Base ↔ AI Orchestration",
    "aggregate": "IndexShardAggregate",
    "why": "Prevent cross-recipient leak",
    "enforcement": "RecipientIsolationSpec at retrieval router"
   },
   {
    "invariant": "Reproject cannot flip to 'ready' with open blocking owner actions.",
    "context": "Compliance & Governance",
    "aggregate": "OwnerActionLedgerAggregate",
    "why": "Prevent premature public claim",
    "enforcement": "ReprojectReadinessSpec on ResolveOwnerAction"
   },
   {
    "invariant": "Every recipient has at least one named reviewer with valid credential.",
    "context": "Client Onboarding & Profile",
    "aggregate": "RecipientAggregate",
    "why": "No unattributed signoffs",
    "enforcement": "ReviewerCredentialSpec on recipient provisioning"
   },
   {
    "invariant": "Roles are stored in a dedicated table and checked server-side.",
    "context": "Identity & Access",
    "aggregate": "UserAggregate",
    "why": "Prevent privilege escalation",
    "enforcement": "RoleAuthoritySpec + RLS on protected tables"
   }
  ],
  "ai_agents": [
   {
    "name": "Drafter Agent",
    "context": "AI Orchestration",
    "responsibility": "Produce a cited draft of a recovery file section from validated retrieval context.",
    "inputs": [
     "Intake summary",
     "Retrieval hits (recipient-scoped)",
     "Prompt version"
    ],
    "outputs": [
     "Structured draft payload",
     "Confidence score",
     "Citations"
    ],
    "tools": [
     "Retrieval API",
     "Structured-output validator",
     "Cost meter"
    ],
    "forbidden_actions": [
     "Call external tools not in its allowlist",
     "Access another recipient's retrieval index",
     "Emit output that skips the OutputValidator",
     "Author final legal / clinical / financial decisions"
    ],
    "memory_scope": "Per-run only; no cross-run memory; prompt-injection scrubber on all customer inputs.",
    "retrieval_sources": [
     "Recipient-scoped knowledge base",
     "Public the applicant's counsel sources (read-only cache)"
    ],
    "validations": [
     "Structured-output schema",
     "Citation-coverage rule",
     "PII-scrub rule on prompt inputs"
    ],
    "confidence_scoring": "Model-reported logprobs + citation-coverage combined into a bounded [0..1] score.",
    "escalation_triggers": [
     "Score < threshold",
     "Ambiguous disaster event",
     "Missing citation on any claim"
    ],
    "human_approval": true,
    "failure_modes": [
     "Prompt injection",
     "Hallucinated citation",
     "Retrieval-recipient leak"
    ],
    "audit_logs": [
     "Prompt version",
     "Retrieval hits (ids only)",
     "Cost + latency",
     "Validator verdict"
    ],
    "metrics": [
     "Draft acceptance rate",
     "Escalation rate",
     "Cost per artifact",
     "p95 latency"
    ],
    "versioning": "Prompt versions immutable; published via PromptRegistryAggregate; rollout via feature flag."
   },
   {
    "name": "Classifier Agent",
    "context": "AI Orchestration",
    "responsibility": "Route an pack order to the right template, disaster event, and reviewer queue.",
    "inputs": [
     "Intake payload"
    ],
    "outputs": [
     "Route decision + confidence"
    ],
    "tools": [
     "Prompt registry"
    ],
    "forbidden_actions": [
     "Make final legal / clinical / financial decisions",
     "Bypass Reviewer queue routing"
    ],
    "memory_scope": "Per-run only",
    "retrieval_sources": [
     "Templates + disaster event reference"
    ],
    "validations": [
     "Structured-output schema",
     "Known-route allowlist"
    ],
    "confidence_scoring": "Model logprobs.",
    "escalation_triggers": [
     "Score < threshold",
     "Unknown disaster event"
    ],
    "human_approval": false,
    "failure_modes": [
     "Wrong route → wrong reviewer"
    ],
    "audit_logs": [
     "Route decision + rationale"
    ],
    "metrics": [
     "Routing accuracy vs reviewer corrections"
    ],
    "versioning": "Same as Drafter"
   },
   {
    "name": "Evaluator Agent",
    "context": "AI Orchestration",
    "responsibility": "Run offline evals on prompt versions before rollout.",
    "inputs": [
     "Golden dataset",
     "Prompt candidate"
    ],
    "outputs": [
     "Pass/fail per case + drift report"
    ],
    "tools": [
     "Golden dataset"
    ],
    "forbidden_actions": [
     "Touch production recipient data"
    ],
    "memory_scope": "Per-eval only",
    "retrieval_sources": [
     "Golden dataset only"
    ],
    "validations": [
     "Regression thresholds"
    ],
    "confidence_scoring": "Aggregate over dataset",
    "escalation_triggers": [
     "Regression > threshold"
    ],
    "human_approval": true,
    "failure_modes": [
     "Overfit to golden dataset"
    ],
    "audit_logs": [
     "Full eval report archived"
    ],
    "metrics": [
     "Pass rate",
     "Regression rate"
    ],
    "versioning": "Every prompt reproject requires a passing eval"
   }
  ],
  "prompt_chain_map": [
   "Intake → Classifier (route + disaster event) → Drafter (cite + draft) → OutputValidator → Reviewer (approve or escalate)",
   "Retraction analysis → Evaluator (assist only) → Legal + Reviewer co-sign"
  ],
  "rag_map": [
   "Per-recipient knowledge base partition → retrieval router → recipient-scoped hits → Drafter",
   "Public the applicant's counsel sources (read-only cache) → shared retrieval → Drafter (cited)"
  ],
  "ai_evaluation": [
   "Golden dataset of past reviewer-accepted artifacts per vertical",
   "Regression thresholds on acceptance rate + citation coverage",
   "Every prompt reproject requires a passing Evaluator run"
  ],
  "hallucination_controls": [
   "Retrieval-first (no free-form generation without citation)",
   "Structured-output validator enforces citation-per-claim",
   "Confidence-scored escalation",
   "Reviewer gate on all outbound artifacts"
  ],
  "human_in_the_loop_plan": [
   "Reviewer signoff on every outbound artifact",
   "Legal co-sign on retractions",
   "Owner approval on public-reproject readiness",
   "Ops sign-off on prompt-version rollout"
  ],
  "ai_audit_plan": [
   "Every AgentRun logged with prompt version, retrieval hit ids, cost, latency, validator verdict",
   "13-month rolling retention on run logs",
   "PII scrubbed from log payloads"
  ],
  "prompt_versioning": "Prompt versions immutable once published; rolled out via feature flag; every rollout paired with an Evaluator run.",
  "human_roles": [
   {
    "role": "Documentation analyst",
    "responsibilities": [
     "Approve / reject / request revisions on drafts",
     "Co-sign retractions"
    ],
    "contexts": [
     "Quality Assurance",
     "Service Fulfillment"
    ],
    "decisions_owned": [
     "Signoff",
     "Rejection",
     "Escalation acceptance"
    ],
    "ai_support": [
     "Cited drafts",
     "Confidence-ranked findings"
    ],
    "approval_authority": "Full artifact signoff",
    "escalation_authority": "Escalate to Legal",
    "quality_metrics": [
     "Cycle time to signoff",
     "Signoff-to-retraction ratio"
    ],
    "workload_risks": [
     "Single-reviewer bottleneck"
    ]
   },
   {
    "role": "Business owner",
    "responsibilities": [
     "Resolve owner actions",
     "Decide public-reproject readiness",
     "Own commercial claims"
    ],
    "contexts": [
     "Compliance & Governance",
     "Sales & Intake"
    ],
    "decisions_owned": [
     "Reproject decision",
     "Owner-action ledger"
    ],
    "ai_support": [
     "Blocker summary"
    ],
    "approval_authority": "Reproject readiness",
    "escalation_authority": "Escalate to Legal",
    "quality_metrics": [
     "Blocker close time"
    ],
    "workload_risks": [
     "Single-owner queue"
    ]
   },
   {
    "role": "Legal reviewer",
    "responsibilities": [
     "Retraction co-sign",
     "DSAR + the applicant's counsel response"
    ],
    "contexts": [
     "Quality Assurance",
     "Compliance & Governance"
    ],
    "decisions_owned": [
     "Retraction approval",
     "Disaster-event counsel response"
    ],
    "ai_support": [
     "Precedent surfacing (assist only)"
    ],
    "approval_authority": "Retraction, the applicant's counsel response",
    "escalation_authority": "External counsel",
    "quality_metrics": [
     "Retraction latency"
    ],
    "workload_risks": [
     "Retainer capacity"
    ]
   },
   {
    "role": "Success lead",
    "responsibilities": [
     "Delivery health, revision loop, renewal signal"
    ],
    "contexts": [
     "Client Delivery & Success"
    ],
    "decisions_owned": [
     "Escalate silent failures"
    ],
    "ai_support": [
     "Delivery health digest"
    ],
    "approval_authority": "Customer-visible remediation",
    "escalation_authority": "Owner",
    "quality_metrics": [
     "Time-to-alert on delivery failure"
    ],
    "workload_risks": [
     "Alert fatigue"
    ]
   },
   {
    "role": "Onboarding lead",
    "responsibilities": [
     "Provision recipients, register reviewers, import evidence pack"
    ],
    "contexts": [
     "Client Onboarding & Profile"
    ],
    "decisions_owned": [
     "Recipient readiness"
    ],
    "ai_support": [
     "Checklist coverage"
    ],
    "approval_authority": "Go-live per recipient",
    "escalation_authority": "Owner",
    "quality_metrics": [
     "Time-to-first-artifact"
    ],
    "workload_risks": [
     "Sequential onboarding queue"
    ]
   },
   {
    "role": "Ops (prompt owner)",
    "responsibilities": [
     "Prompt version registry + eval sign-off"
    ],
    "contexts": [
     "AI Orchestration"
    ],
    "decisions_owned": [
     "Prompt rollout"
    ],
    "ai_support": [
     "Evaluator Agent"
    ],
    "approval_authority": "Prompt rollout",
    "escalation_authority": "Engineering",
    "quality_metrics": [
     "Regression rate at rollout"
    ],
    "workload_risks": [
     "Version drift"
    ]
   }
  ],
  "human_review_checkpoints": [
   "AI draft → reviewer approval",
   "Public reproject → owner acceptance",
   "Retraction → legal + reviewer co-sign",
   "Prompt rollout → ops + evaluator"
  ],
  "escalation_matrix": [
   "AI → Reviewer → Legal → Owner → External counsel",
   "Success → Owner → External counsel (the applicant's counsel inquiries)"
  ],
  "manual_override_rules": [
   "Any manual override captured as an explicit override event with actor + reason",
   "No override may bypass a reviewer signoff invariant"
  ],
  "separation_of_duties": [
   "Drafter Agent cannot sign; Reviewer cannot draft on behalf of AI without an override event; Legal cannot silently retract"
  ],
  "quality_control_workflow": [
   "Weekly reviewer calibration meeting",
   "Monthly evaluator regression report",
   "Quarterly retraction-rate review with owner + legal"
  ],
  "data_objects": [
   {
    "name": "pack order",
    "meaning": "Unit of work brought in by customer",
    "owner_context": "Service Fulfillment",
    "writers": [
     "Service Fulfillment"
    ],
    "readers": [
     "QA",
     "Analytics"
    ],
    "source_of_truth": "Service Fulfillment DB",
    "retention": "the grant period plus a defined retention window (audit)",
    "privacy": "confidential",
    "audit": true
   },
   {
    "name": "control evidence",
    "meaning": "Cited fact backing a claim",
    "owner_context": "Service Fulfillment",
    "writers": [
     "Service Fulfillment"
    ],
    "readers": [
     "QA",
     "Analytics"
    ],
    "source_of_truth": "Service Fulfillment DB + Knowledge Base pointers",
    "retention": "the grant period plus a defined retention window",
    "privacy": "confidential",
    "audit": true
   },
   {
    "name": "recovery file",
    "meaning": "Reviewer-signed deliverable",
    "owner_context": "Service Fulfillment",
    "writers": [
     "Service Fulfillment"
    ],
    "readers": [
     "QA",
     "Client Delivery",
     "Analytics"
    ],
    "source_of_truth": "Service Fulfillment DB (immutable after signoff)",
    "retention": "7-10 years (vertical-specific)",
    "privacy": "regulated",
    "audit": true
   },
   {
    "name": "Signoff",
    "meaning": "Reviewer signature manifest",
    "owner_context": "Quality Assurance",
    "writers": [
     "Quality Assurance"
    ],
    "readers": [
     "Service Fulfillment",
     "Analytics"
    ],
    "source_of_truth": "QA DB (append-only)",
    "retention": "10 years",
    "privacy": "confidential",
    "audit": true
   },
   {
    "name": "OwnerActionLedger",
    "meaning": "Blocker facts per recipient",
    "owner_context": "Compliance & Governance",
    "writers": [
     "Compliance & Governance"
    ],
    "readers": [
     "Service Fulfillment (reproject decision)",
     "Analytics"
    ],
    "source_of_truth": "Compliance DB",
    "retention": "the grant period plus a defined retention window",
    "privacy": "internal",
    "audit": true
   },
   {
    "name": "AgentRun",
    "meaning": "Trace of one AI orchestrator run",
    "owner_context": "AI Orchestration",
    "writers": [
     "AI Orchestration"
    ],
    "readers": [
     "Analytics",
     "QA (on escalation)"
    ],
    "source_of_truth": "AI Orchestration DB",
    "retention": "13 months (rolling)",
    "privacy": "internal",
    "audit": true
   },
   {
    "name": "Recipient",
    "meaning": "Customer organization + reviewers",
    "owner_context": "Client Onboarding & Profile",
    "writers": [
     "Client Onboarding & Profile"
    ],
    "readers": [
     "all contexts"
    ],
    "source_of_truth": "Onboarding DB",
    "retention": "Life of contract + the grant period plus a defined retention window",
    "privacy": "confidential",
    "audit": true
   },
   {
    "name": "Subscription + Invoice",
    "meaning": "Commercial relationship + charges",
    "owner_context": "Billing & Revenue",
    "writers": [
     "Billing"
    ],
    "readers": [
     "Analytics"
    ],
    "source_of_truth": "Billing provider (Stripe)",
    "retention": "As required by tax law",
    "privacy": "confidential",
    "audit": true
   },
   {
    "name": "User + Role",
    "meaning": "Identity + authorization",
    "owner_context": "Identity & Access",
    "writers": [
     "Identity & Access"
    ],
    "readers": [
     "all contexts"
    ],
    "source_of_truth": "Identity DB",
    "retention": "Life of account + 2 years",
    "privacy": "confidential",
    "audit": true
   }
  ],
  "read_models": [
   "OperatorDashboard read model (per recipient): open intakes, in-review, delivered this week",
   "ReviewerQueue read model: cases awaiting reviewer with confidence + escalation reason",
   "ComplianceLedger read model: open owner actions + reproject-decision",
   "AnalyticsRollup read model: metric definitions rolled up daily"
  ],
  "reporting_models": [
   "Outcome report per customer: artifacts delivered, cycle time, acceptance rate, retractions",
   "Ops report: AI cost per artifact, escalation rate, reviewer load"
  ],
  "data_duplication_notes": [
   "Reviewer identity is stored in Onboarding, referenced by QA — QA does not own it",
   "OwnerActionLedger duplicates minimal facts into read models for Fulfillment consumption"
  ],
  "data_retention": [
   "Artifacts + evidence + signoffs: 7-10 years (vertical-specific)",
   "AgentRun logs: 13 months rolling",
   "Users + sessions: life of account + 2 years"
  ],
  "data_quality_risks": [
   "Silent schema drift from external systems",
   "Stale retrieval indices after source-doc updates",
   "Missing retraction cross-links after legacy import"
  ],
  "use_cases": [
   {
    "name": "Deliver a reviewer-signed recovery file",
    "actor": "Customer operator + Reviewer",
    "context": "Service Fulfillment + Quality Assurance + AI Orchestration",
    "goal": "Produce and deliver a reviewer-signed recovery file",
    "preconditions": [
     "Recipient provisioned",
     "Reviewer registered",
     "Engagement accepted"
    ],
    "main_flow": [
     "Operator opens pack order",
     "Evidence attached / retrieved",
     "AI Orchestrator drafts with citations",
     "Reviewer approves",
     "Delivery adapter delivers",
     "Success lead confirms delivery"
    ],
    "alternative_flows": [
     "Confidence below threshold → EscalationRaised → reviewer drafts manually",
     "Blocking owner action open → DeliveryBlocked → surfaced to owner",
     "Delivery failure → alert customer within 1h"
    ],
    "business_rules": [
     "Every claim must cite evidence",
     "Only registered reviewer may sign"
    ],
    "ai_role": "Draft + validate + score confidence",
    "human_role": "Sign; escalate; retract",
    "commands": [
     "OpenIntake",
     "AttachEvidence",
     "StartAgentRun",
     "ApproveArtifact",
     "DeliverCompletenessPack"
    ],
    "events": [
     "PackOrderAccepted",
     "EvidenceCollected",
     "DraftProduced",
     "ArtifactSigned",
     "ArtifactDelivered"
    ],
    "aggregates": [
     "PackOrderAggregate",
     "AgentRunAggregate",
     "SignoffAggregate",
     "CompletenessPackAggregate"
    ],
    "success": "recovery file delivered + reviewer signed + audit trail complete",
    "failure_handling": "EscalationRaised → reviewer queue; DeliveryFailed → customer alert + Success ticket",
    "audit": "Full command → event chain with actor + timestamp per step"
   },
   {
    "name": "Retract a delivered artifact",
    "actor": "Legal + Documentation analyst",
    "context": "Quality Assurance + Compliance & Governance",
    "goal": "Formally withdraw / correct a delivered artifact",
    "preconditions": [
     "Artifact previously delivered",
     "Material finding documented"
    ],
    "main_flow": [
     "Finding documented",
     "Legal + Reviewer co-sign retraction",
     "Customer notified",
     "Audit-log append"
    ],
    "alternative_flows": [
     "Reviewer disagrees → escalate to owner",
     "Disaster-event counsel inquiry incoming → run in parallel with legal-response workflow"
    ],
    "business_rules": [
     "Retraction requires Legal + Reviewer co-sign"
    ],
    "ai_role": "Surface prior similar cases (assist only)",
    "human_role": "Co-sign + notify",
    "commands": [
     "FileRetraction"
    ],
    "events": [
     "RetractionFiled"
    ],
    "aggregates": [
     "RetractionAggregate",
     "OwnerActionLedgerAggregate"
    ],
    "success": "Retraction filed + customer notified + audit trail updated",
    "failure_handling": "Rejection path emits RetractionRejected + escalates to owner",
    "audit": "Full retraction recovery file archived, immutable"
   },
   {
    "name": "Resolve an owner action and flip reproject decision",
    "actor": "Business owner",
    "context": "Compliance & Governance",
    "goal": "Close a blocking owner action and recompute reproject readiness",
    "preconditions": [
     "Owner action open"
    ],
    "main_flow": [
     "Owner supplies fact",
     "Ledger updated",
     "ReprojectDecision recomputed",
     "Downstream contexts notified"
    ],
    "alternative_flows": [
     "Fact rejected → OwnerActionRejected",
     "Legal review required → route to legal"
    ],
    "business_rules": [
     "Reproject cannot flip to ready with any blocking action open"
    ],
    "ai_role": "Blocker digest",
    "human_role": "Supply fact + accept reproject",
    "commands": [
     "ResolveOwnerAction"
    ],
    "events": [
     "OwnerActionResolved",
     "ReprojectDecisionChanged"
    ],
    "aggregates": [
     "OwnerActionLedgerAggregate"
    ],
    "success": "Reproject decision flips or stays with clear reason",
    "failure_handling": "OwnerActionRejected + retry loop",
    "audit": "Actor + before/after + timestamp"
   }
  ],
  "architecture": {
   "style": "modular-monolith-event-driven",
   "why": "Single team + single regulated vertical per blueprint + strong consistency requirements around signoff / delivery / reproject-decision favor a monolith. Event-driven internals give us the audit-friendly append-only log without the operational cost of microservices.",
   "rejected_alternatives": [
    "Microservices — no independent scaling or team boundary justifies distributed cost yet.",
    "Serverless-workflow-only — reviewer signoff and audit invariants are easier to keep correct in a monolith.",
    "No-code / low-code — cannot enforce OutputValidator, prompt versioning, or per-recipient retrieval isolation with fidelity."
   ],
   "backend_modules": [
    "Service Fulfillment",
    "AI Orchestration",
    "Quality Assurance",
    "Compliance & Governance",
    "Sales & Intake",
    "Client Onboarding & Profile",
    "Client Delivery & Success",
    "Knowledge Base & Retrieval",
    "Analytics & Reporting"
   ],
   "frontend_modules": [
    "Operator dashboard",
    "Reviewer console",
    "Client portal",
    "Owner console",
    "Ops (prompt registry) console"
   ],
   "api_boundaries": [
    "/intake/*",
    "/artifacts/*",
    "/reviewer/*",
    "/compliance/*",
    "/knowledge/*",
    "/admin/*"
   ],
   "database_strategy": "One managed Postgres; schema-per-context; cross-context reads via published projections; RLS on protected tables.",
   "event_bus": "In-process event dispatcher backed by an outbox table (transactional publish); upgrade path to a real broker if throughput demands.",
   "queue": "Background job queue (managed) for AI runs, delivery adapters, and reindex jobs.",
   "workflow_engine": "None initially — orchestrate via domain events + policies; add a workflow engine if orchestrations exceed 5 sequential steps.",
   "ai_orchestration": "AI Orchestration context owns bounded agents; OutputValidator + prompt registry + recipient-scoped retrieval; retries with backoff.",
   "rag_layer": "Per-recipient partitioned retrieval indices in a managed vector DB; ingestion pipeline in Knowledge Base context.",
   "file_storage": "Managed blob storage with per-recipient prefixes + signed URLs; artifacts hashed on write.",
   "authn_authz": "IdP (Google / Okta) for authn; RBAC via dedicated roles table with server-side checks + RLS.",
   "admin_dashboard": "Ops-facing admin for recipients, users, feature flags, prompt versions.",
   "client_portal": "Customer-facing portal: submit intake, see status, receive artifacts.",
   "operator_dashboard": "Internal: intake queue, reviewer queue, escalation queue, delivery health.",
   "observability": "Structured logs with recipient + request ids; RED metrics per workflow; error tracking with source maps; model-call spans with cost + latency; SLO review weekly.",
   "audit_logging": "Append-only audit log for all state transitions; hash-chained snapshots on signed artifacts.",
   "deployment": "Single production region + multi-AZ managed DB; per-PR preview deploys; migrations gated on review."
  },
  "module_structure": {
   "tree": "/src\n  /contexts\n    /sales-intake\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /client-onboarding\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /service-fulfillment\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /ai-orchestration\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /quality-assurance\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /compliance-governance\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /client-delivery\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /knowledge-base\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n    /analytics\n      /domain\n      /application\n      /infrastructure\n      /interfaces\n  /shared\n    /kernel        # tiny — Ids, Money, Recipient, Actor\n    /events        # published-language event contracts\n    /auth          # session + role primitives\n    /observability # logging, metrics, tracing\n    /config",
   "modules": [
    {
     "name": "service-fulfillment",
     "purpose": "PackOrder → recovery file lifecycle",
     "owned_domain": [
      "PackOrder",
      "Draft",
      "Completeness pack",
      "Delivery"
     ],
     "application_services": [
      "OpenIntake",
      "AttachEvidence",
      "SubmitForSignoff",
      "DeliverCompletenessPack"
     ],
     "infra_adapters": [
      "Delivery adapter",
      "Outbox publisher"
     ],
     "public_interfaces": [
      "/intake/*",
      "/artifacts/*"
     ],
     "forbidden_deps": [
      "billing infra",
      "identity provider internals"
     ]
    },
    {
     "name": "ai-orchestration",
     "purpose": "Bounded AI agents",
     "owned_domain": [
      "AgentRun",
      "PromptVersion"
     ],
     "application_services": [
      "StartAgentRun",
      "PublishPromptVersion"
     ],
     "infra_adapters": [
      "LLM provider client (portable)",
      "Retrieval router"
     ],
     "public_interfaces": [
      "internal"
     ],
     "forbidden_deps": [
      "cross-recipient retrieval",
      "direct delivery"
     ]
    },
    {
     "name": "quality-assurance",
     "purpose": "Signoff + retraction",
     "owned_domain": [
      "Signoff",
      "Retraction"
     ],
     "application_services": [
      "ApproveArtifact",
      "FileRetraction"
     ],
     "infra_adapters": [
      "Signature service"
     ],
     "public_interfaces": [
      "/reviewer/*"
     ],
     "forbidden_deps": [
      "draft content mutation"
     ]
    },
    {
     "name": "compliance-governance",
     "purpose": "Owner-action ledger + reproject decision",
     "owned_domain": [
      "OwnerActionLedger",
      "ReprojectDecision",
      "DSARRequest"
     ],
     "application_services": [
      "ResolveOwnerAction",
      "ProcessDSAR"
     ],
     "infra_adapters": [
      "Email adapter"
     ],
     "public_interfaces": [
      "/compliance/*"
     ],
     "forbidden_deps": [
      "draft content"
     ]
    }
   ],
   "dependency_rules": [
    "Domain layer must not depend on infrastructure.",
    "Application layer may depend on domain.",
    "Infrastructure implements ports defined by application/domain.",
    "Interfaces call application services.",
    "Shared kernel must remain small (Ids, Money, Recipient, Actor).",
    "Contexts communicate through published events or explicit application APIs — never via direct database access to another context."
   ]
  },
  "security_governance": {
   "controls": [
    {
     "risk": "Prompt injection via customer input",
     "context": "AI Orchestration",
     "impact": "high",
     "control": "Input scrubber + OutputValidator + recipient-scoped retrieval",
     "audit": "AgentRun trace"
    },
    {
     "risk": "Cross-recipient retrieval leak",
     "context": "Knowledge Base",
     "impact": "severe",
     "control": "Per-recipient index partitions + RecipientIsolationSpec enforced at router",
     "audit": "Retrieval call log"
    },
    {
     "risk": "Signature spoofing",
     "context": "Quality Assurance",
     "impact": "severe",
     "control": "Signature bound to authenticated session; server-side validation",
     "audit": "Signature manifest"
    },
    {
     "risk": "Premature public claim",
     "context": "Compliance & Governance",
     "impact": "high",
     "control": "ReprojectReadinessSpec on OwnerActionLedger",
     "audit": "Reproject-decision log"
    },
    {
     "risk": "Privilege escalation",
     "context": "Identity & Access",
     "impact": "high",
     "control": "Roles in dedicated table + server-side checks + RLS",
     "audit": "Role assignment log"
    },
    {
     "risk": "Silent delivery failure",
     "context": "Client Delivery & Success",
     "impact": "medium",
     "control": "Adapter receipt required; alert customer within 1h on failure",
     "audit": "Delivery receipt archive"
    }
   ],
   "ai_governance": [
    "Every prompt version has a named owner + evaluator run + rollout flag",
    "AI outputs marked as suggestions until reviewer signoff",
    "Model + prompt inventory maintained in Ops console"
   ],
   "prompt_injection_defense": [
    "Strip / neutralize instruction-like patterns in customer inputs before prompt assembly",
    "Never concatenate raw customer input into a system prompt",
    "OutputValidator rejects outputs that reference forbidden actions"
   ],
   "sensitive_data_handling": [
    "PII scrubbed from logs",
    "Regulated data classes never sent to external model providers unless BAA/DPA covers it",
    "Per-recipient blob storage prefixes + signed URLs"
   ],
   "access_control_matrix": [
    {
     "role": "Customer operator",
     "context": "Service Fulfillment",
     "capabilities": [
      "OpenIntake",
      "AttachEvidence",
      "View own artifacts"
     ]
    },
    {
     "role": "Documentation analyst",
     "context": "Quality Assurance",
     "capabilities": [
      "ApproveArtifact",
      "RejectArtifact",
      "Co-sign retraction"
     ]
    },
    {
     "role": "Business owner",
     "context": "Compliance & Governance",
     "capabilities": [
      "ResolveOwnerAction",
      "Set reproject decision"
     ]
    },
    {
     "role": "Legal",
     "context": "Quality Assurance + Compliance",
     "capabilities": [
      "Co-sign retraction",
      "Handle DSAR"
     ]
    },
    {
     "role": "Ops",
     "context": "AI Orchestration",
     "capabilities": [
      "PublishPromptVersion",
      "Set confidence threshold"
     ]
    },
    {
     "role": "Platform admin",
     "context": "Identity & Access",
     "capabilities": [
      "Provision users",
      "Assign roles"
     ]
    }
   ],
   "audit_log_requirements": [
    "Append-only",
    "Actor + recipient + timestamp + command + before/after hash",
    "PII scrubbed",
    "Exportable per recipient on request (DSAR support)"
   ]
  },
  "observability": {
   "metrics": [
    {
     "metric": "Reviewer-signed artifacts / week / recipient",
     "type": "business",
     "context": "Service Fulfillment",
     "why": "North star: repeatable value delivery",
     "target": "≥ contracted cadence",
     "alert_threshold": "< 80% of contracted cadence"
    },
    {
     "metric": "AI draft acceptance rate",
     "type": "ai-quality",
     "context": "AI Orchestration",
     "why": "Signals grounding + prompt fit",
     "target": "≥ 70% by Phase 2",
     "alert_threshold": "< 50% weekly"
    },
    {
     "metric": "Escalation rate",
     "type": "ai-quality",
     "context": "AI Orchestration",
     "why": "Guardrails firing correctly",
     "target": "5-15%",
     "alert_threshold": "> 30% weekly"
    },
    {
     "metric": "Cycle time to signoff (p50 + p95)",
     "type": "operational",
     "context": "Quality Assurance",
     "why": "Reviewer throughput",
     "target": "p95 ≤ 5 business days",
     "alert_threshold": "> 5 business days"
    },
    {
     "metric": "Signoff-to-retraction ratio",
     "type": "risk",
     "context": "Quality Assurance",
     "why": "Correctness signal",
     "target": "< 1%",
     "alert_threshold": "any retraction week-over-week"
    },
    {
     "metric": "Delivery failure rate",
     "type": "reliability",
     "context": "Client Delivery & Success",
     "why": "Customer-facing reliability",
     "target": "< 0.5%",
     "alert_threshold": "> 1% daily"
    },
    {
     "metric": "Owner-action open count",
     "type": "business",
     "context": "Compliance & Governance",
     "why": "Public-reproject readiness",
     "target": "0 for launched blueprints",
     "alert_threshold": "any blocker aging > 30 days"
    },
    {
     "metric": "Model cost per artifact",
     "type": "financial",
     "context": "AI Orchestration",
     "why": "Margin control",
     "target": "≤ target per pricing model",
     "alert_threshold": "> 1.5× target"
    },
    {
     "metric": "Cross-recipient retrieval violation attempts",
     "type": "risk",
     "context": "Knowledge Base",
     "why": "Security invariant",
     "target": "0",
     "alert_threshold": "any > 0"
    },
    {
     "metric": "First-artifact time per recipient",
     "type": "customer",
     "context": "Client Onboarding & Profile",
     "why": "Activation",
     "target": "≤ 2 weeks",
     "alert_threshold": "> 4 weeks"
    }
   ],
   "dashboards": [
    "Operator dashboard",
    "Reviewer queue",
    "Delivery health",
    "AI cost + escalation",
    "Compliance blockers"
   ],
   "audit_reports": [
    "Per-recipient audit-log export",
    "Signature manifest export"
   ],
   "quality_review_reports": [
    "Reviewer calibration report",
    "Escalation-outcome report"
   ],
   "ai_evaluation_reports": [
    "Evaluator regression report",
    "Prompt-rollout diff"
   ],
   "client_outcome_reports": [
    "Artifacts delivered",
    "Cycle time",
    "Retraction rate"
   ]
  },
  "testing_strategy": {
   "tests": [
    {
     "type": "Domain unit",
     "validates": "Aggregate invariants",
     "context": "all core contexts",
     "example": "CompletenessPackAggregate rejects deliver without signoff"
    },
    {
     "type": "Aggregate invariant",
     "validates": "Consistency boundaries",
     "context": "Service Fulfillment / QA",
     "example": "Signed artifact is immutable"
    },
    {
     "type": "Policy",
     "validates": "Reactive rules",
     "context": "AI Orchestration",
     "example": "Escalates below confidence threshold"
    },
    {
     "type": "Specification",
     "validates": "Reusable rules",
     "context": "Compliance",
     "example": "ReprojectReadinessSpec blocks 'ready' with open owner actions"
    },
    {
     "type": "Application use-case",
     "validates": "End-to-end command flow",
     "context": "Fulfillment + QA",
     "example": "Deliver signed artifact happy path"
    },
    {
     "type": "Integration",
     "validates": "Adapter behavior",
     "context": "External Integrations",
     "example": "Stripe subscription webhook translates correctly"
    },
    {
     "type": "Contract",
     "validates": "Published-language event schemas",
     "context": "cross-context",
     "example": "DraftProduced payload matches consumer expectations"
    },
    {
     "type": "AI prompt eval",
     "validates": "Prompt quality vs golden dataset",
     "context": "AI Orchestration",
     "example": "Drafter accepts ≥ 40% in shadow mode"
    },
    {
     "type": "RAG retrieval",
     "validates": "Recipient isolation + coverage",
     "context": "Knowledge Base",
     "example": "Cross-recipient lookup returns zero rows"
    },
    {
     "type": "Golden dataset",
     "validates": "AI regression",
     "context": "AI Orchestration",
     "example": "No regression on past accepted artifacts"
    },
    {
     "type": "Human review simulation",
     "validates": "Escalation UX",
     "context": "QA",
     "example": "Reviewer can complete signoff in ≤ 5 clicks"
    },
    {
     "type": "End-to-end",
     "validates": "Critical path",
     "context": "all",
     "example": "Intake → signoff → delivery in staging"
    },
    {
     "type": "Security",
     "validates": "Auth + RLS + injection defense",
     "context": "Identity + AI Orchestration",
     "example": "Prompt-injection payload is neutralized"
    },
    {
     "type": "Regression",
     "validates": "No drift on prior fixes",
     "context": "all",
     "example": "Prior retraction bug does not reappear"
    }
   ],
   "critical_domain_rules": [
    "No delivery without signoff",
    "No AI output without OutputValidator pass",
    "No retrieval outside recipient partition",
    "No public-reproject flip with open blockers"
   ],
   "ai_eval_dataset": [
    "50 past reviewer-accepted artifacts per vertical (redacted)",
    "20 rejected drafts (ground truth for escalation)",
    "10 injection-payload cases"
   ],
   "regression_plan": "Every PR runs domain + policy + spec unit tests. Every prompt reproject runs Evaluator with regression gate. Weekly critical-path smoke test in staging.",
   "contract_testing_plan": "Published-language event schemas versioned in /shared/events; consumer tests run in CI against schema-version compatibility.",
   "manual_qa_checklist": [
    "Signoff flow: signature captured + timestamp + hash",
    "Retraction flow: co-sign captured + customer notified",
    "Delivery flow: receipt archived",
    "DSAR flow: export completes end-to-end"
   ]
  },
  "mvp_roadmap": [
   {
    "phase": "Phase 0 — Manual workflow with instrumented capture",
    "goal": "Deliver one artifact end-to-end manually, capture every step as a domain event.",
    "features": [
     "Manual intake form",
     "Evidence upload",
     "Human draft",
     "Reviewer signoff via signed form"
    ],
    "contexts": [
     "Sales & Intake",
     "Service Fulfillment",
     "Quality Assurance"
    ],
    "ai_needs": [],
    "human_workflows": [
     "Reviewer signoff"
    ],
    "data_needs": [
     "pack order",
     "control evidence",
     "recovery file"
    ],
    "integrations": [
     "Email"
    ],
    "risks": [
     "Un-audited manual step"
    ],
    "exit_criteria": [
     "1 real artifact delivered + reviewer-signed"
    ]
   },
   {
    "phase": "Phase 1 — AI-assisted drafting for internal use only",
    "goal": "Introduce Drafter Agent with reviewer gate; no customer-facing AI language.",
    "features": [
     "Drafter Agent (internal)",
     "OutputValidator",
     "Escalation route"
    ],
    "contexts": [
     "AI Orchestration",
     "Service Fulfillment"
    ],
    "ai_needs": [
     "Drafter, Classifier"
    ],
    "human_workflows": [
     "Escalation review"
    ],
    "data_needs": [
     "AgentRun",
     "PromptVersion"
    ],
    "integrations": [
     "frontier LLM providers"
    ],
    "risks": [
     "Prompt injection",
     "Grounding drift"
    ],
    "exit_criteria": [
     "AI draft acceptance rate ≥ 40% in shadow mode"
    ]
   },
   {
    "phase": "Phase 2 — Operator dashboard + owner-action ledger",
    "goal": "Make the workflow legible + governable for the owner.",
    "features": [
     "Operator dashboard",
     "Owner-action ledger",
     "Reproject-decision engine"
    ],
    "contexts": [
     "Compliance & Governance"
    ],
    "ai_needs": [],
    "human_workflows": [
     "Owner action resolution"
    ],
    "data_needs": [
     "OwnerActionLedger"
    ],
    "integrations": [
     "IdP"
    ],
    "risks": [
     "Ungoverned public claims"
    ],
    "exit_criteria": [
     "Reproject decisions computed from ledger"
    ]
   },
   {
    "phase": "Phase 3 — Client delivery portal",
    "goal": "Give customers a portal to see status + receive artifacts.",
    "features": [
     "Client portal",
     "Delivery adapter",
     "Revision workflow"
    ],
    "contexts": [
     "Client Delivery & Success"
    ],
    "ai_needs": [],
    "human_workflows": [
     "Success cadence"
    ],
    "data_needs": [
     "Delivery"
    ],
    "integrations": [
     "Email"
    ],
    "risks": [
     "Silent delivery failure"
    ],
    "exit_criteria": [
     "Delivery-failure alert within 1h"
    ]
   },
   {
    "phase": "Phase 4 — Automated QA + reporting",
    "goal": "Wire metrics, retraction runbook, and evaluator agent.",
    "features": [
     "Evaluator Agent",
     "Retraction workflow",
     "Dashboards"
    ],
    "contexts": [
     "Analytics & Reporting",
     "Quality Assurance"
    ],
    "ai_needs": [
     "Evaluator"
    ],
    "human_workflows": [
     "Retraction co-sign"
    ],
    "data_needs": [
     "Retraction"
    ],
    "integrations": [],
    "risks": [
     "Vanity metrics"
    ],
    "exit_criteria": [
     "North-star + guardrail metrics live"
    ]
   },
   {
    "phase": "Phase 5 — Scale + optimization",
    "goal": "Reduce cost per artifact, increase reviewer throughput.",
    "features": [
     "Prompt versioning UI",
     "Cost budgeting",
     "Multi-reviewer queue"
    ],
    "contexts": [
     "AI Orchestration",
     "Quality Assurance"
    ],
    "ai_needs": [
     "Cost meter"
    ],
    "human_workflows": [
     "Multi-reviewer routing"
    ],
    "data_needs": [],
    "integrations": [],
    "risks": [
     "Regression on rollout"
    ],
    "exit_criteria": [
     "Model cost per artifact ≤ target"
    ]
   }
  ],
  "scaling_roadmap": [
   {
    "stage": "≤ 5 recipients",
    "trigger": "Design-partner cohort",
    "architecture_change": "Single-region modular monolith + managed DB",
    "operational_change": "Founder-led ops; weekly working session",
    "risk": "Single-owner queue"
   },
   {
    "stage": "5-25 recipients",
    "trigger": "First paid conversions",
    "architecture_change": "Extract heaviest module (AI Orchestration) behind an internal queue; keep monolith",
    "operational_change": "Named on-call rotation; SOC 2 Type I scoping",
    "risk": "Reviewer bottleneck"
   },
   {
    "stage": "25-100 recipients",
    "trigger": "Multi-reviewer demand",
    "architecture_change": "Split AI Orchestration into its own service if throughput/isolation demands it; per-recipient retrieval sharding",
    "operational_change": "Dedicated success + prompt-ops roles",
    "risk": "Prompt version drift"
   },
   {
    "stage": "100+ recipients",
    "trigger": "Enterprise + regulated segments",
    "architecture_change": "Regional deployments; per-region data residency; segregated compliance environments",
    "operational_change": "Dedicated SRE + compliance team; SOC 2 Type II + framework additions",
    "risk": "Compliance framework demand exceeds team capacity"
   }
  ],
  "risk_register": [
   {
    "risk": "Disaster-event counsel-facing claim proves incorrect",
    "likelihood": "medium",
    "impact": "severe",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "Every claim linked to a cited source + reviewer signoff",
    "owner": "legal",
    "context": "Compliance & Governance"
   },
   {
    "risk": "AI hallucination in a delivered artifact",
    "likelihood": "medium",
    "impact": "high",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "Retrieval-first pipeline + structured output validation + reviewer gate",
    "owner": "engineering",
    "context": "AI Orchestration / Knowledge Base"
   },
   {
    "risk": "Cross-recipient data leak",
    "likelihood": "low",
    "impact": "severe",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "Row-level auth + per-recipient retrieval indices + log-scrubbing",
    "owner": "engineering",
    "context": "AI Orchestration / Knowledge Base"
   },
   {
    "risk": "Design partner churns before contract",
    "likelihood": "medium",
    "impact": "high",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "Weekly working-session cadence; documented value moments; owner-action ledger",
    "owner": "owner",
    "context": "Service Fulfillment"
   },
   {
    "risk": "Compliance framework demand exceeds team capacity",
    "likelihood": "high",
    "impact": "high",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "SOC 2 Type I year one; map controls once, evidence continuously",
    "owner": "ops",
    "context": "Compliance & Governance"
   },
   {
    "risk": "Single-region outage takes production down",
    "likelihood": "low",
    "impact": "high",
    "signal": "See ProductBlueprintDNA / risk register for tuned early-warning signals",
    "mitigation": "Multi-AZ managed database; nightly cross-region backup",
    "owner": "engineering",
    "context": "Service Fulfillment"
   }
  ],
  "adrs": [
   {
    "id": "ADR-001",
    "decision": "Architecture style",
    "status": "accepted",
    "context": "Single team, single regulated vertical per blueprint, evidence-linked workflow.",
    "options": [
     "Modular monolith",
     "Microservices",
     "Serverless workflow",
     "No-code first"
    ],
    "chosen": "Modular monolith with event-driven internals",
    "business_reason": "Ship a defensible vertical slice with one team; avoid distributed-systems cost until scale forces it.",
    "technical_reason": "Deterministic transactions across aggregates; simpler ops; one deployable.",
    "tradeoffs": [
     "May feel unsophisticated to enterprise reviewers",
     "Refactor cost if we later split"
    ],
    "risks": [
     "Module boundaries erode without discipline"
    ],
    "revisit_trigger": "Any single module needs independent scaling or team boundary."
   },
   {
    "id": "ADR-002",
    "decision": "Bounded context boundaries",
    "status": "accepted",
    "context": "Domain analysis above; distinct language groups for Fulfillment, AI Orchestration, QA, Compliance.",
    "options": [
     "Contexts as above",
     "One big 'app' context",
     "Contexts split by UI page"
    ],
    "chosen": "Contexts as above (domain-derived)",
    "business_reason": "Protects the reviewer signoff invariant + owner-action ledger + evidence spine as first-class boundaries.",
    "technical_reason": "Aggregates align to consistency boundaries; ACLs contain external mess.",
    "tradeoffs": [
     "More code organization discipline"
    ],
    "risks": [
     "Team tries to bypass ACL for speed"
    ],
    "revisit_trigger": "New subdomain emerges (e.g., self-serve marketplace)."
   },
   {
    "id": "ADR-003",
    "decision": "Database ownership",
    "status": "accepted",
    "context": "Modular monolith with shared Postgres; per-context schemas.",
    "options": [
     "One shared schema",
     "Schema per context",
     "DB per context"
    ],
    "chosen": "Schema per context in shared Postgres, cross-context reads only via published projections.",
    "business_reason": "Keeps operational cost low; enforces boundaries without paying multi-DB tax.",
    "technical_reason": "RLS + schema separation gives ownership clarity.",
    "tradeoffs": [
     "Discipline required to avoid cross-schema joins"
    ],
    "risks": [
     "Bypass joins for speed"
    ],
    "revisit_trigger": "A context needs independent scaling or residency."
   },
   {
    "id": "ADR-004",
    "decision": "AI orchestration strategy",
    "status": "accepted",
    "context": "Retrieval-first with structured-output validation + human gate.",
    "options": [
     "Open-ended chat",
     "Retrieval-first + validated",
     "Autonomous multi-agent"
    ],
    "chosen": "Retrieval-first + structured validation + reviewer gate",
    "business_reason": "Grounding + defensibility are the paid outcome.",
    "technical_reason": "OutputValidator gives a hard boundary before drafts leave AI Orchestration.",
    "tradeoffs": [
     "Slower than agentic chat"
    ],
    "risks": [
     "Prompt version regression"
    ],
    "revisit_trigger": "Evaluator shows a step-function accuracy gain from a new pattern."
   },
   {
    "id": "ADR-005",
    "decision": "Human review strategy",
    "status": "accepted",
    "context": "Regulated vertical; brand + legal risk on wrong outputs.",
    "options": [
     "No human review (fully automated)",
     "Sampling review",
     "Every-artifact review"
    ],
    "chosen": "Every-artifact review by named licensed reviewer",
    "business_reason": "Signoff is the trust primitive.",
    "technical_reason": "Signature bound to session; append-only log.",
    "tradeoffs": [
     "Reviewer throughput becomes the bottleneck"
    ],
    "risks": [
     "Reviewer burnout"
    ],
    "revisit_trigger": "Sustained low retraction rate + the applicant's counsel acceptance."
   },
   {
    "id": "ADR-006",
    "decision": "Integration strategy",
    "status": "accepted",
    "context": "External systems: recovery-ops management software, cost-documentation-study vendor formats, Airtable intake tracker, ...",
    "options": [
     "Direct API coupling",
     "Anti-corruption layer per system",
     "Middleware bus (Zapier/n8n)"
    ],
    "chosen": "Anti-corruption layer per system, owned by External Integrations context",
    "business_reason": "External schemas must never leak into the core.",
    "technical_reason": "Adapters translate + validate; upstream break contained.",
    "tradeoffs": [
     "More code than direct coupling"
    ],
    "risks": [
     "Adapter lag on upstream change"
    ],
    "revisit_trigger": "External system stability changes materially."
   },
   {
    "id": "ADR-007",
    "decision": "Modular monolith vs microservices",
    "status": "accepted",
    "context": "Same as ADR-001.",
    "options": [
     "Monolith",
     "Microservices"
    ],
    "chosen": "Monolith",
    "business_reason": "Team size and scale do not justify microservices cost.",
    "technical_reason": "Distributed transactions across signoff/delivery would be a nightmare early.",
    "tradeoffs": [
     "Refactor cost later"
    ],
    "risks": [
     "Cultural expectation drift"
    ],
    "revisit_trigger": "See ADR-001."
   },
   {
    "id": "ADR-008",
    "decision": "Build vs buy for generic subdomains",
    "status": "accepted",
    "context": "Billing, Identity, IdP, email.",
    "options": [
     "Build all",
     "Buy generics"
    ],
    "chosen": "Buy generics (Stripe, IdP, transactional email)",
    "business_reason": "Do not spend core-domain hours on solved categories.",
    "technical_reason": "Standard SDKs + well-documented failure modes.",
    "tradeoffs": [
     "Vendor risk"
    ],
    "risks": [
     "Vendor lock-in"
    ],
    "revisit_trigger": "Cost or reliability materially degrades."
   }
  ],
  "self_audit": {
   "scores": [
    {
     "category": "Domain accuracy",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Ubiquitous language quality",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Subdomain classification quality",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Bounded context clarity",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Core domain focus",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Context map quality",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Aggregate design quality",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Invariant quality",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "AI-agent responsibility design",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Human review safety",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Data ownership clarity",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Integration protection",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Implementation feasibility",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Scalability",
     "score": 7,
     "weakness": "Single-region; single-reviewer bottleneck; monolith split not planned.",
     "improvement": "Add per-recipient AI queue + multi-reviewer routing at Phase 2."
    },
    {
     "category": "Security and compliance",
     "score": 7,
     "weakness": "High-trust vertical needs Type II mapping and per-disaster event controls earlier.",
     "improvement": "Map controls at Phase 1; commit to Type II by Phase 3."
    },
    {
     "category": "Testing strategy",
     "score": 8,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    },
    {
     "category": "Operational realism",
     "score": 7,
     "weakness": "Founder-led ops assumed through Phase 2; brittle to key-person absence.",
     "improvement": "Document runbooks; cross-train success + prompt-ops role by Phase 2."
    },
    {
     "category": "MVP practicality",
     "score": 9,
     "weakness": "None material at this stage.",
     "improvement": "Maintain the current standard; re-audit after the first pilots land real data."
    }
   ],
   "weakest_parts": [
    "Scalability plan assumes single reviewer per recipient through Phase 2",
    "Operational realism depends on founder-led ops",
    "Compliance framework depth for Type II"
   ],
   "biggest_assumptions": [
    "The target audience will pay for evidence-linked, human-reviewed outputs over unverified AI generation.",
    "The workflow can be reconstructed from an owner-supplied evidence pack within one week per design partner.",
    "The vertical tolerates AI-assisted drafts when human review is explicit and audit-traceable."
   ],
   "highest_risk_decisions": [
    "Modular monolith (ADR-001)",
    "Every-artifact reviewer signoff (ADR-005)",
    "Anti-corruption layer per external system (ADR-006)"
   ],
   "needs_domain_expert": [
    "Documentation analyst to validate signoff workflow ergonomics",
    "Vertical SME on control evidence taxonomy"
   ],
   "needs_legal": [
    "Retraction workflow language",
    "DSAR SLA + the applicant's counsel-response runbook",
    "Public-claim policy for microsite content"
   ],
   "needs_prototype": [
    "Drafter Agent accuracy on 20-case golden dataset",
    "Reviewer signoff UX end-to-end in ≤ 5 minutes per artifact",
    "Per-recipient retrieval isolation test"
   ],
   "validate_before_prod": [
    "Named licensed reviewer + engagement letter on file",
    "Owner-action ledger populated per launch recipient",
    "OutputValidator false-negative rate acceptable",
    "Delivery failure alert path tested"
   ]
  },
  "final_recommendations": [
   "Ship a modular-monolith, evidence-linked, reviewer-gated vertical slice for Reoblige. Preserve the invariant that no recovery file leaves the system without Documentation analyst signoff. Do not launch commercially until owner-action facts close and at least one reviewer-signed recovery file is delivered.",
   "Do NOT default to microservices. Extract a module only when a specific pressure demands it.",
   "Do NOT allow AI outputs to leave AI Orchestration without OutputValidator pass and citation coverage.",
   "Do NOT ship any public claim on the Reoblige microsite while owner actions are open.",
   "Do NOT store roles on user/profile tables; use a dedicated roles table with server-side checks + RLS.",
   "DO wire the north-star + guardrail metrics before Phase 2 launch.",
   "DO capture every state transition as an append-only domain event; the audit trail is the product."
  ],
  "extensions": {
   "service_business_reality_check": {
    "is_service_business": true,
    "paid_outcome_clear": true,
    "workflow_present": true,
    "ai_native_fit_score": 8,
    "red_flags": []
   },
   "ai_native_fit": {
    "score": 8,
    "why": "Evidence-linked drafting + confidence-scored escalation is only economical with bounded AI orchestration. Pure-manual = uneconomic; pure-automated = undefensible.",
    "disqualifiers": [
     "High-trust vertical: cannot ship without licensed reviewer signoff"
    ]
   },
   "domain_evidence_register": [
    {
     "claim": "Reoblige paid outcome is a reviewer-signed artifact",
     "evidence_type": "primary",
     "source": "Business Understanding + subdomain 'Service Fulfillment'",
     "strength": "strong",
     "gaps": "Confirm with 3 design-partner interviews"
    },
    {
     "claim": "Reviewer signoff is legally / commercially required for defensibility",
     "evidence_type": "primary",
     "source": "Vertical shape + the applicant's counsel archetype",
     "strength": "strong",
     "gaps": "Vertical-specific attestation standard citation"
    },
    {
     "claim": "AI drafting materially reduces cycle time vs. pure manual",
     "evidence_type": "assumed",
     "source": "Category benchmark",
     "strength": "medium",
     "gaps": "Measure on internal golden dataset"
    },
    {
     "claim": "Customer will supply structured intake within SLA",
     "evidence_type": "assumed",
     "source": "Prospect conversations (unverified)",
     "strength": "weak",
     "gaps": "Run 5 intake dry-runs with design partners"
    },
    {
     "claim": "Per-recipient retrieval isolation prevents cross-recipient leakage",
     "evidence_type": "primary",
     "source": "Architecture (Knowledge Base context)",
     "strength": "strong",
     "gaps": "Add automated cross-recipient lookup test"
    },
    {
     "claim": "Owner-action ledger blocks premature public reproject",
     "evidence_type": "primary",
     "source": "Compliance & Governance context invariants",
     "strength": "strong",
     "gaps": "None"
    },
    {
     "claim": "Model + prompt versioning enables reproducible outputs",
     "evidence_type": "primary",
     "source": "AI Orchestration context",
     "strength": "strong",
     "gaps": "Evaluator regression thresholds not yet baselined"
    },
    {
     "claim": "Cycle-time reduction supports premium pricing",
     "evidence_type": "assumed",
     "source": "Pricing hypothesis",
     "strength": "medium",
     "gaps": "Test with 3 pricing conversations"
    }
   ],
   "assumption_register": [
    {
     "assumption": "The target audience will pay for evidence-linked, human-reviewed outputs over unverified AI generation.",
     "impact_if_wrong": "high",
     "how_to_validate": "Design-partner interview + measurement",
     "blocking": true
    },
    {
     "assumption": "The workflow can be reconstructed from an owner-supplied evidence pack within one week per design partner.",
     "impact_if_wrong": "high",
     "how_to_validate": "Design-partner interview + measurement",
     "blocking": true
    },
    {
     "assumption": "The vertical tolerates AI-assisted drafts when human review is explicit and audit-traceable.",
     "impact_if_wrong": "high",
     "how_to_validate": "Design-partner interview + measurement",
     "blocking": false
    },
    {
     "assumption": "Single-recipient per customer is not required for the first cohort — logical isolation with row-level auth is acceptable.",
     "impact_if_wrong": "medium",
     "how_to_validate": "Instrument metric + review after Phase 1",
     "blocking": false
    },
    {
     "assumption": "Manifest-backed blueprint reflects real customer workflow, not a synthetic scenario.",
     "impact_if_wrong": "medium",
     "how_to_validate": "Instrument metric + review after Phase 1",
     "blocking": false
    },
    {
     "assumption": "A licensed reviewer can be sourced and retained for this vertical",
     "impact_if_wrong": "severe",
     "how_to_validate": "Recruit + sign engagement letter before commercial launch",
     "blocking": true
    },
    {
     "assumption": "External systems expose stable APIs with predictable failure modes",
     "impact_if_wrong": "medium",
     "how_to_validate": "Adapter contract tests + failure-injection",
     "blocking": false
    }
   ],
   "language_conflict_map": [
    {
     "term": "Engagement",
     "meaning_a": "A signed billing contract",
     "context_a": "Billing & Revenue",
     "meaning_b": "An accepted unit of intake work",
     "context_b": "Sales & Intake",
     "resolution": "Billing owns 'Engagement'; Fulfillment uses vertical-specific intake noun."
    },
    {
     "term": "Approval",
     "meaning_a": "Customer accepts a delivered draft",
     "context_a": "Client Delivery",
     "meaning_b": "Reviewer signs an artifact",
     "context_b": "Quality Assurance",
     "resolution": "QA uses 'Signoff'; Delivery uses 'Customer approval'."
    },
    {
     "term": "Confidence",
     "meaning_a": "Model-assigned probability",
     "context_a": "AI Orchestration",
     "meaning_b": "Human legal/clinical confidence",
     "context_b": "Quality Assurance",
     "resolution": "Never conflate; always qualify (model_confidence vs reviewer_confidence)."
    }
   ],
   "build_buy_integrate": [
    {
     "subdomain": "Service Fulfillment (evidence-linked drafting + review)",
     "decision": "build",
     "reason": "This is what customers pay for and what counsel and owners inspect."
    },
    {
     "subdomain": "AI Orchestration (bounded agents + retrieval)",
     "decision": "build",
     "reason": "The AI-native competitive edge lives here; misuse here creates every high-severity risk."
    },
    {
     "subdomain": "Quality Assurance (reviewer signoff + retraction)",
     "decision": "build",
     "reason": "Signoff is the trust primitive of the whole business."
    },
    {
     "subdomain": "Sales & Intake",
     "decision": "build",
     "reason": "Feeds Fulfillment; not the differentiator, but if broken, nothing else runs."
    },
    {
     "subdomain": "Client Onboarding & Profile",
     "decision": "build",
     "reason": "One-time high-touch step per customer."
    },
    {
     "subdomain": "Client Delivery & Success",
     "decision": "build",
     "reason": "Customer-visible surface; drives retention."
    },
    {
     "subdomain": "Compliance & Governance",
     "decision": "build",
     "reason": "Cross-cuts every context; owns 'can we publicly claim this?'."
    },
    {
     "subdomain": "Billing & Revenue",
     "decision": "buy",
     "reason": "Solved category; do not build."
    },
    {
     "subdomain": "Identity & Access",
     "decision": "integrate",
     "reason": "Solved category."
    },
    {
     "subdomain": "Knowledge Base & Retrieval",
     "decision": "build",
     "reason": "Feeds AI Orchestration; poor retrieval = poor drafts."
    },
    {
     "subdomain": "Analytics & Reporting",
     "decision": "build",
     "reason": "Drives every operational decision."
    },
    {
     "subdomain": "External Integrations (Anti-Corruption Layer)",
     "decision": "build",
     "reason": "External schemas must never leak into the core."
    }
   ],
   "core_protection_strategy": [
    "Core contexts (Service Fulfillment, AI Orchestration, Quality Assurance) staffed before any generic subdomain work.",
    "Any change to a core aggregate requires a paired ADR + invariant test.",
    "Generic subdomains (Billing, Identity) are bought or integrated; never built in-house without a killer reason.",
    "Prompt-version rollout to core agents gated on Evaluator regression run.",
    "No feature flag may bypass the reviewer-signoff invariant."
   ],
   "boundary_stress_tests": [
    {
     "scenario": "Customer requests changes to a delivered artifact",
     "contexts_touched": [
      "Client Delivery",
      "Service Fulfillment",
      "Quality Assurance"
     ],
     "breaks_if": "Revision creates a new draft without re-triggering signoff",
     "verdict": "holds"
    },
    {
     "scenario": "Reviewer identity changes mid-engagement",
     "contexts_touched": [
      "Client Onboarding",
      "Quality Assurance"
     ],
     "breaks_if": "QA cached reviewer identity locally",
     "verdict": "adjust"
    },
    {
     "scenario": "External the applicant's counsel issues a new pack order",
     "contexts_touched": [
      "Compliance & Governance",
      "Knowledge Base"
     ],
     "breaks_if": "Retrieval index not reindexed within SLA",
     "verdict": "holds"
    },
    {
     "scenario": "Owner marks an action resolved that is actually not",
     "contexts_touched": [
      "Compliance & Governance"
     ],
     "breaks_if": "No re-verification step before reproject-decision flips",
     "verdict": "adjust"
    },
    {
     "scenario": "AI produces high-confidence draft with wrong citation",
     "contexts_touched": [
      "AI Orchestration",
      "Quality Assurance"
     ],
     "breaks_if": "OutputValidator does not check citation-to-claim linkage",
     "verdict": "holds"
    }
   ],
   "unresolved_ownership": [
    {
     "concept": "Reviewer engagement letter",
     "candidates": [
      "Client Onboarding",
      "Quality Assurance"
     ],
     "recommendation": "Own in Client Onboarding; QA references by id."
    },
    {
     "concept": "Public claim / marketing site content",
     "candidates": [
      "Compliance & Governance",
      "Client Delivery"
     ],
     "recommendation": "Compliance owns the reproject-decision; Delivery renders."
    },
    {
     "concept": "Model + prompt cost attribution",
     "candidates": [
      "AI Orchestration",
      "Billing & Revenue"
     ],
     "recommendation": "AI Orchestration owns raw run cost; Billing consumes rolled-up projections."
    }
   ],
   "published_language_contracts": [
    {
     "producer": "Sales & Intake",
     "consumer": "Service Fulfillment",
     "contract": "EngagementAccepted",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Service Fulfillment",
     "consumer": "Quality Assurance",
     "contract": "DraftReady, ArtifactSigned",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "AI Orchestration",
     "consumer": "Service Fulfillment",
     "contract": "DraftProduced, EscalationRaised",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Knowledge Base & Retrieval",
     "consumer": "AI Orchestration",
     "contract": "DocIngested, IndexRebuilt",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Client Onboarding & Profile",
     "consumer": "Service Fulfillment",
     "contract": "RecipientProvisioned, ReviewerRegistered",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Service Fulfillment",
     "consumer": "Client Delivery & Success",
     "contract": "ArtifactDelivered, DeliveryConfirmed",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Quality Assurance",
     "consumer": "Compliance & Governance",
     "contract": "RetractionFiled",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    },
    {
     "producer": "Client Delivery & Success",
     "consumer": "Billing & Revenue",
     "contract": "DeliveryConfirmed",
     "versioning": "SemVer on event schema; consumer contract tests in CI."
    }
   ],
   "shared_kernel_warnings": [
    "Shared kernel must remain small: Ids, Money, Recipient, Actor. Adding a domain concept here couples every context.",
    "Never share aggregates across contexts via shared kernel — publish an event or expose an application service.",
    "Any addition to /shared requires 2-context approval to prevent silent coupling."
   ],
   "aggregate_stress_tests": [
    {
     "aggregate": "PackOrderAggregate",
     "scenario": "Concurrent command on PackOrderAggregate",
     "invariant_at_risk": "Every claim in a delivered artifact cites evidence",
     "verdict": "holds"
    },
    {
     "aggregate": "CompletenessPackAggregate",
     "scenario": "Concurrent command on CompletenessPackAggregate",
     "invariant_at_risk": "A recovery file cannot be delivered without a valid Signoff",
     "verdict": "holds"
    },
    {
     "aggregate": "SignoffAggregate",
     "scenario": "Concurrent command on SignoffAggregate",
     "invariant_at_risk": "Signature bound to a live authenticated session, not a form field",
     "verdict": "holds"
    },
    {
     "aggregate": "RetractionAggregate",
     "scenario": "Concurrent command on RetractionAggregate",
     "invariant_at_risk": "A retraction requires Legal + Reviewer co-signature",
     "verdict": "holds"
    },
    {
     "aggregate": "AgentRunAggregate",
     "scenario": "Concurrent command on AgentRunAggregate",
     "invariant_at_risk": "No output emitted without OutputValidator pass",
     "verdict": "holds"
    }
   ],
   "agent_stress_tests": [
    {
     "agent": "Drafter Agent",
     "scenario": "Malformed / adversarial input to Drafter Agent",
     "failure_mode": "Prompt injection",
     "guardrail": "Structured-output schema",
     "verdict": "holds"
    },
    {
     "agent": "Classifier Agent",
     "scenario": "Malformed / adversarial input to Classifier Agent",
     "failure_mode": "Wrong route → wrong reviewer",
     "guardrail": "Structured-output schema",
     "verdict": "holds"
    },
    {
     "agent": "Evaluator Agent",
     "scenario": "Malformed / adversarial input to Evaluator Agent",
     "failure_mode": "Overfit to golden dataset",
     "guardrail": "Regression thresholds",
     "verdict": "holds"
    }
   ],
   "regulated_domain_handling": [
    {
     "regime": "FEMA SB23-206 (PAPPG V5 2 CFR 200 / §38-12-503)",
     "applies_because": "Packs draft statutory authorized representative documentation that condition the owner’s the warranty of eligibility (§38-12-503) assessment authority",
     "controls": [
      "Cited pack order per claim",
      "Compliance-officer signoff"
     ],
     "evidence_required": [
      "PackOrder-to-control map",
      "Documentation receipts"
     ]
    }
   ],
   "unit_economics": {
    "price_model": "Fixed fee per recovery file + seasonal disaster event retainer",
    "unit_of_value": "Reviewer-signed fema-public-assistance-recovery-engine artifact",
    "gross_margin_pct": 65,
    "cost_drivers": [
     "Reviewer hours per artifact",
     "AI model + retrieval cost",
     "External API + delivery cost",
     "Support + success"
    ],
    "breakeven_note": "Breakeven depends on analyst throughput and extraction acceptance; target 45–60 analyst minutes per pack by day 90 (blueprint band), 55–65% firm gross margin by year 1."
   },
   "margin_leakage_map": [
    {
     "leakage": "Reviewer over-editing AI drafts",
     "cause": "Low AI acceptance rate",
     "impact": "high",
     "mitigation": "Evaluator regression + prompt-owner accountability"
    },
    {
     "leakage": "External API retries without backoff",
     "cause": "Poor adapter design",
     "impact": "medium",
     "mitigation": "Exponential backoff + circuit breaker"
    },
    {
     "leakage": "Cross-recipient retrieval scan cost",
     "cause": "Missing partitioning",
     "impact": "high",
     "mitigation": "Per-recipient index partitions"
    },
    {
     "leakage": "Silent delivery failure absorbing support time",
     "cause": "No adapter receipts",
     "impact": "medium",
     "mitigation": "Adapter receipts + 1h SLA alert"
    }
   ],
   "slop_findings": [
    {
     "pattern": "generic 'dashboard'-only value prop",
     "status": "clean",
     "note": "Value prop is reviewer-signed artifact, not a dashboard."
    },
    {
     "pattern": "AI-as-magic",
     "status": "clean",
     "note": "AI is bounded to drafting + validation; humans own signoff."
    },
    {
     "pattern": "blockchain",
     "status": "clean",
     "note": "No blockchain-as-hype in derivation."
    },
    {
     "pattern": "agent-first (agents replace humans)",
     "status": "clean",
     "note": "Every agent has forbidden actions + human escalation."
    },
    {
     "pattern": "microservices by default",
     "status": "clean",
     "note": "ADR-001 chose modular monolith."
    },
    {
     "pattern": "everything-is-core",
     "status": "clean",
     "note": "Generic subdomains explicitly marked buy/integrate."
    }
   ],
   "drift_checks": [
    {
     "stage": "Business Truth Discovery",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Ubiquitous Language",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Strategic Subdomains",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Bounded Contexts",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Context Mapping",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Event Storming",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Commands/Events/Policies",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Tactical Model",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "AI Ops",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Human-in-the-Loop",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Evidence + Compliance",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Data Ownership",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Integration",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Application Use Cases",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Outcome Economics",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Technical Architecture",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Security + Governance",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Testing",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "MVP Roadmap",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Scaling",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Risk",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "ADRs",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Foundry Package",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Contradiction Scan",
     "status": "pass",
     "findings": []
    },
    {
     "stage": "Self-Audit",
     "status": "pass",
     "findings": []
    }
   ],
   "gates": [
    {
     "id": "domain",
     "title": "Domain Clarity",
     "passed": true,
     "checks": [
      {
       "name": "Paid outcome present",
       "ok": true,
       "evidence": "business_understanding.paid_outcome"
      },
      {
       "name": "≥3 actors identified",
       "ok": true,
       "evidence": "5 actors"
      }
     ]
    },
    {
     "id": "core",
     "title": "Core Domain",
     "passed": true,
     "checks": [
      {
       "name": "At least one core subdomain",
       "ok": true,
       "evidence": "Service Fulfillment (evidence-linked drafting + review), AI Orchestration (bounded agents + retrieval), Quality Assurance (reviewer signoff + retraction)"
      }
     ]
    },
    {
     "id": "boundary",
     "title": "Boundary",
     "passed": true,
     "checks": [
      {
       "name": "≥4 bounded contexts",
       "ok": true,
       "evidence": "11 contexts"
      },
      {
       "name": "Every context has owned language",
       "ok": true,
       "evidence": "all populated"
      }
     ]
    },
    {
     "id": "invariant",
     "title": "Invariant",
     "passed": true,
     "checks": [
      {
       "name": "≥4 business invariants",
       "ok": true,
       "evidence": "9 invariants"
      }
     ]
    },
    {
     "id": "ai-safety",
     "title": "AI Safety",
     "passed": true,
     "checks": [
      {
       "name": "Every agent has forbidden actions",
       "ok": true,
       "evidence": "yes"
      },
      {
       "name": "Every agent has escalation triggers",
       "ok": true,
       "evidence": "yes"
      }
     ]
    },
    {
     "id": "buildability",
     "title": "Buildability",
     "passed": true,
     "checks": [
      {
       "name": "MVP roadmap ≥2 phases",
       "ok": true,
       "evidence": "6 phases"
      }
     ]
    },
    {
     "id": "anti-slop",
     "title": "Anti-Slop",
     "passed": true,
     "checks": [
      {
       "name": "No slop patterns",
       "ok": true,
       "evidence": "slop_findings all clean/warn"
      },
      {
       "name": "No failing contradictions",
       "ok": true,
       "evidence": "8 findings"
      }
     ]
    }
   ],
   "contradiction_scan": [
    {
     "id": "INV-AGG-SignoffAggregate + RetractionAggregate",
     "severity": "warn",
     "message": "Invariant references aggregate 'SignoffAggregate + RetractionAggregate' not defined",
     "refs": [
      "SignoffAggregate + RetractionAggregate"
     ]
    },
    {
     "id": "INV-AGG-IndexShardAggregate",
     "severity": "warn",
     "message": "Invariant references aggregate 'IndexShardAggregate' not defined",
     "refs": [
      "IndexShardAggregate"
     ]
    },
    {
     "id": "INV-AGG-UserAggregate",
     "severity": "warn",
     "message": "Invariant references aggregate 'UserAggregate' not defined",
     "refs": [
      "UserAggregate"
     ]
    },
    {
     "id": "CMD-EVT-OpenIntake-IntakeRejected",
     "severity": "info",
     "message": "Command OpenIntake references event 'IntakeRejected' not present in domain_events",
     "refs": [
      "OpenIntake",
      "IntakeRejected"
     ]
    },
    {
     "id": "CMD-EVT-AttachEvidence-EvidenceRejected",
     "severity": "info",
     "message": "Command AttachEvidence references event 'EvidenceRejected' not present in domain_events",
     "refs": [
      "AttachEvidence",
      "EvidenceRejected"
     ]
    },
    {
     "id": "CMD-EVT-DeliverCompletenessPack-DeliveryFailed",
     "severity": "info",
     "message": "Command DeliverCompletenessPack references event 'DeliveryFailed' not present in domain_events",
     "refs": [
      "DeliverCompletenessPack",
      "DeliveryFailed"
     ]
    },
    {
     "id": "CMD-EVT-ResolveOwnerAction-OwnerActionRejected",
     "severity": "info",
     "message": "Command ResolveOwnerAction references event 'OwnerActionRejected' not present in domain_events",
     "refs": [
      "ResolveOwnerAction",
      "OwnerActionRejected"
     ]
    },
    {
     "id": "CMD-EVT-FileRetraction-RetractionRejected",
     "severity": "info",
     "message": "Command FileRetraction references event 'RetractionRejected' not present in domain_events",
     "refs": [
      "FileRetraction",
      "RetractionRejected"
     ]
    }
   ],
   "rubric": {
    "categories": [
     {
      "category": "Domain accuracy",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Ubiquitous language quality",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Subdomain classification quality",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Bounded context clarity",
      "score": 9,
      "min": 7,
      "passed": true
     },
     {
      "category": "Core domain focus",
      "score": 9,
      "min": 7,
      "passed": true
     },
     {
      "category": "Context map quality",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Aggregate design quality",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Invariant quality",
      "score": 9,
      "min": 7,
      "passed": true
     },
     {
      "category": "AI-agent responsibility design",
      "score": 9,
      "min": 7,
      "passed": true
     },
     {
      "category": "Human review safety",
      "score": 9,
      "min": 7,
      "passed": true
     },
     {
      "category": "Data ownership clarity",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Integration protection",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Implementation feasibility",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Scalability",
      "score": 7,
      "min": 7,
      "passed": true
     },
     {
      "category": "Security and compliance",
      "score": 7,
      "min": 7,
      "passed": true
     },
     {
      "category": "Testing strategy",
      "score": 8,
      "min": 7,
      "passed": true
     },
     {
      "category": "Operational realism",
      "score": 7,
      "min": 7,
      "passed": true
     },
     {
      "category": "MVP practicality",
      "score": 9,
      "min": 7,
      "passed": true
     }
    ],
    "pass": true,
    "average": 8.2
   },
   "foundry_package": {
    "version": "1.0.0",
    "checksum": "bec1171d",
    "counts": {
     "subdomains": 12,
     "bounded_contexts": 11,
     "aggregates": 8,
     "events": 8,
     "commands": 7,
     "policies": 5,
     "ai_agents": 3,
     "invariants": 9,
     "integrations": 4,
     "adrs": 8
    },
    "subset": {
     "subdomains": [
      "Service Fulfillment (evidence-linked drafting + review)",
      "AI Orchestration (bounded agents + retrieval)",
      "Quality Assurance (reviewer signoff + retraction)",
      "Sales & Intake",
      "Client Onboarding & Profile",
      "Client Delivery & Success",
      "Compliance & Governance",
      "Billing & Revenue",
      "Identity & Access",
      "Knowledge Base & Retrieval",
      "Analytics & Reporting",
      "External Integrations (Anti-Corruption Layer)"
     ],
     "bounded_contexts": [
      "Service Fulfillment",
      "AI Orchestration",
      "Quality Assurance",
      "Compliance & Governance",
      "Sales & Intake",
      "Client Onboarding & Profile",
      "Client Delivery & Success",
      "Knowledge Base & Retrieval",
      "Billing & Revenue",
      "Identity & Access",
      "Analytics & Reporting"
     ],
     "aggregates": [
      "PackOrderAggregate",
      "CompletenessPackAggregate",
      "SignoffAggregate",
      "RetractionAggregate",
      "AgentRunAggregate",
      "OwnerActionLedgerAggregate",
      "RecipientAggregate",
      "DeliveryAggregate"
     ],
     "events": [
      "packOrderAccepted",
      "EvidenceCollected",
      "DraftReady",
      "EscalationRaised",
      "ReviewerSigned",
      "ArtifactDelivered",
      "OwnerActionResolved",
      "RetractionFiled"
     ],
     "commands": [
      "OpenIntake",
      "AttachEvidence",
      "StartAgentRun",
      "ApproveArtifact",
      "DeliverCompletenessPack",
      "ResolveOwnerAction",
      "FileRetraction"
     ],
     "policies": [
      "Auto-request signoff on coverage complete",
      "Escalate on low confidence",
      "Block delivery on open compliance blocker",
      "Retract on material finding",
      "Alert on delivery failure"
     ],
     "ai_agents": [
      "Drafter Agent",
      "Classifier Agent",
      "Evaluator Agent"
     ],
     "invariants": [
      "A recovery file cannot be delivered without a valid Reviewer signoff.",
      "Every claim in a delivered artifact cites at least one evidence item.",
      "A signature is bound to a live authenticated session, not a form field.",
      "Signed artifacts are immutable; corrections go through Retraction.",
      "No AI output leaves AI Orchestration without OutputValidator pass.",
      "Retrieval is scoped to a single recipient partition per call.",
      "Reproject cannot flip to 'ready' with open blocking owner actions.",
      "Every recipient has at least one named reviewer with valid credential.",
      "Roles are stored in a dedicated table and checked server-side."
     ],
     "integrations": [
      "PM management software (Vantaca / CINC / AppFolio / TOPS)",
      "Cost-documentation-study vendor formats (major + regional preparers)",
      "Airtable intake tracker + Drive folder tree",
      "Frontier LLM APIs (provider-portable)"
     ],
     "adrs": [
      "ADR-001",
      "ADR-002",
      "ADR-003",
      "ADR-004",
      "ADR-005",
      "ADR-006",
      "ADR-007",
      "ADR-008"
     ]
    }
   }
  }
 },
 "ddd_coverage": {
  "slug": "fema-public-assistance-recovery-engine",
  "total": 20,
  "passed": 20,
  "pct": 100,
  "checks": [
   {
    "key": "actors",
    "label": "Actors",
    "count": 5,
    "min": 3,
    "ok": true,
    "gate": "domain",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "glossary",
    "label": "Glossary",
    "count": 8,
    "min": 6,
    "ok": true,
    "gate": "domain",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "decisions",
    "label": "Business decisions",
    "count": 5,
    "min": 4,
    "ok": true,
    "gate": "domain",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "events",
    "label": "Domain events",
    "count": 8,
    "min": 6,
    "ok": true,
    "gate": "domain",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "subdomains",
    "label": "Subdomains",
    "count": 12,
    "min": 8,
    "ok": true,
    "gate": "core",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "bcs",
    "label": "Bounded contexts",
    "count": 11,
    "min": 4,
    "ok": true,
    "gate": "boundary",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "ctx_map",
    "label": "Context map",
    "count": 11,
    "min": 3,
    "ok": true,
    "gate": "boundary",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "event_storm",
    "label": "Event storm rows",
    "count": 13,
    "min": 6,
    "ok": true,
    "gate": "boundary",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "aggregates",
    "label": "Aggregates",
    "count": 8,
    "min": 3,
    "ok": true,
    "gate": "invariant",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "invariants",
    "label": "Invariants",
    "count": 9,
    "min": 4,
    "ok": true,
    "gate": "invariant",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "ai_agents",
    "label": "AI agents",
    "count": 3,
    "min": 2,
    "ok": true,
    "gate": "ai-safety",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "use_cases",
    "label": "Use cases",
    "count": 3,
    "min": 3,
    "ok": true,
    "gate": "buildability",
    "unblock": "Not needed — check passes at current counts."
   },
   {
    "key": "evidence_reg",
    "label": "Evidence register",
    "count": 8,
    "min": 5,
    "ok": true,
    "gate": "domain",
    "unblock": "Attach or verify a domain-evidence claim (source + strength)."
   },
   {
    "key": "assumptions",
    "label": "Assumption register",
    "count": 7,
    "min": 4,
    "ok": true,
    "gate": "domain",
    "unblock": "Log and validate a blocking assumption in the evidence register."
   },
   {
    "key": "stress_boundary",
    "label": "Boundary stress tests",
    "count": 5,
    "min": 3,
    "ok": true,
    "gate": "boundary",
    "unblock": "Resolve an unresolved-ownership scenario before wiring boundary evidence."
   },
   {
    "key": "stress_agg",
    "label": "Aggregate stress tests",
    "count": 5,
    "min": 3,
    "ok": true,
    "gate": "invariant",
    "unblock": "Add or verify an aggregate invariant enforcement test."
   },
   {
    "key": "stress_agent",
    "label": "Agent stress tests",
    "count": 3,
    "min": 2,
    "ok": true,
    "gate": "ai-safety",
    "unblock": "Attach an AI-safety guardrail evidence item for the agent."
   },
   {
    "key": "gates_pass",
    "label": "Hard gates passing",
    "count": 7,
    "min": 7,
    "ok": true,
    "unblock": "One or more hard gates are failing — see failing gates below."
   },
   {
    "key": "rubric",
    "label": "Extended rubric pass",
    "count": 1,
    "min": 1,
    "ok": true,
    "gate": "buildability",
    "unblock": "Raise weakest rubric category by attaching evidence for the linked concern."
   },
   {
    "key": "foundry",
    "label": "Foundry package",
    "count": 11,
    "min": 4,
    "ok": true,
    "gate": "buildability",
    "unblock": "Foundry package under-populated — regenerate blueprint via GitHub sync."
   }
  ],
  "failingGates": []
 },
 "architecture": {
  "slug": "fema-public-assistance-recovery-engine",
  "archetypes": [
   "regulated system",
   "CRUD/workflow application",
   "internal operations platform"
  ],
  "archetype_impact": "Per-disaster event scope is a global query parameter — every read/write is scoped by disaster event + pack order window, not just recipient.",
  "personality": [
   "workflow-heavy",
   "cost-sensitive",
   "highly regulated",
   "highly secure"
  ],
  "forces_ranked": [
   {
    "force": "compliance",
    "why": "Regulated verticals gate reproject; the architecture must prove, not assert, compliance."
   },
   {
    "force": "auditability",
    "why": "Every reproject decision, every evidence toggle, must be defensible in review."
   },
   {
    "force": "reliability",
    "why": "A broken blueprint is a broken reproject gate — availability is a product feature."
   },
   {
    "force": "data integrity",
    "why": "Evidence is the product; a corrupted citation is a shipped defect."
   },
   {
    "force": "maintainability",
    "why": "One team maintains dozens of blueprints; the shape must be identical across them."
   }
  ],
  "tradeoffs": [
   "Prioritizing auditability slows raw throughput — accepted; the product IS the audit trail.",
   "Choosing a modular monolith trades independent scaling for a single deploy story — accepted while the team is small.",
   "Using managed Cloud primitives trades some portability for zero ops — accepted; data is portable, runtime is not the moat."
  ],
  "quality_scenarios": [
   {
    "attribute": "Performance (interactive p95)",
    "target": "600 ms on Blueprint detail routes",
    "assumption": "Measured from Cloud edge, warm cache."
   },
   {
    "attribute": "Availability",
    "target": "99.5% (with documentation-window freeze protection)",
    "assumption": "Rolling 30-day window; excludes announced maintenance."
   },
   {
    "attribute": "RTO",
    "target": "24h"
   },
   {
    "attribute": "RPO",
    "target": "24h (daily backups)"
   },
   {
    "attribute": "Latency (edge function warm)",
    "target": "≤ 800ms p95 excluding upstream AI calls"
   },
   {
    "attribute": "Data durability",
    "target": "11 nines via managed Postgres + storage replication"
   },
   {
    "attribute": "Security",
    "target": "OWASP ASVS L1 baseline"
   },
   {
    "attribute": "Auditability",
    "target": "100% of reproject decisions + evidence toggles logged with actor + timestamp"
   },
   {
    "attribute": "Maintainability",
    "target": "New blueprint reaches validation-microsite state in ≤ 1 working session"
   },
   {
    "attribute": "Deployment frequency",
    "target": "≥ 5 deploys/week without incident"
   },
   {
    "attribute": "Observability",
    "target": "Every edge function emits correlationId; retries + phases visible in diagnostics drawer"
   },
   {
    "attribute": "Cost envelope",
    "target": "Idle per-blueprint cost ≈ $0; active < $5/month at MVP traffic"
   },
   {
    "attribute": "Scalability",
    "target": "Horizontal by blueprint count; single blueprint sized for < 10 req/s sustained"
   }
  ],
  "options": [
   {
    "style": "simple monolith",
    "fits_when": "Single team, low traffic, no independent scaling concerns.",
    "fits_here": "Matches the per-blueprint scope — one microsite, one schema, one code path.",
    "wrong_here": "Would couple every blueprint into a single deploy — not acceptable at network scale.",
    "complexity": "low",
    "cost": "low",
    "ops_burden": "low",
    "security_impact": "Small surface, single audit boundary.",
    "scaling_path": "Vertical scale only; hits ceiling on team velocity, not compute.",
    "team_fit": "Ideal for one dev; fine at MVP.",
    "recommended": false
   },
   {
    "style": "modular monolith",
    "fits_when": "Multiple bounded contexts but shared deploy lifecycle acceptable.",
    "fits_here": "Each blueprint is a module inside the network shell; shared shell, isolated data.",
    "wrong_here": "Wrong only if a blueprint needs independent SLOs — none currently do.",
    "complexity": "moderate",
    "cost": "low",
    "ops_burden": "low",
    "security_impact": "Single trust boundary; row-level isolation carries the tenancy load.",
    "scaling_path": "Modules become services only when SLOs or teams diverge.",
    "team_fit": "Best fit for a small team maintaining many blueprints.",
    "recommended": true
   },
   {
    "style": "serverless",
    "fits_when": "Bursty, per-request workloads with idle-to-zero cost targets.",
    "fits_here": "Edge functions already handle sync, docs, legal, seed articles, integrity — pay-per-invoke.",
    "wrong_here": "Wrong for long-running orchestrations; IDLE_TIMEOUT already bit us on legal docs.",
    "complexity": "moderate",
    "cost": "low",
    "ops_burden": "moderate",
    "security_impact": "Function-scoped IAM; secrets via managed vault.",
    "scaling_path": "Auto; watch cold-start p95 and per-invocation cost.",
    "team_fit": "Good — team already ships functions weekly.",
    "recommended": false
   },
   {
    "style": "microservices",
    "fits_when": "Multiple teams, divergent SLOs, independent reproject cadence required.",
    "fits_here": "Nothing here justifies it; single team, single deploy cadence, shared data plane.",
    "wrong_here": "Adds network, discovery, deploy topology, and observability cost with zero product benefit.",
    "complexity": "very high",
    "cost": "high",
    "ops_burden": "high",
    "security_impact": "Bigger attack surface, more inter-service auth to get right.",
    "scaling_path": "Best-in-class if the org can afford it.",
    "team_fit": "Wrong for this team.",
    "recommended": false
   },
   {
    "style": "event-driven",
    "fits_when": "Async fan-out, decoupled producers/consumers, replayable history required.",
    "fits_here": "Only the sync + integrity pipeline is fan-out; keep it as background jobs, not a broker.",
    "wrong_here": "Broker + schema registry + DLQ topology is overkill for current volumes.",
    "complexity": "high",
    "cost": "moderate",
    "ops_burden": "high",
    "security_impact": "Extra ACLs; message-level auth needed.",
    "scaling_path": "Excellent for future audit-log fan-out, revisit at 10x volume.",
    "team_fit": "Team can operate a small in-process queue; not a full broker yet.",
    "recommended": false
   },
   {
    "style": "workflow/orchestration",
    "fits_when": "Long, multi-step, resumable pipelines with human-in-the-loop steps.",
    "fits_here": "Blueprint pipeline (sources → articles → integrity → smoke test) already smells like this.",
    "wrong_here": "Full engine (Temporal/Airflow) is heavy; a typed in-app queue with retries covers today's needs.",
    "complexity": "high",
    "cost": "moderate",
    "ops_burden": "moderate",
    "security_impact": "Central choke point — must be hardened.",
    "scaling_path": "Adopt engine once we cross ~10 concurrent long-running jobs per blueprint.",
    "team_fit": "Would require operator ramp-up.",
    "recommended": false
   }
  ],
  "chosen_style": "modular monolith",
  "chosen_rationale": "Modular monolith with edge functions for bursty AI/generation — one audit boundary, low ops burden, easy per-team ownership.",
  "rejected": [
   {
    "style": "microservices",
    "why_rejected": "Adds network, discovery, deploy topology, and observability cost with zero product benefit."
   },
   {
    "style": "event-driven",
    "why_rejected": "Broker + schema registry + DLQ topology is overkill for current volumes."
   }
  ],
  "target": {
   "overview": "React shell → Lovable Cloud (Postgres + Auth + Storage + Edge Functions). Every blueprint is a module inside the shell; per-vertical differences live in derived DNA, not in separate deploys. Compliance posture: Domain-specific (agency documentation, attestation signers, retention schedules).",
   "frontend": "Vite + React + TypeScript + Tailwind + shadcn primitives; per-blueprint themed via Design DNA; job queue for background pipelines; URL-persisted filter state on audit + diagnostics.",
   "backend": "Deno-based edge functions per capability. Long generations split into per-item endpoints to stay under IDLE_TIMEOUT.",
   "data": "Managed Postgres with RLS + JSONB for shape drift. Object storage for source files + generated artifacts.",
   "api": "REST-ish RPC over edge functions with typed payloads; correlationId on every call for retry/diagnostics.",
   "authn_authz": "Managed OAuth (Google default). Roles in a dedicated user_roles table + has_role() SECURITY DEFINER function referenced by RLS policies.",
   "integrations": "GitHub (public read for sync + sources), Lovable AI Gateway (all LLM calls), Cloud Storage (artifacts). No third-party CRM/email yet.",
   "background_jobs": "blueprintJobQueue in-app: per-slug concurrency limit, exponential backoff + jitter, cancel + invalidate, retention of last error diagnostics.",
   "object_storage": "Cloud Storage buckets scoped per blueprint slug; signed URLs for artifact download.",
   "notifications": "In-app toasts + audit trail entries. Email/webhook deferred until owners request it.",
   "search": "Postgres FTS on blueprint titles + evidence claims; client-side filter for audit trail. Dedicated index deferred.",
   "analytics": "Lightweight event log in Postgres; dashboard-grade analytics deferred until we have a paying recipient.",
   "ai": "not applicable",
   "observability": "correlationId per request, per-phase timings, retry timeline in diagnostics drawer, per-blueprint pipeline status panel, JSON report export.",
   "deployment": "Preview + Production environments; edge functions deploy with the app; Postgres migrations shipped via managed migration tool.",
   "security": "RLS on every public table; roles in user_roles; secrets in managed vault; OWASP ASVS L1 baseline.",
   "dr": "Daily backups; restore drill twice/year."
  },
  "modules": [
   {
    "name": "Blueprint Core",
    "responsibility": "Owns the SeedBusiness catalog, reproject decisions, evidence register, owner actions.",
    "owned_data": [
     "seed business rows",
     "reproject_decision",
     "evidence items",
     "owner-action state"
    ],
    "entities": [
     "SeedBusiness",
     "EvidenceItem",
     "OwnerAction",
     "ReprojectDecision"
    ],
    "interfaces": [
     "React store (StoreProvider)",
     "public read via microsite route"
    ],
    "depends_on": [
     "Content Pipeline (for source files + articles)",
     "Cloud auth"
    ],
    "events_produced": [
     "reproject.decision.changed",
     "evidence.status.changed",
     "owner.action.resolved"
    ],
    "events_consumed": [
     "sync.blueprint.applied",
     "integrity.check.completed"
    ],
    "failure_risks": [
     "Duplicate slug in seed → React key crash (mitigated by dedupe in mergedSeed)",
     "Evidence drift after sync"
    ],
    "scaling": "Bounded by SEED size; irrelevant even at 10x.",
    "future_split_trigger": "Split out Blueprint Core into an independent deployment when its throughput or a distinct scaling profile justifies it; not warranted pre-revenue."
   },
   {
    "name": "Content Pipeline",
    "responsibility": "Fetches GitHub sources, generates docs/seed articles, runs citation integrity, per slug with concurrency + backoff.",
    "owned_data": [
     "blueprint_sources",
     "blueprint_seed_articles",
     "job status per slug",
     "integrity results"
    ],
    "entities": [
     "SourceFile",
     "SeedArticle",
     "IntegrityReport",
     "JobState"
    ],
    "interfaces": [
     "blueprintJobQueue API",
     "edge functions: fetch-blueprint-sources, generate-seed-articles, generate-blueprint-docs"
    ],
    "depends_on": [
     "Cloud edge functions",
     "AI Gateway",
     "GitHub public read"
    ],
    "events_produced": [
     "sources.fetched",
     "articles.generated",
     "integrity.completed",
     "cache.invalidated"
    ],
    "events_consumed": [
     "blueprint.cache.invalidate"
    ],
    "failure_risks": [
     "Edge IDLE_TIMEOUT on long generations (mitigated: per-doc endpoints + retries)",
     "Upstream AI 5xx storms"
    ],
    "scaling": "Concurrency + backoff configurable in UI; scales with edge function limits.",
    "future_split_trigger": "If cross-blueprint queueing coordination is needed, promote to a shared job service."
   },
   {
    "name": "Runtime & Capabilities",
    "responsibility": "Per-blueprint runtime modules — verification, SEO, legal docs, chatbot — with retry + diagnostic history.",
    "owned_data": [
     "capability status per slug",
     "runtime module errors",
     "chatbot threads + FAQ"
    ],
    "entities": [
     "CapabilityStatus",
     "RuntimeError",
     "ChatMessage"
    ],
    "interfaces": [
     "React Runtime tab",
     "edge functions: verify-blueprint, generate-seo-posts, generate-legal-docs/*, blueprint-chat"
    ],
    "depends_on": [
     "Content Pipeline (grounding)",
     "AI Gateway"
    ],
    "events_produced": [
     "capability.status.changed",
     "runtime.error.recorded"
    ],
    "events_consumed": [
     "cache.invalidated"
    ],
    "failure_risks": [
     "AI provider outage",
     "Prompt drift causing ungrounded output"
    ],
    "scaling": "Per-slug; independent of network size.",
    "future_split_trigger": "Split out Runtime & Capabilities into an independent deployment when its throughput or a distinct scaling profile justifies it; not warranted pre-revenue."
   },
   {
    "name": "Sync & Rollback",
    "responsibility": "Daily GitHub sync of blueprint definitions with dry-run, partial-apply, and server-backed rollback of last snapshot.",
    "owned_data": [
     "sync_runs",
     "sync_snapshots per slug",
     "audit_trail"
    ],
    "entities": [
     "SyncRun",
     "SyncDiff",
     "SyncSnapshot",
     "AuditEntry"
    ],
    "interfaces": [
     "/github-sync page",
     "edge functions: github-sync-blueprints, rollback-blueprint-sync"
    ],
    "depends_on": [
     "Blueprint Core",
     "Cloud storage for snapshots"
    ],
    "events_produced": [
     "sync.run.completed",
     "sync.blueprint.applied",
     "sync.blueprint.rolled_back"
    ],
    "events_consumed": [],
    "failure_risks": [
     "Partial apply leaving mixed state (mitigated by per-blueprint snapshots)",
     "Audit trail size growth"
    ],
    "scaling": "Paginate audit trail; snapshot retention window is finite.",
    "future_split_trigger": "Split out Sync & Rollback into an independent deployment when its throughput or a distinct scaling profile justifies it; not warranted pre-revenue."
   },
   {
    "name": "Design & Architecture DNA",
    "responsibility": "Deterministic per-blueprint design + architecture briefs used to gate reproject readiness.",
    "owned_data": [
     "derived only — no persistence"
    ],
    "entities": [
     "DesignDNA",
     "ArchitectureDNA"
    ],
    "interfaces": [
     "React panels in Business Detail"
    ],
    "depends_on": [
     "Blueprint Core"
    ],
    "events_produced": [],
    "events_consumed": [],
    "failure_risks": [
     "Vertical → profile drift if new verticals are not mapped"
    ],
    "scaling": "Pure functions; free.",
    "future_split_trigger": "Split out Design & Architecture DNA into an independent deployment when its throughput or a distinct scaling profile justifies it; not warranted pre-revenue."
   }
  ],
  "data_architecture": {
   "primary_db": "Managed Postgres (Cloud)",
   "secondary": [
    "Object storage for artifacts + snapshots",
    "Client localStorage for UI state (filters, drawer state) — never for auth"
   ],
   "cache": "React Query + module-level memoization; no dedicated cache service.",
   "search": "Postgres FTS on titles + evidence; consider pg_trgm on slugs.",
   "vector": "not applicable",
   "object_storage": "Per-slug prefixes; lifecycle rules to prune stale sync snapshots.",
   "schema_strategy": "Normalized core + JSONB for evolving shapes (evidence details, capability status).",
   "migrations": "Forward-only migrations reviewed in PR; every CREATE TABLE ships GRANTs + RLS enable + policies in the same migration.",
   "backups": "Managed daily backups with 30-day retention.",
   "retention": "Audit trail retained ≥ 1y; sync snapshots retained 90d; error diagnostics retained 30d.",
   "audit_logs": "audit_trail table + append-only pattern; export CSV from UI.",
   "soft_delete": "Soft-delete evidence via status transition; hard-delete only via owner-initiated purge.",
   "privacy": "Only owner-supplied facts persist; documentation, attestations, the applicant's counsel correspondence handled per vertical policy.",
   "encryption": "TLS 1.2+ in transit; AES-256 at rest via managed storage.",
   "multi_tenancy": "Row-level tenancy keyed on auth.uid() + blueprint slug; RLS policies enforce isolation."
  },
  "api": {
   "style": "REST-ish RPC over edge functions with JSON payloads; typed client wrappers.",
   "public_vs_internal": "Public microsite reads via Postgres RLS-protected queries; internal capability calls via authenticated edge functions.",
   "versioning": "Version via function name suffix (v1, v2) when breaking; additive changes preferred.",
   "rate_limiting": "Per-user + per-slug in edge functions; UI-level concurrency caps for AI calls.",
   "idempotency": "Sync + rollback carry an idempotency key; retries safe.",
   "pagination": "Cursor pagination on audit trail; offset paging tolerated on small lists.",
   "error_format": "{ code, message, correlationId, retryable, details? } — normalized in client.",
   "webhook_security": "HMAC-signed webhooks (deferred until we accept inbound webhooks).",
   "retries": "Exponential backoff + jitter, capped attempts, respect idempotency keys.",
   "contract_testing": "Zod schemas shared between client + edge; smoke test runner exercises each endpoint.",
   "backward_compat": "Additive fields only; deprecations announced in audit trail before removal.",
   "contract_testing_plan": "Intake, source-result, and delivery payload schemas are contract-tested per consumer; the JSON contract between AI layers is schema-pinned and versioned."
  },
  "security": {
   "authn": "Managed OAuth (Google default). Session in httpOnly cookie / managed client storage.",
   "authz": "user_roles table + has_role() SECURITY DEFINER, referenced from RLS policies. Never store roles on profiles.",
   "tenant_isolation": "RLS on every public table; every query filters by auth.uid() or by an explicit owner grant.",
   "secrets": "Managed vault; never in client bundle; edge functions read via runtime env.",
   "encryption": "TLS in transit; AES-256 at rest; column-level encryption only when regulation requires.",
   "session": "Short-lived access tokens + refresh rotation; SSR cookie parity for edge routes.",
   "input_validation": "Zod schemas at the edge boundary; reject on unknown fields.",
   "api_protection": "Rate limits + WAF rules on public endpoints; correlationId logging for abuse forensics.",
   "audit_log": "Every reproject decision, evidence toggle, sync, and rollback records actor + timestamp + before/after.",
   "admin_access": "Admin actions gated behind role check + two-key confirmation on destructive operations.",
   "supply_chain": "Lockfile pinning + weekly dependency scan; SBOM produced on reproject.",
   "threat_model": [
    "Prompt injection via ingested source files → sanitize + refuse instructions from ingested content.",
    "Cross-recipient read via missing RLS on new table → migration checklist blocks merge.",
    "Rollback abuse to overwrite recent legitimate edits → rollback preview + confirm-typed pattern.",
    "AI cost DOS by repeated regeneration → per-slug rate limits + concurrency cap."
   ],
   "abuse_cases": [
    "Malicious owner uploads privileged content into a public microsite field.",
    "Sync run tampered with to inject a slug that overlaps a real blueprint.",
    "Attacker triggers regeneration loop to drive AI cost."
   ],
   "zero_trust": "Every service call authenticates; no implicit trust between edge functions.",
   "asvs_notes": "OWASP ASVS L1 baseline."
  },
  "reliability": {
   "failure_modes": [
    "Edge function IDLE_TIMEOUT on long AI generations.",
    "Upstream AI provider 5xx / rate limit.",
    "GitHub API rate limit during sync.",
    "Postgres connection saturation during sync fan-out."
   ],
   "graceful_degradation": "Runtime tab modules degrade independently; microsite serves cached last-known-good content when generation fails.",
   "retry_policy": "Exponential backoff + jitter, max 5 attempts, respect Retry-After.",
   "timeouts": "Edge function ≤ 120s wall clock (safety margin under 150s limit); client fetch ≤ 60s per call.",
   "circuit_breaker": "Client-side per-endpoint breaker: after 3 consecutive IDLE_TIMEOUTs, pause 5m and surface to UI.",
   "queueing": "In-app blueprintJobQueue with concurrency limits per slug.",
   "idempotency": "Sync + rollback idempotent via key; generation endpoints idempotent per (slug, doc_key).",
   "dlq": "Failed jobs recorded in error diagnostics; user re-triggers manually (no auto-DLQ needed at current volume).",
   "transactions": "Multi-row writes wrapped in single transaction; audit entry written in the same transaction as the mutation.",
   "dr": "Daily backup + semi-annual restore drill.",
   "incident_response": "correlationId in every log line; on-call runbook per capability module; smoke test replays post-incident.",
   "slos": [
    {
     "name": "Interactive p95",
     "target": "600 ms on blueprint detail"
    },
    {
     "name": "Availability",
     "target": "99.5% (with documentation-window freeze protection)"
    },
    {
     "name": "Sync success rate",
     "target": "≥ 99% per daily run over rolling 7 days"
    },
    {
     "name": "Generation success rate",
     "target": "≥ 95% per doc across last 7d (excludes provider outages)"
    }
   ]
  },
  "scaling": {
   "mvp_can_stay_simple": [
    "Single Postgres, single region.",
    "No dedicated search or vector index.",
    "In-app job queue; no message broker."
   ],
   "modular_now": [
    "Content Pipeline is already isolated behind blueprintJobQueue — future extraction is a 1-day job.",
    "Runtime capabilities are one function per module — swap in isolation."
   ],
   "deferrable": [
    "Workflow engine (Temporal/Airflow).",
    "Vector DB / RAG.",
    "Multi-region replication.",
    "Feature flag service (env-based toggle covers MVP)."
   ],
   "breaks_first": "Edge function IDLE_TIMEOUT under multi-doc generation — already addressed by per-doc endpoints; watch for regression.",
   "db_path": "Vertical scale → read replica → partition by recipient if a single recipient dominates load.",
   "jobs_path": "In-app queue → dedicated worker → workflow engine, gated by concurrency + resumability need.",
   "cache_path": "React Query only → HTTP cache headers → CDN edge cache for microsite content.",
   "search_path": "Postgres FTS → pg_trgm → dedicated search only when p95 breaches SLO.",
   "files_path": "Managed object storage → CDN → per-region cache if traffic warrants.",
   "api_path": "Vertical edge function scale → per-capability autoscaling → extract hot module to its own service.",
   "multi_region": "Not planned; introduce only on customer contract with residency requirement.",
   "cost_control": "Per-blueprint AI recovery, concurrency cap, smoke-test cache; monthly cost review with per-blueprint attribution."
  },
  "ai": {
   "provider": "Frontier LLM via API with provider-agnostic prompt contracts; a second vendor is configured for failover so a reprojectd deliverable never depends on a single model.",
   "prompt_mgmt": "Extraction, drafting, and matrix prompts are held in versioned files with eval-gated deploys and one-step rollback; prompt changes require diff review.",
   "rag": "A versioned, jurisdiction-scoped rule pack for applicant / residential recovery cost-documentation compliance is retrieved with source-scoped filters; drafting is grounded and citation-anchored to the source text, never free-form generation.",
   "vector": "Not warranted pre-revenue — the rule pack is small and structured, so section/keyword lookups suffice until a larger corpus justifies similarity search.",
   "embeddings": "Deferred with the vector store; rule-pack keys are structured (element, source, subsection), not semantic.",
   "eval": "A gold set of specialist-reprojectd files measures element-extraction F1 and completeness-gate agreement per model reproject; accuracy vs specialist labels is reviewed on a fixed cadence.",
   "hitl": "Specialist reproject is never automated; a domain expert signs off on the exception queue, with sampling QA on a fraction of outputs and expert red-team on the first reprojects.",
   "guardrails": "Field-locked templates, source-tie reconciliation, and completeness rules mean a draft missing a required field emits a MISSING_ELEMENT exception rather than inventing content.",
   "prompt_injection": "Source documents are treated as data, never instructions; the red-team suite includes injected-instruction files disguised as legitimate inputs.",
   "leakage": "Client and subject identifiers are scoped per case; retrieval is scoped per client; provider training-use is disabled; there is no cross-client corpus.",
   "fallback": "A manual specialist workbench runbook plus the second LLM vendor keep production moving if the primary model is unavailable.",
   "latency_cost": "Inference cost per deliverable is bounded at launch and trends down with volume; the standard SLA leaves generous headroom over model latency.",
   "memory": "Agents are stateless per case; durable knowledge lives in the versioned rule pack and SOP library, not in model memory.",
   "tool_permissions": "The prompt runner has no tool access beyond returning JSON; search ordering, document assembly, and delivery are deterministic code.",
   "auditability": "Every prompt+output pair is logged to the per-case audit trail with version tags alongside the specialist reproject record.",
   "citation": "Every drafted element carries the source provision it satisfies, and every matrix entry carries the search or record it came from."
  },
  "devops": {
   "environments": [
    "Preview (per branch)",
    "Production"
   ],
   "cicd": "Lovable build pipeline; deploys on merge; edge functions ship atomically with the app.",
   "iac": "Cloud managed; migrations + config in-repo.",
   "secrets": "Managed vault; separate values per environment.",
   "preview_envs": "Automatic per branch; seeded with anonymized fixtures.",
   "migrations": "Forward-only; migrations reviewed for GRANT + RLS + policies; every table gated by the migration checklist.",
   "rollback": "App: redeploy previous build. Data: server-backed rollback per blueprint via rollback-blueprint-sync.",
   "release_style": "Continuous deploy with feature flags; canary only when a change touches shared shell.",
   "feature_flags": "Env-based booleans at MVP; consider a flag service when we have > 20 flags in flight.",
   "monitoring": "Cloud platform metrics + per-function logs + client error reporting.",
   "alerting": "SLO burn-rate alerts + IDLE_TIMEOUT rate alert + AI cost anomaly alert.",
   "logs": "Structured JSON with correlationId; retained per platform defaults.",
   "error_tracking": "Client-side error capture wired to console + in-app diagnostics drawer.",
   "uptime": "Synthetic checks on microsite + shell login every 5 minutes.",
   "cost_monitoring": "Per-blueprint cost view; alert on 3x baseline over 24h."
  },
  "testing": {
   "unit": "Vitest for pure derivations (DNA, business helpers).",
   "integration": "Edge function contract tests with recorded fixtures.",
   "contract": "Zod schemas shared client + edge; smoke test runner as continuous contract check.",
   "e2e": "Playwright against localhost preview for critical flows (sign in, evidence toggle, sync apply).",
   "security": "Weekly dependency scan; RLS policy audit script; abuse-case checklist per reproject.",
   "a11y": "Axe checks + keyboard-only smoke on shell components; WCAG 2.2 AA target.",
   "load": "k6 scenarios against edge functions before enabling a new capability network-wide.",
   "chaos": "Manual fault injection on AI provider (simulate 500s) during reproject rehearsal.",
   "migration": "Every migration runs in preview + dry-run on prod snapshot before apply.",
   "backup_restore": "Semi-annual restore drill.",
   "ai_eval": "not applicable",
   "test_data": "Deterministic fixtures per vertical; no real PHI/PII ever in fixtures."
  },
  "observability": {
   "logs": "Structured JSON with correlationId, phase, attempt, doc_key, slug.",
   "metrics": "Per-endpoint latency, error rate, retry count, AI token spend.",
   "traces": "Cross-function trace via correlationId propagation.",
   "audit_events": "Reproject decision, evidence toggle, sync, rollback, cache invalidation.",
   "business_events": "Blueprint promoted to ready, first microsite view, first customer-visible export.",
   "error_tracking": "In-app diagnostics drawer + persistent per-slug error history.",
   "security_monitoring": "Failed auth + rate-limit breach + admin action logs.",
   "cost_monitoring": "Per-blueprint + per-capability cost attribution.",
   "dashboards": [
    "SLO burn",
    "AI cost per blueprint",
    "Sync success rate",
    "Generation success rate"
   ],
   "alert_thresholds": [
    "IDLE_TIMEOUT rate > 3/day for one blueprint.",
    "Sync run failure > 1 in rolling 7 days.",
    "AI cost > 3x rolling 7-day baseline over 24h.",
    "p95 breach on Blueprint detail > 800ms for 15 min."
   ],
   "triage": "correlationId → diagnostics drawer → retry timeline → JSON report export → runbook link."
  },
  "cost": {
   "drivers": [
    {
     "name": "AI generation",
     "note": "Dominant driver; capped by concurrency + per-slug recovery."
    },
    {
     "name": "Edge function invocations",
     "note": "Bursty at sync + generation; idle-to-zero otherwise."
    },
    {
     "name": "Managed Postgres",
     "note": "Small; scales with audit trail retention."
    },
    {
     "name": "Object storage",
     "note": "Snapshots + artifacts; lifecycle rules prevent growth."
    },
    {
     "name": "Bandwidth",
     "note": "Low; static microsite content."
    }
   ],
   "likely_traps": [
    "Regeneration loops on failure (mitigated by circuit breaker).",
    "Audit trail unbounded growth (mitigated by retention policy).",
    "Storing large HTML snapshots per sync (mitigated by delta snapshots)."
   ],
   "controls": [
    "Per-blueprint AI recovery with hard cap.",
    "Smoke-test result caching in localStorage.",
    "Concurrency cap in blueprintJobQueue.",
    "Retention policy on audit + diagnostics."
   ]
  },
  "multi_tenancy": {
   "model": "Row-level tenancy: one shared Postgres, recipient scope by auth.uid() + blueprint slug.",
   "isolation": "RLS policies on every public table; policies reference has_role() where role checks are needed.",
   "tenant_aware_authz": "Every query filters by auth.uid(); admin overrides go through explicit role check + audit entry.",
   "tenant_config": "Per-slug config stored as JSONB on the blueprint row; no per-recipient deploy.",
   "branding": "Per-blueprint Design DNA drives theme; no runtime branding upload at MVP.",
   "tenant_export": "Owner can export evidence + audit trail as JSON/CSV from the UI.",
   "tenant_deletion": "Owner-initiated purge cascades across blueprint rows + storage prefix; soft-delete window of 30 days.",
   "tenant_audit": "Per-slug audit trail table view with actor + timestamp on every mutation.",
   "noisy_neighbor": "Per-slug concurrency cap in blueprintJobQueue; per-slug AI recovery.",
   "tenant_rate_limits": "Edge functions apply per-slug + per-user rate limits.",
   "billing": "Not billed at MVP; per-blueprint cost attribution feeds the future billing model.",
   "why_this_fits": "Team size and blueprint scale don't justify schema/db-per-recipient; RLS covers the isolation requirement with negligible ops burden."
  },
  "privacy_compliance": {
   "data_classification": "Owner-supplied facts and evidence citations are the sensitive classes; documentation, attestations, the applicant's counsel correspondence per vertical.",
   "minimization": "Only owner-supplied facts persist; no third-party enrichment; no PII scraping.",
   "consent": "Consent captured at intake for owner-supplied contact info; microsite visitors get standard cookie/consent banner where required.",
   "access_logs": "Every admin + edge function invocation logged with correlationId + actor.",
   "audit_trails": "Immutable append-only audit_trail table; export from UI.",
   "retention": "Audit ≥ 1y; sync snapshots 90d; error diagnostics 30d; artifacts per lifecycle rule.",
   "legal_hold": "Deferred until a matter requires it.",
   "right_to_delete": "Owner-initiated purge honored within 30 days; downstream copies pruned by lifecycle rules.",
   "right_to_export": "JSON + CSV export for evidence, audit trail, and generated artifacts.",
   "sensitive_handling": "No PHI/PII in prompts; owner-supplied facts only; secrets in managed vault.",
   "boundaries": "Domain-specific (agency documentation, attestation signers, retention schedules)",
   "residency": "Single region at MVP; residency contract triggers per-recipient residency planning.",
   "vendor_risk": "Lovable Cloud + AI Gateway are the only critical vendors; both reviewed for security posture.",
   "breach_response": "correlationId + audit trail enables scope determination; documentation per compliance policy within statutory window.",
   "admin_controls": "Admin actions gated by role check + two-key confirm for destructive operations; every admin session logged.",
   "evidence_collection": "Access reviews, change management, restore drills produce artifacts filed into the evidence pipeline."
  },
  "frontend": {
   "framework": "React 18 + Vite + TypeScript.",
   "rendering": "SPA with per-route code-split; microsite routes prerender-friendly.",
   "routing": "react-router-dom v6 with URL-persisted filter/drawer state.",
   "state": "React context + useSyncExternalStore for the job queue; localStorage only for UI state, never for auth.",
   "server_state": "@tanstack/react-query for cache + retries.",
   "forms": "Controlled components + Zod validation on submit; RHF only where forms grow.",
   "error_handling": "Error boundary at shell + per-panel skeletons + retry affordances.",
   "components": "shadcn primitives + per-blueprint themed panels; deterministic Design DNA drives look.",
   "design_system": "Tailwind semantic tokens (index.css); no hardcoded color utilities in components.",
   "auth_ui": "Managed OAuth callback via Cloud client; session hydration before protected routes render.",
   "authz_aware_ui": "UI hides actions the current role cannot perform; server-side check is authoritative.",
   "a11y": "WCAG 2.2 AA target; visible focus rings; keyboard shortcuts in diagnostics drawer.",
   "i18n": "Copy budgets assume +35% expansion for DE/FR; Intl APIs for dates/currencies.",
   "performance": "Route-level code split; lazy-load Runtime tab; memoize DNA derivations.",
   "bundling": "Vite defaults; per-route lazy imports for heavy panels.",
   "testing": "Vitest for unit; Playwright for critical flows.",
   "offline": "Not required; last-known-good served from React Query cache.",
   "realtime": "Not required at MVP; audit trail is polled on interaction."
  },
  "backend": {
   "framework": "Deno-based edge functions on Lovable Cloud, one function per capability.",
   "layering": "Handler → validator (Zod) → service → repository → Postgres.",
   "domain": "Blueprint, Evidence, OwnerAction, SyncRun, RuntimeCapability, ChatMessage.",
   "services": "Pure functions kept out of edge boundary; shared logic imported from a common module.",
   "repositories": "Thin Postgres wrappers; RLS enforces recipient scope.",
   "validation": "Zod at the edge boundary; reject unknown fields.",
   "authorization": "has_role() SECURITY DEFINER in Postgres; edge function also asserts role for defense in depth.",
   "jobs": "In-app blueprintJobQueue on the client for user-triggered pipelines; server-side cron only for daily sync.",
   "events": "Domain events emitted to audit_trail; no external broker.",
   "files": "Signed URLs from Cloud Storage; virus scan on upload (deferred until user uploads exist).",
   "email_sms": "Deferred; owner-configured inbox required before enabling outbound mail.",
   "scheduled": "Daily GitHub sync via scheduled function; retention prune weekly.",
   "errors": "Normalized error envelope { code, message, correlationId, retryable, details? }.",
   "logging": "Structured JSON logs with correlationId, phase, attempt, slug.",
   "config": "Env-based; secrets from managed vault.",
   "di": "Not required at current size; explicit imports.",
   "testing": "Contract tests per function with recorded fixtures + smoke-test runner."
  },
  "diagrams": {
   "context_mermaid": "flowchart LR\n  Owner([Blueprint Owner]) --> Shell[Network Shell]\n  Reviewer([Reviewer]) --> Shell\n  Public([Public Visitor]) --> Micro[Public Microsite fema-public-assistance-recovery-engine]\n  Shell --> Cloud[(Lovable Cloud: DB + Auth + Storage + Edge)]\n  Cloud --> AI[[AI Gateway]]\n  Cloud --> GH[[GitHub API]]\n  Micro --> Cloud",
   "container_mermaid": "flowchart TB\n  subgraph Client\n    UI[React Shell + Blueprint Detail]\n    Queue[blueprintJobQueue]\n  end\n  subgraph Cloud[Lovable Cloud]\n    DB[(Postgres + RLS)]\n    Store[(Object Storage)]\n    subgraph Edge[Edge Functions]\n      Sync[github-sync-blueprints]\n      Roll[rollback-blueprint-sync]\n      Src[fetch-blueprint-sources]\n      Seed[generate-seed-articles]\n      Docs[generate-blueprint-docs]\n      Legal[generate-legal-docs/*]\n      Verify[verify-blueprint]\n      SEO[generate-seo-posts]\n      Chat[blueprint-chat]\n    end\n  end\n  UI --> DB\n  Queue --> Src\n  Queue --> Seed\n  UI --> Docs\n  UI --> Legal\n  UI --> Verify\n  UI --> SEO\n  UI --> Chat\n  UI --> Sync\n  UI --> Roll\n  Seed --> AI[[AI Gateway]]\n  Docs --> AI\n  Legal --> AI\n  Chat --> AI\n  Src --> GH[[GitHub]]",
   "data_flow_mermaid": "flowchart LR\n  A[Owner edits Evidence] --> B[Store: evidence.custom]\n  B --> C{Reproject Gate}\n  C -- ready --> D[Business marked Ready]\n  C -- blocker --> E[Owner Actions queue]\n  F[GitHub Sync] --> G[Diff + Snapshot]\n  G --> H[(Postgres)]\n  H --> I[Audit trail]\n  H --> J[React store]",
   "auth_flow_mermaid": "sequenceDiagram\n  participant U as User\n  participant UI as Network Shell\n  participant Auth as Cloud Auth\n  participant API as Edge Function\n  participant DB as Postgres+RLS\n  U->>UI: sign in\n  UI->>Auth: OAuth (Google)\n  Auth-->>UI: session (JWT)\n  UI->>API: call with JWT\n  API->>DB: query as auth.uid()\n  DB-->>API: rows filtered by RLS\n  API-->>UI: response",
   "authz_flow_mermaid": "flowchart LR\n  Req[Request w/ JWT] --> Fn[Edge Function]\n  Fn --> Role[has_role user_id, role]\n  Role --> DB[(user_roles + RLS policies)]\n  DB -- allow --> Ok[Return rows]\n  DB -- deny --> Err[403 + audit entry]",
   "deployment_mermaid": "flowchart LR\n  Dev[Developer] --> Repo[Git]\n  Repo --> CI[Lovable Build]\n  CI --> Preview[Preview Env]\n  CI --> Prod[Production]\n  Prod --> Cloud[(Lovable Cloud)]\n  Prod --> CDN[[Edge CDN]]",
   "background_job_mermaid": "flowchart LR\n  UI[Blueprint Detail] --> Enq[blueprintJobQueue.enqueue]\n  Enq --> Slot{Concurrency slot?}\n  Slot -- yes --> Run[Run job]\n  Slot -- no --> Queued[queued]\n  Run -->|success| Done[Persist result + emit event]\n  Run -->|error| Back[Exponential backoff + jitter]\n  Back -->|attempts left| Run\n  Back -->|exhausted| Fail[Record diagnostic + expose retry button]",
   "event_flow_mermaid": "flowchart LR\n  Sync[sync.blueprint.applied] --> Core[Blueprint Core]\n  Integ[integrity.completed] --> UI\n  CacheInv[cache.invalidated] --> Pipe[Content Pipeline]\n  Pipe --> Sources[sources.fetched]\n  Sources --> Articles[articles.generated]\n  Articles --> Integ",
   "failure_flow_mermaid": "flowchart LR\n  Call[Edge Function call] --> Timeout{Timeout / 5xx?}\n  Timeout -- no --> Ok[Success]\n  Timeout -- yes --> Retry[Backoff + retry]\n  Retry --> Cap{Attempts cap?}\n  Cap -- no --> Call\n  Cap -- yes --> Breaker[Open circuit]\n  Breaker --> Cache[Serve last-known-good]\n  Breaker --> Owner[Surface diagnostic + owner action]",
   "multi_tenant_flow_mermaid": "flowchart LR\n  Owner1([Owner A]) --> UI\n  Owner2([Owner B]) --> UI\n  UI --> API[Edge Function w/ JWT]\n  API --> Policy{RLS: auth.uid + slug scope}\n  Policy -- match --> Rows[Owner-scoped rows]\n  Policy -- no match --> Deny[403]",
   "ai_flow_mermaid": "graph LR; SRC[Source documents as DATA]-->EX[Extract + normalize]-->SR[Order source searches]-->MTX[Build matrix]-->DR[Draft locked-field elements]-->GT[Deterministic completeness gates]-->SP[Specialist reproject]-->DL[Deliver]; GT-.exception.->SP; SP-.high-risk.->EXP[Expert review]"
  },
  "adrs": [
   {
    "id": "ADR-001",
    "decision": "Adopt modular monolith as the network-wide architecture style",
    "context": "Small team maintaining many blueprints with shared shell, evidence discipline, and per-vertical trust variation.",
    "options": [
     "simple monolith",
     "modular monolith",
     "microservices",
     "serverless-only",
     "hybrid"
    ],
    "chosen": "modular monolith",
    "why": "Preserves a single audit boundary and deploy cadence while allowing edge functions for burst workloads.",
    "consequences": [
     "Shared deploy lifecycle across blueprints",
     "Row-level recipient isolation carries the security load"
    ],
    "risks": [
     "A rogue blueprint can regress network shell performance"
    ],
    "reversal": "Extract a module to its own deploy only when its SLO diverges from the network shell.",
    "revisit_when": "A blueprint acquires a divergent SLO, a second team joins, or the shell deploy time exceeds 10 minutes."
   },
   {
    "id": "ADR-002",
    "decision": "Managed Postgres as the sole primary datastore",
    "context": "All entities are relational (blueprints, evidence, sync runs, articles, audit).",
    "options": [
     "Postgres",
     "Postgres + DocumentDB",
     "Postgres + vector DB",
     "Firestore"
    ],
    "chosen": "Postgres (Cloud managed) with JSONB for semi-structured fields",
    "why": "Relational integrity + row-level security satisfies audit, tenancy, and reporting; JSONB absorbs shape drift.",
    "consequences": [
     "RLS policies are the primary tenancy control",
     "Full-text search via Postgres FTS until it stops scaling"
    ],
    "risks": [
     "Complex joins under growth"
    ],
    "reversal": "Introduce a read-replica or a dedicated search index only when p95 breaches SLO.",
    "revisit_when": "FTS p95 > SLO for 2 consecutive weeks, or a genuine RAG surface appears."
   },
   {
    "id": "ADR-003",
    "decision": "Per-document edge functions for long-running AI generation",
    "context": "IDLE_TIMEOUT (150s) on monolithic legal-docs generator forced this split.",
    "options": [
     "Single long function",
     "Chunked per-doc functions",
     "Background job with polling"
    ],
    "chosen": "Per-document endpoints with client-side fan-out + retries",
    "why": "Keeps each invocation under the timeout, isolates failures, enables partial success reporting.",
    "consequences": [
     "More endpoints to maintain",
     "Client must own orchestration"
    ],
    "risks": [
     "Client back-pressure if fan-out is too wide"
    ],
    "reversal": "Move to a real workflow engine when we cross ~10 concurrent long jobs per blueprint.",
    "revisit_when": "Concurrent long-running jobs > 10 per blueprint, or client-side orchestration becomes buggy."
   },
   {
    "id": "ADR-004",
    "decision": "Evidence-first reproject gate",
    "context": "Vertical compliance posture: Domain-specific (agency documentation, attestation signers, retention schedules).",
    "options": [
     "Owner-declared ready",
     "Auto-ready via checklist",
     "Evidence-gated ready"
    ],
    "chosen": "Evidence-gated ready — reproject requires resolved owner actions + verified evidence",
    "why": "Regulated verticals cannot ship on self-declaration; evidence provides defensibility.",
    "consequences": [
     "Slower path to ready",
     "Higher confidence at ready"
    ],
    "risks": [
     "Owners abandon incomplete blueprints"
    ],
    "reversal": "Introduce a 'ready-with-caveats' state only if the network stalls on this gate.",
    "revisit_when": "> 30% of blueprints stuck in owner-action state for > 30 days."
   },
   {
    "id": "ADR-005",
    "decision": "Defer AI adoption until a specific evidence-generation need arises",
    "context": "AI is powerful but adds cost, latency, and auditability burden.",
    "options": [
     "No AI",
     "Grounded AI only",
     "Agentic AI"
    ],
    "chosen": "No AI in this vertical",
    "why": "Vertical does not currently justify AI-shaped complexity.",
    "consequences": [
     "No prompt catalog to maintain"
    ],
    "risks": [],
    "reversal": "Introduce AI only for a scoped generation task.",
    "revisit_when": "A specific generation task appears with clear source grounding."
   },
   {
    "id": "ADR-006",
    "decision": "Managed OAuth (Google) with roles in a dedicated user_roles table",
    "context": "Storing roles on the profile row invites privilege-escalation bugs; RLS policies must reference a stable role source.",
    "options": [
     "Roles on profiles",
     "user_roles + has_role() SECURITY DEFINER",
     "External IdP with JIT claims"
    ],
    "chosen": "user_roles table + has_role() SECURITY DEFINER, referenced by RLS",
    "why": "Prevents recursive RLS, isolates authz decisions, satisfies audit review.",
    "consequences": [
     "One extra join in policies",
     "Explicit role grants required"
    ],
    "risks": [
     "Role drift if grants are not audited"
    ],
    "reversal": "Swap SECURITY DEFINER function for an IdP claim without changing policies.",
    "revisit_when": "Enterprise SSO / SAML contract signed, or role count exceeds ~10."
   },
   {
    "id": "ADR-007",
    "decision": "Single-recipient per blueprint slug with row-level isolation",
    "context": "Blueprints share infra but must never cross-read evidence, sync history, or generated artifacts.",
    "options": [
     "Shared DB + RLS",
     "Schema-per-recipient",
     "DB-per-recipient"
    ],
    "chosen": "Shared DB + RLS keyed on auth.uid() and blueprint slug",
    "why": "Simplest operable model at current scale; migration cost stays near zero.",
    "consequences": [
     "RLS is load-bearing security"
    ],
    "risks": [
     "A missing policy = a leak"
    ],
    "reversal": "Extract a specific recipient to its own schema when contract requires it.",
    "revisit_when": "First enterprise customer with a residency or dedicated-DB clause."
   }
  ],
  "roadmap": [
   {
    "phase": "MVP",
    "build": [
     "Network shell + Blueprint Core module",
     "Content Pipeline with concurrency + backoff",
     "Design + Architecture DNA per blueprint",
     "Sync + rollback + audit trail"
    ],
    "avoid": [
     "Any per-blueprint deploy pipeline",
     "Message brokers",
     "Vector DBs",
     "Multi-region"
    ],
    "defer": [
     "A workflow engine",
     "Full-text search infra",
     "Dedicated CDN rules"
    ],
    "monitor": [
     "Edge function IDLE_TIMEOUT rate",
     "AI cost per generation",
     "Duplicate-slug regressions"
    ],
    "triggers_to_change": [
     "p95 breach on Blueprint detail > 800ms",
     "≥ 3 IDLE_TIMEOUTs/day sustained"
    ],
    "acceptable_debt": [
     "Client-owned job orchestration",
     "localStorage-backed UI state"
    ],
    "dangerous_debt": [
     "Missing RLS on any public table",
     "Ungrounded AI in customer-visible surfaces"
    ]
   },
   {
    "phase": "Stabilization",
    "build": [
     "Automated smoke test per blueprint on cache invalidation",
     "Per-slug retention + audit trail export",
     "Contract tests for every edge function"
    ],
    "avoid": [
     "Premature module extraction"
    ],
    "defer": [
     "Multi-recipient admin console"
    ],
    "monitor": [
     "SLO burn rate",
     "Cost per blueprint per week"
    ],
    "triggers_to_change": [
     "A single blueprint accounts for > 30% of AI spend"
    ],
    "acceptable_debt": [
     "Manual runbook execution for rare failures"
    ],
    "dangerous_debt": [
     "Untested rollback path",
     "Backups without a restore drill"
    ]
   },
   {
    "phase": "Growth",
    "build": [
     "Optional workflow engine adapter behind the current queue interface",
     "Read replica for Postgres if analytics queries interfere",
     "Feature flags per capability module"
    ],
    "avoid": [
     "Splitting Blueprint Core into services without SLO justification"
    ],
    "defer": [
     "Real-time collaboration"
    ],
    "monitor": [
     "Fan-out concurrency vs edge function limits"
    ],
    "triggers_to_change": [
     "> 10 concurrent long jobs per blueprint",
     "New team joins with independent reproject cadence"
    ],
    "acceptable_debt": [
     "Env-based feature flags"
    ],
    "dangerous_debt": [
     "Skipping migration reviews",
     "Unaudited role grants"
    ]
   },
   {
    "phase": "Scale",
    "build": [
     "Extract Content Pipeline to a dedicated service if it dominates deploys",
     "Search index (Postgres FTS → dedicated) once FTS p95 breaches SLO"
    ],
    "avoid": [
     "Microservices per blueprint"
    ],
    "defer": [
     "Multi-region until a customer contract requires it"
    ],
    "monitor": [
     "DB CPU + IO under peak",
     "Search p95"
    ],
    "triggers_to_change": [
     "Regional compliance contract signed"
    ],
    "acceptable_debt": [
     "Single-region deployment"
    ],
    "dangerous_debt": [
     "Unbounded audit trail growth",
     "Missing DR drill evidence"
    ]
   },
   {
    "phase": "Enterprise/Compliance",
    "build": [
     "Formal SOC 2 evidence pipeline (access reviews, change management)",
     "Recipient-scoped encryption keys where regulation requires",
     "DR drill quarterly with restore proof"
    ],
    "avoid": [
     "Custom compliance frameworks; ride managed platform attestations"
    ],
    "defer": [
     "FedRAMP unless a customer commits"
    ],
    "monitor": [
     "Access review completion",
     "Restore-test success rate"
    ],
    "triggers_to_change": [
     "Signed contract with SOC 2 clause",
     "PHI/PII scope change"
    ],
    "acceptable_debt": [
     "Manual quarterly access review with checklist"
    ],
    "dangerous_debt": [
     "Ad-hoc admin access without approval trail"
    ]
   }
  ],
  "anti_overengineering": {
   "flagged": [
    {
     "item": "Introducing Kubernetes",
     "why": "Team size + workload shape don't justify it.",
     "simpler": "Managed Cloud primitives."
    },
    {
     "item": "Adopting microservices",
     "why": "Single deploy cadence + shared audit boundary.",
     "simpler": "Modular monolith with edge functions."
    },
    {
     "item": "Adopting a vector DB",
     "why": "Sources are small + structured; deterministic retrieval works.",
     "simpler": "Direct source fetch + Postgres FTS."
    },
    {
     "item": "Adopting event sourcing",
     "why": "Audit trail table already provides the needed reconstructibility.",
     "simpler": "Append-only audit_trail + snapshots."
    },
    {
     "item": "Multi-region from day one",
     "why": "No customer contract requires it.",
     "simpler": "Single region + documented DR plan."
    },
    {
     "item": "Custom workflow engine",
     "why": "In-app queue covers current concurrency needs.",
     "simpler": "blueprintJobQueue with backoff."
    },
    {
     "item": "Premature message queue",
     "why": "In-app queue + audit trail cover the fan-out cases.",
     "simpler": "Keep blueprintJobQueue; revisit at 10x volume."
    },
    {
     "item": "Custom auth",
     "why": "Managed OAuth + user_roles cover the model.",
     "simpler": "Cloud Auth + user_roles table."
    },
    {
     "item": "Premature caching layer",
     "why": "React Query covers the read-heavy paths.",
     "simpler": "React Query + HTTP cache headers."
    },
    {
     "item": "Data warehouse",
     "why": "No analytics contract; Postgres analytics queries suffice.",
     "simpler": "Read replica if the primary is hurt."
    }
   ]
  },
  "risks": [
   {
    "risk": "Edge function IDLE_TIMEOUT on long generations",
    "likelihood": "moderate",
    "impact": "high",
    "mitigation": "Per-document endpoints + client-side retries with exponential backoff.",
    "detection": "Smoke test runner + diagnostics drawer flags IDLE_TIMEOUT.",
    "owner": "engineering",
    "escalation": "Sustained > 3/day for one blueprint → open incident.",
    "fallback": "Fall back to last-known-good cached artifact; pause auto-generation for the affected blueprint.",
    "category": "technical"
   },
   {
    "risk": "Duplicate slugs in SEED causing UI regressions",
    "likelihood": "moderate",
    "impact": "moderate",
    "mitigation": "mergedSeed dedupes by slug; add lint on SEED at build time.",
    "detection": "React duplicate-key warning; per-slug uniqueness assertion in tests.",
    "owner": "engineering",
    "escalation": "Ship-block if reproduced on main.",
    "fallback": "Runtime dedupe in mergedSeed keeps first occurrence.",
    "category": "technical"
   },
   {
    "risk": "Ungrounded AI output shipped to microsite",
    "likelihood": "low",
    "impact": "high",
    "mitigation": "Citation-first prompts; integrity check gates Seed Articles view.",
    "detection": "Integrity report failing count > 0 blocks display.",
    "owner": "engineering",
    "escalation": "Any customer-visible ungrounded claim → rollback the blueprint.",
    "fallback": "Auto-hide the article + surface owner action to regenerate with stricter prompt.",
    "category": "product"
   },
   {
    "risk": "Cross-recipient data leak via missing RLS on new table",
    "likelihood": "low",
    "impact": "critical",
    "mitigation": "Every CREATE TABLE ships with GRANT + ENABLE RLS + policies in the same migration.",
    "detection": "Security scanner + migration checklist.",
    "owner": "engineering",
    "escalation": "Immediate lockdown + audit.",
    "fallback": "Revoke Data API grants on affected table; restore from PITR if data was modified.",
    "category": "security"
   },
   {
    "risk": "AI cost runaway on a single blueprint",
    "likelihood": "moderate",
    "impact": "moderate",
    "mitigation": "Per-slug rate limits + smoke-test cache + concurrency cap in UI.",
    "detection": "Cost monitoring dashboard; per-blueprint spend alert at 3x baseline.",
    "owner": "SRE",
    "escalation": "Auto-pause generation; require manual re-enable.",
    "fallback": "Disable AI for the offending blueprint via feature flag; serve last-known-good.",
    "category": "cost"
   },
   {
    "risk": "AI provider outage or model deprecation",
    "likelihood": "moderate",
    "impact": "moderate",
    "mitigation": "Per-capability fallback model + retry with backoff; abstract via Lovable AI Gateway.",
    "detection": "Elevated 5xx or empty completions; smoke test failing across blueprints.",
    "owner": "engineering",
    "escalation": "Sustained > 30 min → switch fallback model; notify owners.",
    "fallback": "Serve cached artifacts + disable AI-only capabilities until restored.",
    "category": "vendor"
   },
   {
    "risk": "Compliance evidence gap during audit",
    "likelihood": "low",
    "impact": "high",
    "mitigation": "Evidence-first reproject gate + audit trail export from UI.",
    "detection": "Missing audit entries surfaced in periodic reconciliation report.",
    "owner": "legal",
    "escalation": "Disaster-event counsel-visible gap → incident + documentation per policy.",
    "fallback": "Freeze affected blueprint's reproject state; produce backfill evidence pack.",
    "category": "compliance"
   },
   {
    "risk": "Solo/small-team key-person dependency",
    "likelihood": "moderate",
    "impact": "high",
    "mitigation": "Deterministic DNA modules keep decisions in code, not in one head; runbooks per capability.",
    "detection": "Bus-factor review each quarter.",
    "owner": "owner",
    "escalation": "> 1 critical path with no backup → hire or contract.",
    "fallback": "Freeze non-critical changes; document current state before further work.",
    "category": "team"
   },
   {
    "risk": "Audit trail gaps on reproject decisions",
    "likelihood": "low",
    "impact": "critical",
    "mitigation": "Every mutation writes audit entry in the same transaction.",
    "detection": "Audit trail row count vs mutation count reconciliation.",
    "owner": "engineering",
    "escalation": "Disaster-event counsel-visible gap → incident + documentation.",
    "fallback": "Reconstruct from Postgres WAL + application logs; disclose per compliance policy.",
    "category": "compliance"
   }
  ],
  "rules": [
   "Keep business logic out of UI components — derivations live in lib/*, panels only render.",
   "Do not introduce a new service without a clear owner and a scaling reason.",
   "All external integrations must have retries, timeouts, and failure handling.",
   "All sensitive actions must be auditable in the same transaction that performs them.",
   "All background jobs must be idempotent.",
   "All APIs must return the normalized error envelope.",
   "All recipient-scoped queries must enforce recipient isolation via RLS — never trust the client.",
   "All expensive AI calls must be logged, capped, and observable.",
   "All schema changes must be reversible or safely migratable — no destructive drops without a rollout plan.",
   "All critical workflows must have observability: correlationId, phase timings, retry timeline.",
   "Every public table ships with GRANT + ENABLE RLS + policies in the same migration.",
   "Every AI span carries a citation; no citation, no ship.",
   "Every destructive action requires typed confirmation."
  ],
  "audit": {
   "product_fit": "Architecture matches an evidence-first, regulated-adjacent workflow product per blueprint.",
   "simplicity": "One shell, one DB, edge functions for bursts — near the simplicity floor for the product's ambitions.",
   "security": "RLS + role table + audit trail; meets ASVS L1 baseline.",
   "reliability": "SLOs defined; per-module degradation; retries + diagnostics in place.",
   "scalability": "Horizontal by blueprint count is the growth axis; per-blueprint scaling is comfortably in headroom.",
   "maintainability": "Deterministic derivations (Design DNA, Architecture DNA) keep per-vertical drift out of components.",
   "performance": "p95 target 600ms is realistic on Cloud edge with warm cache.",
   "cost": "Idle-to-zero for cold blueprints; per-blueprint attribution keeps AI spend controllable.",
   "compliance": "Domain-specific (agency documentation, attestation signers, retention schedules)",
   "dx": "Single stack (React + Vite + Tailwind + Cloud); new blueprint reaches microsite state in one session.",
   "ops_burden": "Managed platform absorbs infra ops; SRE work is limited to SLO watch + runbooks.",
   "extensibility": "New capability = new edge function + new Runtime tab entry; no shell changes required.",
   "team_suitability": "Fits a small team; every added component must retire an older one.",
   "time_to_market": "New blueprint reachable to validation-microsite state within one working session.",
   "recommendation": {
    "style": "modular monolith",
    "stack": "React + Vite + TypeScript + Tailwind + shadcn on the client; Deno edge functions + managed Postgres (RLS) + object storage on the server; Lovable AI Gateway (unused in this vertical).",
    "hosting": "Lovable Cloud managed hosting; preview + production environments; edge functions co-deploy with the app.",
    "database": "Managed Postgres with RLS + JSONB; PITR enabled for critical-tier recipients.",
    "auth": "Managed OAuth (Google default) + user_roles table + has_role() SECURITY DEFINER referenced from RLS policies.",
    "integrations": "GitHub (public read) for sync + sources; Lovable AI Gateway for LLM calls; Cloud Storage for artifacts. No third-party CRM/email/SMS at MVP.",
    "ai_approach": "No AI at MVP for this vertical; revisit only when a scoped generation task with clear sources appears.",
    "build_first": [
     "Blueprint Core (evidence + reproject gate) — vertical-agnostic.",
     "Content Pipeline (sources → articles → integrity) — required for any evidence claim.",
     "Sync + rollback — required to safely onboard the network."
    ],
    "avoid": [
     "Any per-blueprint deploy pipeline.",
     "Autonomous AI agents that mutate data without owner confirmation.",
     "Bespoke workflow engines before the in-app queue is exhausted."
    ],
    "revisit_later": [
     "Workflow engine adoption when > 10 concurrent long jobs per blueprint.",
     "Search index dedicated infra when Postgres FTS p95 breaches SLO.",
     "Multi-region on the first residency-bound contract."
    ],
    "biggest_risks": [
     "Missing RLS on a new public table (critical).",
     "Ungrounded AI output reaching a customer-visible surface.",
     "AI cost runaway on a single blueprint.",
     "Solo/small-team key-person dependency."
    ],
    "first_10_steps": [
     "Confirm managed OAuth + user_roles table + has_role() function are in place.",
     "Enable RLS + policies on every existing public table; add the migration checklist to CI.",
     "Wire correlationId end-to-end across every edge function call.",
     "Ship the smoke test runner as a required post-deploy gate.",
     "Enable PITR + schedule the first restore drill on the calendar.",
     "Add per-slug AI recovery caps and cost dashboards.",
     "Enforce evidence-first reproject gate for every blueprint.",
     "Set SLO burn-rate alerts on the top 3 SLIs.",
     "Document the per-capability runbook (retry, cancel, invalidate).",
     "Publish this Architecture DNA per blueprint as part of the reproject evidence pack."
    ],
    "top_10_rules": [
     "Every public table ships with GRANT + RLS + policies in the same migration.",
     "Every mutation writes an audit entry in the same transaction.",
     "Every AI span carries a citation; no citation, no ship.",
     "Every long AI call is per-item, never monolithic.",
     "Every edge function call carries a correlationId end-to-end.",
     "Every retry uses exponential backoff + jitter with a hard attempt cap.",
     "Every destructive action requires typed confirmation.",
     "No microservice extraction without a divergent SLO.",
     "No new dependency without a supply-chain scan.",
     "Signature element (Documentation-dossier tabs with disaster event chip) and accent (dossier-slate) are network invariants — respect them."
    ]
   }
  }
 },
 "design": {
  "slug": "fema-public-assistance-recovery-engine",
  "archetypes": [
   "compliance/regulatory tool",
   "workflow tool",
   "operations system"
  ],
  "user_mindset": {
   "goals": "Produce a statute-complete recovery file under a recovery-season deadline.",
   "session_length": "Bursty around the peak-recovery distribution windows; otherwise review-oriented.",
   "confidence": "Expert users; will not accept opaque AI output.",
   "interface_needs": "Print-parity layouts, citation chains, freeze/approval states."
  },
  "posture": [
   "authoritative",
   "trustworthy",
   "operational"
  ],
  "density": "compact",
  "trust_level": {
   "tier": "high",
   "sensitive_domains": [
    "documentation",
    "disaster event data",
    "the applicant's counsel communications"
   ],
   "implications": [
    "Every destructive action confirmed with typed intent, never a single-click.",
    "Errors carry remediation copy + owner, not just a message.",
    "Focus rings visible on every interactive element (WCAG 2.2 AA minimum).",
    "Named signer on any outbound artifact.",
    "Explicit unsaved-changes gate on nav."
   ]
  },
  "differentiation": {
   "avoid": [
    "Material Design defaults",
    "shadcn stock look (unstyled cards + slate ring)",
    "Purple/indigo gradient heroes",
    "Stripe/Linear/Notion mimicry",
    "Vertical cliché: Cartoon shield mascots"
   ],
   "strategy": "Anchor on the documentation-dossier tabs with disaster event chip as the recurring signature element; every page must include it at least once. Cost-documentation the dossier-slate accent for evidence/status signals only."
  },
  "territories": [
   {
    "name": "Documentation Dossier",
    "color_mood": "dossier slate + parchment",
    "typography": "Söhne + Serif Display",
    "density": "tabbed dossier",
    "component_feel": "government form set",
    "motion": "tab-first",
    "fits": "the applicant's counsel parity",
    "risks": "bureaucratic feel"
   },
   {
    "name": "Disaster-event Atlas",
    "color_mood": "map ink + civic navy",
    "typography": "Neue Haas Grotesk",
    "density": "map-driven",
    "component_feel": "atlas + rules",
    "motion": "map pan",
    "fits": "multi-disaster event",
    "risks": "requires geo data"
   },
   {
    "name": "Pack Timeline",
    "color_mood": "slate + amber",
    "typography": "Inter",
    "density": "timeline",
    "component_feel": "gantt of duties",
    "motion": "scroll-sync",
    "fits": "recurring documentation",
    "risks": "gantt fatigue"
   }
  ],
  "chosen_territory": "Deobligation-Defense Dossier",
  "chosen_rationale": "Mid-market recovery coordinators and CFOs trust a file that looks like it will survive a Single Audit; the dossier territory signals rigor over flash.",
  "prioritized_components": [
   {
    "name": "Disaster-event chip",
    "why": "scope is always per-disaster event"
   },
   {
    "name": "PackOrder card w/ due-by",
    "why": "primary work unit"
   },
   {
    "name": "Documentation package assembler",
    "why": "output is a bundle"
   }
  ],
  "patterns": [
   {
    "name": "Disaster-event switcher",
    "description": "Global scope selector; every query respects it."
   },
   {
    "name": "Documentation sign-off",
    "description": "Named signer with attestation copy."
   }
  ],
  "states": [
   "default",
   "hover",
   "active",
   "focus",
   "disabled",
   "loading",
   "skeleton",
   "empty",
   "error",
   "warning",
   "success",
   "offline",
   "permission-denied",
   "partial-data",
   "syncing",
   "unsaved-changes",
   "ai-generating"
  ],
  "localization": [
   "Copy budgets assume +35% expansion for DE/FR translations.",
   "RTL mirror verified for AR/HE (icons flipped, numerals kept LTR).",
   "Dates/times/currencies use Intl APIs, never hardcoded formats.",
   "Touch targets ≥ 44px; keyboard tab order matches visual order.",
   "Density modes: comfortable (default), compact (power users), spacious (accessibility)."
  ],
  "uniqueness_audit": {
   "app_specific_decisions": [
    "Dossier tab motif",
    "Attestation copy discipline"
   ],
   "cliches_avoided": [
    "Shield mascots",
    "Green-check compliance theatre"
   ],
   "scale_notes": "New blueprints inherit the network shell but MUST declare their own signature element, accent role, and anti-reference before they can be marked ready. Enforced by the reproject gate."
  },
  "tokens": {
   "brand": "222 30% 24%",
   "brand-fg": "36 30% 97%",
   "surface": "40 25% 95%",
   "ink": "220 25% 14%",
   "muted": "220 10% 42%",
   "accent": "45 85% 52%"
  },
  "type": {
   "display": "'DM Serif Display', ui-serif, serif",
   "body": "'Inter', system-ui, sans-serif",
   "fonts_url": "https://fonts.googleapis.com/css2?family=DM+Serif+Display&family=Inter:wght@400;500;600&display=swap"
  },
  "signature": {
   "motif": "Documentation dossier tabs · disaster event chip",
   "render": "dossier-tabs"
  }
 },
 "seo": {
  "slug": "fema-public-assistance-recovery-engine",
  "archetype": "statute-fluent authority site",
  "archetype_impact": "Search fit is a statute-fluent authority site. That means depth over breadth: each page cites the specific rule/section it addresses, and thin variants are refused.",
  "authority_dna": {
   "site_archetype": "statute-fluent authority site",
   "monetization_model": "B2B lead → Gap Scan → paid recovery file engagement (not ad revenue; not affiliate).",
   "main_search_intents": [
    "informational",
    "commercial"
   ],
   "topical_authority_opportunity": "Own the \"applicant PA Cost Documentation\" topic cluster by covering Civ. Code PAPPG V5 2 CFR 200, §38-12-503, §38-12-507, and §25-11-114 end-to-end — window math, the seven PA cost documentation recovery file items, percent funded, insurance-offset statements, and distribution evidence.",
   "local_seo_opportunity": "Not justified: buyers search by statute/form, not by city. Do not build /city/ pages.",
   "global_national_opportunity": "National (US-first) is the primary market. International only if the applicant's counsel itself is cross-border (e.g., EU AI Act, VAT, CBP).",
   "easiest_ranking_path": "Long-tail, statute-specific how-to and edge-case queries (window math, percent-funded reconciliation, variable assessments) where the SERP is outdated law-firm alerts and PDFs.",
   "hardest_ranking_path": "Head terms like \"applicant software\" — dominated by aged vendor domains. Defer until authority accrues.",
   "trust_credibility_requirements": [
    "Named human authors with role + credentials",
    "Rule / statute / agency citations on every claim",
    "Last-reviewed date + change log on regulatory pages",
    "Direct links to primary agency source (not aggregators)",
    "Expert reviewer attribution on YMYL pages"
   ],
   "ymyl": true,
   "expert_review_needed": true,
   "site_structure": "Authority hub + narrow high-intent service page + linkable evidence assets. Not a directory. Not a marketplace.",
   "seo_moat": "always-current rule-mapped pages with change-log timestamps"
  },
  "search_market": {
   "primary_markets": [
    "applicant PA cost documentation workflow",
    "crs 2 CFR 200 PA cost documentation recovery file"
   ],
   "secondary_markets": [
    "applicant annual recovery report",
    "cost record documentation",
    "percent funded documentation"
   ],
   "low_competition_subtopics": [
    "applicant PA cost documentation edge cases",
    "PA cost documentation recovery file exception handling",
    "variable assessment PA cost documentation recovery file"
   ],
   "high_commercial_intent": [
    "PA cost documentation recovery file preparation service",
    "applicant documentation outsourcing",
    "federal PA cost documentation service",
    "PA cost documentation recovery file production desk"
   ],
   "informational": [
    "what is the assessment and cost-documentation funding documentation summary",
    "crs 2 CFR 200 annual recovery report explained",
    "what does percent funded mean applicant"
   ],
   "local_intent": [],
   "transactional": [
    "PA cost documentation recovery file preparation pricing",
    "applicant recovery-season gap scan",
    "PA cost documentation pack demo"
   ],
   "comparison": [
    "PA cost documentation recovery file service vs applicant software templates",
    "Reoblige alternatives"
   ],
   "problem_solution": [
    "how to complete the crs 2 CFR 200 form",
    "annual recovery report missing the known-records statement",
    "percent funded does not match the cost record"
   ],
   "near_me": [],
   "long_tail": [
    "PA cost documentation recovery file for phased communities with variable assessments",
    "crs 2 CFR 200 form step by step for a december project signing"
   ],
   "questions": [
    "what is required in the applicant annual recovery report?",
    "when must the annual recovery report be distributed?",
    "what happens if the PA cost documentation recovery file is incomplete?",
    "can the owner raise assessments without a recipient vote?"
   ],
   "emerging": [
    "AI-assisted PA cost documentation recovery file preparation",
    "automated PA cost documentation completeness checks"
   ],
   "seasonal": [
    "applicant recovery season checklist",
    "annual recovery report deadline december project signing"
   ],
   "underserved_serps": [
    "applicant PA cost documentation edge cases",
    "PA cost documentation recovery file exception handling"
   ],
   "weak_serps": [
    "PA cost documentation recovery file checklist",
    "pre-project documentation deadline"
   ],
   "forum_dominated_serps": [
    "what happens if an applicant misses the recovery report deadline",
    "applicant insurance offset 5 percent limit"
   ],
   "winnable_authoritative_serps": [
    "applicant PA cost documentation definitive guide",
    "crs 2 CFR 200 PA cost documentation recovery file requirements"
   ],
   "avoid_initially": [
    "applicant software",
    "applicant management platform",
    "cost record software"
   ],
   "easy_wins": [
    "applicant PA cost documentation edge cases",
    "PA cost documentation recovery file checklist",
    "crs 2 CFR 200 requirements"
   ],
   "moderate": [
    "applicant PA cost documentation definitive guide",
    "PA cost documentation audit-readiness"
   ],
   "long_term_plays": [
    "applicant documentation software",
    "PA cost documentation for large disaster events"
   ],
   "do_not_pursue": [
    "generic \"how to start an applicant management business\" content",
    "celebrity or trend-jacking posts",
    "national applicant content outside FEMA"
   ]
  },
  "keyword_clusters": [
   {
    "primary": "crs 2 CFR 200 PA cost documentation recovery file requirements",
    "related": [
     "assessment and cost-documentation funding documentation summary form",
     "2 CFR 200(b) annual recovery report requirements"
    ],
    "intent": "commercial",
    "user_problem": "Recovery season is coming and the recovery file elements are scattered",
    "funnel": "BOFU",
    "business_value": "high",
    "ranking_difficulty": "medium",
    "conversion_potential": "high",
    "content_effort": "medium",
    "serp_weakness": "SERP dominated by outdated law-firm alerts and PDFs",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Pillar / evidence guide",
    "reason": "High buyer intent + weak SERP + our unique proof",
    "priority_score": 17,
    "priority": "P0",
    "bucket": "easy-win"
   },
   {
    "primary": "PA cost documentation recovery file vs applicant software templates",
    "related": [
     "PA cost documentation recovery file service alternatives",
     "applicant documentation comparison"
    ],
    "intent": "commercial",
    "user_problem": "Evaluating a done-for-you desk against the software template",
    "funnel": "BOFU",
    "business_value": "high",
    "ranking_difficulty": "medium",
    "conversion_potential": "high",
    "content_effort": "medium",
    "serp_weakness": "Weak — mostly self-serving vendor pages",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Comparison page (honest, evidence-based)",
    "reason": "Late-funnel intent with weak competition",
    "priority_score": 17,
    "priority": "P0",
    "bucket": "easy-win"
   },
   {
    "primary": "applicant PA cost documentation checklist",
    "related": [
     "PA cost documentation recovery file checklist",
     "2 CFR 200(b) completeness checklist"
    ],
    "intent": "informational",
    "user_problem": "Manager needs a per-disaster event completeness check",
    "funnel": "MOFU",
    "business_value": "medium",
    "ranking_difficulty": "low",
    "conversion_potential": "medium",
    "content_effort": "low",
    "serp_weakness": "Checklist SERPs are thin listicles without statute citations",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Resource / lead magnet page",
    "reason": "Easy win + strong lead-magnet fit",
    "priority_score": 14,
    "priority": "P0",
    "bucket": "easy-win"
   },
   {
    "primary": "pre-project documentation deadlines",
    "related": [
     "2 CFR 200 pre-project 30–90 day window",
     "december project signing documentation dates"
    ],
    "intent": "informational",
    "user_problem": "Window math across a disaster event of project signings",
    "funnel": "TOFU",
    "business_value": "medium",
    "ranking_difficulty": "low",
    "conversion_potential": "medium",
    "content_effort": "low",
    "serp_weakness": "Deadline SERPs are stale and rarely show the window math",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Data table page (updated quarterly)",
    "reason": "Recurring seasonal traffic + easy freshness moat",
    "priority_score": 14,
    "priority": "P0",
    "bucket": "easy-win"
   },
   {
    "primary": "applicant PA cost documentation edge cases",
    "related": [
     "variable assessment PA cost documentation recovery file",
     "phased recovery PA cost documentation"
    ],
    "intent": "informational",
    "user_problem": "The form does not fit the disaster event’s structure",
    "funnel": "MOFU",
    "business_value": "medium",
    "ranking_difficulty": "low",
    "conversion_potential": "medium",
    "content_effort": "medium",
    "serp_weakness": "Nobody covers edge cases with worked examples",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "How-to cluster page",
    "reason": "Easy win + high assist to product page",
    "priority_score": 13,
    "priority": "P0",
    "bucket": "easy-win"
   },
   {
    "primary": "applicant documentation software",
    "related": [
     "PA cost documentation recovery file automation",
     "PA cost documentation tools"
    ],
    "intent": "commercial",
    "user_problem": "Choosing tooling vs outsourcing production",
    "funnel": "BOFU",
    "business_value": "high",
    "ranking_difficulty": "high",
    "conversion_potential": "high",
    "content_effort": "high",
    "serp_weakness": "Vendor-dominated but reviewable with honest comparisons",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Product page (defer)",
    "reason": "Long-term play — do not chase before authority is built",
    "priority_score": 9,
    "priority": "P1",
    "bucket": "medium"
   },
   {
    "primary": "applicant PA cost documentation definitive guide",
    "related": [
     "federal cost-documentation project documentation guide",
     "crs 2 CFR 200 PA cost documentation guide"
    ],
    "intent": "informational",
    "user_problem": "Needs the whole obligation explained end-to-end",
    "funnel": "TOFU",
    "business_value": "medium",
    "ranking_difficulty": "medium",
    "conversion_potential": "low",
    "content_effort": "high",
    "serp_weakness": "No single current, primary-source-cited guide exists",
    "local_relevance": "low",
    "global_relevance": "high",
    "suggested_page_type": "Pillar page",
    "reason": "Anchors topical authority for the whole cluster",
    "priority_score": 7,
    "priority": "P1",
    "bucket": "medium"
   }
  ],
  "topical_authority_map": {
   "core_topics": [
    "applicant PA Cost Documentation — definitive guide",
    "Civil Code 2 CFR 200/2 CFR 200 evidence & completeness",
    "Statute library"
   ],
   "pillars": [
    {
     "name": "applicant PA Cost Documentation — definitive guide",
     "core_intent": "informational",
     "audience": "recovery coordinators, operations leads, recovery-ops recovery teams",
     "conversion_goal": "Newsletter / checklist download → later validation call",
     "supporting_pages": [
      "applicant PA Cost Documentation explained",
      "applicant PA Cost Documentation workflow step by step",
      "applicant PA Cost Documentation edge cases",
      "applicant PA Cost Documentation FAQs"
     ],
     "internal_links": [
      "/product",
      "/rules/specific-federal-state-the applicant's counsel-per-topic/",
      "/resources/checklist"
     ],
     "schema": [
      "Article",
      "BreadcrumbList",
      "FAQPage (where genuine)"
     ],
     "evidence_needed": [
      "Named reviewer",
      "Primary-source citations",
      "Worked example"
     ],
     "local_variants": [],
     "national_variants": [
      "US-national (default)"
     ]
    },
    {
     "name": "Civil Code 2 CFR 200/2 CFR 200 evidence & completeness",
     "core_intent": "commercial",
     "audience": "recovery coordinators, operations leads, recovery-ops recovery teams",
     "conversion_goal": "Book validation call",
     "supporting_pages": [
      "PAPPG V5 2 CFR 200 evidence requirements",
      "applicant PA Cost Documentation audit checklist",
      "Common applicant PA Cost Documentation evidence gaps"
     ],
     "internal_links": [
      "/product",
      "/guides/federal-cost-documentation-documentation/",
      "/resources/evidence-checklist"
     ],
     "schema": [
      "Article",
      "FAQPage",
      "BreadcrumbList",
      "HowTo (only for real workflow)"
     ],
     "evidence_needed": [
      "Worked evidence artifact",
      "Disaster-event counsel citation",
      "Reviewer credential"
     ],
     "local_variants": [],
     "national_variants": [
      "US-national"
     ]
    },
    {
     "name": "Statute library",
     "core_intent": "informational",
     "audience": "recovery coordinators, operations leads, recovery-ops recovery teams",
     "conversion_goal": "Assisted conversion via internal linking",
     "supporting_pages": [
      "Civ. Code 2 CFR 200 — text and citations",
      "Civ. Code §38-12-503 — text and citations",
      "Civ. Code §38-12-507 — text and citations",
      "Civ. Code §5565 — text and citations",
      "Civ. Code 2 CFR 200 — text and citations",
      "Civ. Code the warranty of eligibility (§38-12-503) — text and citations",
      "Civ. Code §5610 — text and citations"
     ],
     "internal_links": [
      "/guides/federal-cost-documentation-documentation/",
      "/product"
     ],
     "schema": [
      "Article",
      "BreadcrumbList"
     ],
     "evidence_needed": [
      "Primary source link",
      "Visited-on date",
      "Reviewer sign-off"
     ],
     "local_variants": [],
     "national_variants": [
      "US-national"
     ]
    }
   ],
   "supporting_page_types": [
    "definition / glossary",
    "how-to workflow",
    "edge-case handling",
    "rule-change explainer",
    "worked example",
    "FAQ",
    "comparison (only when honest)",
    "case study (only with permission)",
    "evidence artifact / template",
    "the applicant's counsel update log"
   ]
  },
  "site_architecture": {
   "homepage_strategy": "Above-the-fold: one-sentence purpose + primary CTA (validation call). Below: 3 problem-cards linking to pillars, 1 evidence-asset teaser, 1 authority statement with named reviewer.",
   "main_nav": [
    "Product",
    "How it works",
    "Pillars",
    "Resources",
    "About",
    "Contact"
   ],
   "footer_nav": [
    "Editorial policy",
    "Contact",
    "Privacy",
    "Terms",
    "Sitemap",
    "Changelog"
   ],
   "hubs": [
    {
     "name": "Product / service",
     "url": "/product",
     "purpose": "High-intent commercial page"
    },
    {
     "name": "Guides pillar",
     "url": "/guides",
     "purpose": "Topical authority hub"
    },
    {
     "name": "Rule library",
     "url": "/rules",
     "purpose": "Entity/regulation reference"
    },
    {
     "name": "Resources",
     "url": "/resources",
     "purpose": "Linkable assets (templates, checklists)"
    },
    {
     "name": "Changelog",
     "url": "/changelog",
     "purpose": "Freshness + trust signal"
    }
   ],
   "url_patterns": [
    "/product",
    "/guides/[topic]/",
    "/guides/[topic]/[subtopic]/",
    "/rules/[the applicant's counsel]/[rule]/",
    "/resources/[asset]/",
    "/compare/[a]-vs-[b]/",
    "/glossary/[term]/"
   ],
   "avoid_url_patterns": [
    "/[city]/[service]/ (no local intent for this buyer)",
    "/blog/[year]/[month]/[slug]/ (dated slugs decay CTR)",
    "/tag/[tag]/ (thin archive pages)",
    "Any duplicate /service/ and /solutions/ trees"
   ]
  },
  "global_national": {
   "national_clusters": [
    "applicant PA Cost Documentation — definitive guide",
    "PAPPG V5 2 CFR 200 compliance workflow",
    "applicant PA Cost Documentation evidence checklist",
    "documentation audit-readiness"
   ],
   "linkable_assets": [
    "Evidence checklist (downloadable, gated by email is OK)",
    "Rule-to-artifact mapping table (HTML + PDF)",
    "Change-log / the applicant's counsel update tracker",
    "Worked example (redacted real case)"
   ],
   "original_research_ideas": [
    "Annual applicant PA Cost Documentation readiness benchmark (survey of ~50 operators)",
    "Cost-of-non-compliance calculation for documentation",
    "State-by-state variation index (where applicable)"
   ],
   "international_needed": false,
   "international_notes": "Not needed. US-first. Do not build hreflang variants."
  },
  "local_seo": {
   "justified": false,
   "reason": "Buyers search by statute/form, not by city. Local pages would be doorway pages.",
   "gbp_categories_primary": [],
   "gbp_categories_secondary": [],
   "location_page_rules": [
    "Do not build location pages for this blueprint."
   ],
   "citations": [],
   "review_strategy": "Reviews are not a Local ranking factor here; use G2/Capterra + case studies instead.",
   "local_schema": []
  },
  "programmatic": {
   "recommended": false,
   "reason": "Programmatic pages almost always become doorway pages in regulated niches. Prefer a small number of deeply-researched pages.",
   "rules": [
    "Only allowed for genuinely differentiated data (e.g., a state-by-state rule table where each state truly differs)",
    "Every programmatic page must include: unique data field + unique local/regulatory content + human review before publish",
    "noindex until minimum quality threshold met",
    "Rel=canonical to the pillar when a page falls below threshold"
   ],
   "per_page_requirements": [
    "≥1 unique data point not present on sibling pages",
    "≥1 unique paragraph of human-written analysis",
    "Verified last-reviewed date"
   ],
   "quality_gates": [
    "Editorial review before indexation",
    "Quarterly re-review or noindex",
    "Automated thin-content detector (<300 words unique) blocks publish"
   ]
  },
  "page_templates": [
   {
    "page_type": "Homepage",
    "purpose": "State the offer + route to validation call.",
    "target_intent": "commercial",
    "url_pattern": "/",
    "h1_pattern": "[One-sentence purpose]",
    "title_pattern": "[Brand] — [One-sentence purpose]",
    "meta_description_pattern": "One sentence outcome + CTA verb. ≤ 155 chars.",
    "above_the_fold": [
     "H1",
     "Sub-headline (audience + outcome)",
     "Primary CTA (validation call)",
     "1 trust chip (reviewer / cite)"
    ],
    "outline": [
     "Problem framing",
     "3 pillar cards",
     "Evidence asset teaser",
     "Named reviewer statement",
     "Contact"
    ],
    "internal_links": [
     "/product",
     "/guides",
     "/resources",
     "/about"
    ],
    "conversion_elements": [
     "Calendar CTA",
     "Checklist download secondary"
    ],
    "schema": [
     "Organization",
     "WebSite",
     "SearchAction"
    ],
    "trust_elements": [
     "Reviewer name",
     "Editorial policy link"
    ],
    "media": [
     "Original workflow diagram (SVG)"
    ],
    "faq_opportunities": [
     "Top 3 buyer questions"
    ],
    "cta_strategy": "Above-the-fold soft + end-of-page primary",
    "quality_requirements": [
     "Loads < 2.5s LCP",
     "Named reviewer visible"
    ],
    "anti_thin_rules": [
     "No stock hero",
     "No generic 'we help X do Y' filler"
    ]
   },
   {
    "page_type": "Pillar page",
    "purpose": "Anchor a topic cluster with a definitive explanation.",
    "target_intent": "informational",
    "url_pattern": "/guides/[topic]/",
    "h1_pattern": "[Topic] — Definitive Guide",
    "title_pattern": "[Topic] — Definitive Guide | [Brand]",
    "meta_description_pattern": "Definition + what the reader will learn + reviewer credential.",
    "above_the_fold": [
     "H1",
     "40–60 word definition block",
     "TOC",
     "Last-reviewed date + reviewer"
    ],
    "outline": [
     "Definition",
     "Who this applies to",
     "Workflow",
     "Rules & citations",
     "Edge cases",
     "FAQs",
     "Related pages"
    ],
    "internal_links": [
     "Cluster sub-pages",
     "Rule library",
     "Product"
    ],
    "conversion_elements": [
     "End-of-page checklist download",
     "Sidebar validation call CTA"
    ],
    "schema": [
     "Article",
     "BreadcrumbList",
     "FAQPage (only real FAQs)"
    ],
    "trust_elements": [
     "Named author + reviewer",
     "Primary source cites"
    ],
    "media": [
     "Original diagrams",
     "Rule comparison table"
    ],
    "faq_opportunities": [
     "Real questions from practitioners"
    ],
    "cta_strategy": "Assist conversion via internal link to product; primary CTA end-of-page.",
    "quality_requirements": [
     "≥ 1500 words unique",
     "≥ 3 primary sources cited",
     "Reviewer credential visible"
    ],
    "anti_thin_rules": [
     "No listicles padded with keyword variants",
     "No AI-generated body"
    ]
   },
   {
    "page_type": "How-to cluster page",
    "purpose": "Answer a specific workflow question inside a cluster.",
    "target_intent": "informational",
    "url_pattern": "/guides/[topic]/[subtopic]/",
    "h1_pattern": "[Specific action or question]",
    "title_pattern": "[Specific action] — [Pillar topic] | [Brand]",
    "meta_description_pattern": "Concrete outcome + who it applies to + one caveat.",
    "above_the_fold": [
     "H1",
     "Direct answer paragraph",
     "Numbered steps preview"
    ],
    "outline": [
     "Direct answer",
     "Steps",
     "Edge cases",
     "Common mistakes",
     "Related pages"
    ],
    "internal_links": [
     "Pillar page",
     "Sibling clusters",
     "Product"
    ],
    "conversion_elements": [
     "End-of-page checklist download",
     "Related tool link"
    ],
    "schema": [
     "Article",
     "HowTo (only if real workflow)",
     "BreadcrumbList"
    ],
    "trust_elements": [
     "Named author",
     "Reviewer for YMYL"
    ],
    "media": [
     "Screenshots of the actual workflow"
    ],
    "faq_opportunities": [
     "Follow-up questions"
    ],
    "cta_strategy": "Contextual link to product mid-page; primary CTA end-of-page.",
    "quality_requirements": [
     "Unique steps not duplicated from pillar",
     "Reviewer date visible"
    ],
    "anti_thin_rules": [
     "No spun variants of the pillar"
    ]
   },
   {
    "page_type": "Product / service page",
    "purpose": "Convert commercial intent.",
    "target_intent": "commercial",
    "url_pattern": "/product",
    "h1_pattern": "[Outcome-focused headline]",
    "title_pattern": "[Brand] — [Outcome]",
    "meta_description_pattern": "State the outcome + primary CTA verb.",
    "above_the_fold": [
     "H1",
     "Sub-headline",
     "Primary CTA",
     "Trust chip"
    ],
    "outline": [
     "Problem",
     "How we solve it",
     "Proof / worked example",
     "Objection handling",
     "FAQ",
     "CTA"
    ],
    "internal_links": [
     "Case study",
     "Pillar guide",
     "Evidence checklist"
    ],
    "conversion_elements": [
     "Calendar",
     "Secondary checklist"
    ],
    "schema": [
     "Service or SoftwareApplication (whichever fits)",
     "Organization",
     "FAQPage"
    ],
    "trust_elements": [
     "Named reviewer",
     "Primary-source cites",
     "Contact info"
    ],
    "media": [
     "Screenshot of the actual workflow, not marketing composites"
    ],
    "faq_opportunities": [
     "Buyer objections"
    ],
    "cta_strategy": "Above-the-fold + repeated end-of-page",
    "quality_requirements": [
     "Unique per audience segment (no doorway variants)"
    ],
    "anti_thin_rules": [
     "No thin '/services/X/' spin-offs of the same page"
    ]
   },
   {
    "page_type": "Rule / regulation reference page",
    "purpose": "Serve as the site's citation-grade reference for a specific rule.",
    "target_intent": "informational",
    "url_pattern": "/rules/[the applicant's counsel]/[rule]/",
    "h1_pattern": "[Disaster-event counsel] — [Rule] explained",
    "title_pattern": "[Rule] — [Disaster-event counsel] Requirements | [Brand]",
    "meta_description_pattern": "What the rule requires + last-reviewed date.",
    "above_the_fold": [
     "H1",
     "Definition",
     "Last-reviewed + reviewer"
    ],
    "outline": [
     "What the rule says",
     "Who it applies to",
     "Deadlines",
     "Evidence required",
     "Change log"
    ],
    "internal_links": [
     "Pillar guide",
     "Product"
    ],
    "conversion_elements": [
     "Subscribe to change-log",
     "Sidebar validation call"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "trust_elements": [
     "Primary-source link",
     "Visited-on date",
     "Reviewer credential"
    ],
    "media": [
     "Rule comparison table"
    ],
    "faq_opportunities": [
     "Real practitioner questions"
    ],
    "cta_strategy": "Assist conversion via internal link",
    "quality_requirements": [
     "Primary source link required",
     "Quarterly re-review"
    ],
    "anti_thin_rules": [
     "No auto-generated rule scraping without human review"
    ]
   },
   {
    "page_type": "Comparison page",
    "purpose": "Serve genuine BOFU comparison intent.",
    "target_intent": "commercial",
    "url_pattern": "/compare/[a]-vs-[b]/",
    "h1_pattern": "[A] vs [B] — Honest Comparison",
    "title_pattern": "[A] vs [B] | [Brand]",
    "meta_description_pattern": "Honest side-by-side + when to pick which.",
    "above_the_fold": [
     "H1",
     "TL;DR verdict",
     "When-to-pick block"
    ],
    "outline": [
     "Criteria",
     "Side-by-side table",
     "Where each wins",
     "Where each loses",
     "Recommendation"
    ],
    "internal_links": [
     "Product",
     "Pillar guide"
    ],
    "conversion_elements": [
     "Calendar CTA",
     "Evidence checklist"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "trust_elements": [
     "Document the reviewer's relationship to each option"
    ],
    "media": [
     "Feature comparison table"
    ],
    "faq_opportunities": [
     "'Which should I choose?' style"
    ],
    "cta_strategy": "End-of-page primary CTA to the fitting option",
    "quality_requirements": [
     "Honest even when it hurts",
     "Document relationship"
    ],
    "anti_thin_rules": [
     "No manufactured 'X vs Y' pages for every pair"
    ]
   },
   {
    "page_type": "FAQ page",
    "purpose": "Aggregate genuine practitioner questions.",
    "target_intent": "informational",
    "url_pattern": "/faq",
    "h1_pattern": "FAQ",
    "title_pattern": "[Topic] FAQ | [Brand]",
    "meta_description_pattern": "Answers to the questions we hear most.",
    "above_the_fold": [
     "H1",
     "Table of contents"
    ],
    "outline": [
     "Grouped questions",
     "Each answer 40–120 words"
    ],
    "internal_links": [
     "Relevant pillars and rule pages"
    ],
    "conversion_elements": [
     "End-of-page CTA"
    ],
    "schema": [
     "FAQPage (only for genuine FAQs visible on-page)"
    ],
    "trust_elements": [
     "Named reviewer"
    ],
    "media": [],
    "faq_opportunities": [
     "Real questions only — never invented"
    ],
    "cta_strategy": "Related-block links, not inline mid-answer",
    "quality_requirements": [
     "No invented questions"
    ],
    "anti_thin_rules": [
     "No 'is X the best' padding"
    ]
   },
   {
    "page_type": "Glossary term page",
    "purpose": "Definition-grade authority for a single term.",
    "target_intent": "informational",
    "url_pattern": "/glossary/[term]/",
    "h1_pattern": "[Term]",
    "title_pattern": "[Term] — Definition | [Brand]",
    "meta_description_pattern": "Concise definition + who uses the term.",
    "above_the_fold": [
     "H1",
     "40-word definition"
    ],
    "outline": [
     "Definition",
     "Related terms",
     "Where it applies",
     "Common misuses"
    ],
    "internal_links": [
     "Pillar",
     "Rule pages"
    ],
    "conversion_elements": [
     "Sidebar related-tool link"
    ],
    "schema": [
     "Article",
     "BreadcrumbList",
     "DefinedTerm"
    ],
    "trust_elements": [
     "Cite the primary source of the definition"
    ],
    "media": [],
    "faq_opportunities": [],
    "cta_strategy": "Assist via internal link",
    "quality_requirements": [
     "Never duplicate the pillar's intro"
    ],
    "anti_thin_rules": [
     "No glossary spam"
    ]
   },
   {
    "page_type": "Case study page",
    "purpose": "Concrete outcome-based proof.",
    "target_intent": "commercial",
    "url_pattern": "/case-studies/[slug]/",
    "h1_pattern": "[Outcome achieved for [customer type]]",
    "title_pattern": "Case Study — [Outcome] | [Brand]",
    "meta_description_pattern": "Concrete outcome + timeframe + method.",
    "above_the_fold": [
     "H1",
     "Outcome metric",
     "Approved-for-publication chip"
    ],
    "outline": [
     "Context",
     "Approach",
     "Outcome",
     "Reviewer quote"
    ],
    "internal_links": [
     "Product",
     "Pillar guide"
    ],
    "conversion_elements": [
     "End-of-page CTA"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "trust_elements": [
     "Named customer contact (with permission)"
    ],
    "media": [
     "Redacted artifact screenshots"
    ],
    "faq_opportunities": [],
    "cta_strategy": "End-of-page primary CTA",
    "quality_requirements": [
     "Written approval on file"
    ],
    "anti_thin_rules": [
     "No fabricated case studies"
    ]
   }
  ],
  "on_page_rules": {
   "title_tag": "Pattern: [Primary keyword] — [Angle] | applicant PA Cost Documentation. ≤ 60 chars. Front-load the keyword. No clickbait.",
   "meta_description": "≤ 155 chars. State the specific outcome. Include a verb + a rule citation when applicable. No stuffing.",
   "headings": "One H1. H2s follow the workflow steps or the searcher's questions. H3s for edge cases. No decorative headings.",
   "intro": "First 100 words: define the topic in the searcher's language + name the specific rule/agency + preview what the page delivers.",
   "snippet_targeting": "Add a 40–60 word definition block and a numbered how-to block near the top for featured snippet + AI overview eligibility.",
   "tables_lists": "Use tables for rule comparisons, deadlines, and thresholds. Lists for steps. Never use tables for layout.",
   "images": "Original diagrams/screenshots preferred. Descriptive alt text. WebP. Explicit width/height. Never AI slop stock art.",
   "internal_links": "Every page: ≥3 contextual links up to pillar, ≥2 to sibling cluster pages, ≥1 to a commercial page.",
   "external_citations": "Cite the primary source (agency PDF / statute) — not aggregators — with the visited-on date.",
   "author_attribution": "Named author + role + linked bio page. Reviewer for YMYL.",
   "freshness": "Last-reviewed date at top; change log at bottom for the applicant's counsel pages; quarterly review cadence.",
   "cta_placement": "Above the fold (soft), mid-page (contextual to the section), end-of-page (primary).",
   "mobile": "Single-column, tap targets ≥44px, no interstitials, no autoplay video.",
   "avoid": [
    "Keyword stuffing",
    "AI-generated body copy without human edit",
    "Doorway variants",
    "Unsupported superlatives ('best', 'top-rated') without evidence",
    "Meta descriptions duplicated across pages",
    "Marking up invisible content in schema"
   ]
  },
  "entity_seo": {
   "main_entities": [
    "PA cost documentation recovery file (Assessment & Cost-documentation Funding Documentation Summary)",
    "Civil Code 2 CFR 200",
    "PAPPG V5 2 CFR 200 annual recovery report",
    "cost record",
    "percent funded",
    "SB23-206",
    "mitigation history",
    "insurance offset"
   ],
   "related_entities": [
    "FEMA applicant recovery season",
    "project signing distribution window",
    "professional cost record cost record update",
    "fully funded balance",
    "owner assessment authority (the warranty of eligibility (§38-12-503))"
   ],
   "people": [
    "Named practitioners",
    "Reviewers",
    "Disaster-event counsel referenced"
   ],
   "orgs": [
    "FEMA Department of Public Health and Environment (CDPHE)",
    "U.S. Environmental Protection Agency (EPA) Cost-documentation Program",
    "FEMA Division of Real Estate"
   ],
   "tools": [
    "Statute field map",
    "PA cost documentation recovery file source-trace template",
    "Completeness checklist"
   ],
   "regulations": [
    "Civ. Code 2 CFR 200",
    "Civ. Code §38-12-503",
    "Civ. Code §38-12-507",
    "Civ. Code §5565",
    "Civ. Code 2 CFR 200",
    "Civ. Code the warranty of eligibility (§38-12-503)",
    "Civ. Code §5610"
   ],
   "problems": [
    "Incomplete PA cost documentation recovery file",
    "Lost the warranty of eligibility (§38-12-503) assessment authority",
    "Stale cost record",
    "Percent-funded mismatch"
   ],
   "solutions": [
    "Completeness pack workflow",
    "Source-trace appendices",
    "Statute-mapped checklists"
   ],
   "processes": [
    "Intake",
    "Statute field mapping",
    "Extraction & validation",
    "Analyst review",
    "Reproject",
    "Owner adoption & distribution"
   ],
   "alternatives": [
    "PM software (AppFolio/Buildium) templates",
    "the applicant's counsel drafting",
    "in-house spreadsheet production"
   ],
   "synonyms": [
    "PA cost documentation recovery file",
    "PA cost documentation summary",
    "annual recovery report recovery file",
    "assessment and cost-documentation funding documentation"
   ]
  },
  "schema_strategy": [
   {
    "type": "Organization",
    "where": "Site-wide in head",
    "required_fields": [
     "name",
     "url",
     "logo",
     "sameAs"
    ],
    "caution": "Keep in sync with visible About / contact."
   },
   {
    "type": "WebSite + SearchAction",
    "where": "Homepage",
    "required_fields": [
     "name",
     "url",
     "potentialAction"
    ],
    "caution": "Only if on-site search actually exists."
   },
   {
    "type": "BreadcrumbList",
    "where": "All hub / cluster / rule / glossary pages",
    "required_fields": [
     "itemListElement"
    ],
    "caution": "Order must match visible breadcrumbs."
   },
   {
    "type": "Article",
    "where": "Guides, pillars, rule pages",
    "required_fields": [
     "headline",
     "author",
     "datePublished",
     "dateModified"
    ],
    "caution": "Author must exist as a real person."
   },
   {
    "type": "FAQPage",
    "where": "Genuine FAQ pages only",
    "required_fields": [
     "mainEntity[]"
    ],
    "caution": "Only mark up FAQs visible on the page."
   },
   {
    "type": "HowTo",
    "where": "Real step-by-step workflows only",
    "required_fields": [
     "name",
     "step[]"
    ],
    "caution": "Google narrowed HowTo eligibility; use sparingly."
   },
   {
    "type": "Person",
    "where": "Author bio pages",
    "required_fields": [
     "name",
     "jobTitle",
     "sameAs"
    ],
    "caution": "Credentials must be real and verifiable."
   }
  ],
  "internal_linking": {
   "pillar_to_cluster": "Pillar links to every direct cluster page in a curated section (not a mega-menu dump).",
   "cluster_to_pillar": "Every cluster page links back to its pillar in the intro and in-context.",
   "cluster_to_cluster": "Link between sibling clusters only where the user's next question naturally leads there.",
   "service_to_location": "Not applicable.",
   "faq_to_commercial": "Answer the question first, then link to the commercial page in a 'related' block — never inline mid-answer.",
   "breadcrumbs": "Structured breadcrumbs on all guide, rule, and glossary pages.",
   "anchor_text_rules": [
    "Descriptive — match the target page's H1 concept",
    "Vary phrasing across links to the same target",
    "Never exact-match keyword stuffing",
    "Anchor must make sense read aloud"
   ]
  },
  "technical_seo": {
   "crawlability": "Flat depth (≤3 clicks from homepage). No orphan pages. HTML sitemap on /sitemap.",
   "indexability": "Index all real content. noindex utility pages, thank-you pages, and gated-asset landing pages.",
   "sitemaps": "XML sitemap generated at build time. Split by section if > 5k URLs.",
   "robots": "robots.txt allows all; disallow /admin/, /api/. Reference sitemap.",
   "canonicals": "Self-referencing canonical on every page. Filter/sort variants canonical to the base.",
   "pagination": "Prefer 'load more' or a single long page; if paginated, use rel=next/prev semantics via internal linking.",
   "faceted_nav": "Not applicable for this blueprint (no product catalog).",
   "duplicate_control": "One URL per topic. Consolidate before publishing new variants. No www/non-www split.",
   "redirects": "301 for permanent moves; audit chains monthly; never 302 for SEO redirects.",
   "core_web_vitals": "LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1. Test with real-user monitoring.",
   "mobile": "Mobile-first design. No tap-target failures. No horizontal scroll.",
   "accessibility": "WCAG AA. Semantic HTML. Landmarks. Focus states. Alt text.",
   "js_seo": "Content in the initial HTML. Client hydration for interactivity only.",
   "rendering": "Static generation preferred; SSR only where personalized. Never client-only for indexable pages.",
   "gsc_setup": "Verify both www and apex; submit sitemap; monitor Coverage and Enhancements weekly.",
   "analytics_setup": "GA4 + server-side event stream. Consent Mode v2. Event schema documented.",
   "rank_tracking": "Semrush or Ahrefs project set to US database; track pillar + top-20 clusters weekly."
  },
  "eeat": {
   "author_bios": "Every content page has a named author with role, credentials, and a linked author page.",
   "expert_reviewers": "Every YMYL page reviewed by a named expert with disclosed credentials.",
   "editorial_policy": "Public /editorial-policy page: sourcing rules, review cadence, correction policy.",
   "fact_checking": "Every statute/rule reference has a link + visited-on date; corrections dated and disclosed.",
   "credentials": [
    "JD / CPA / MD / CISSP as applicable",
    "Bar admission or license number where public"
   ],
   "citations": "Cite primary sources (agency PDF, statute text). No citation of aggregator blogs.",
   "first_hand_proof": [
    "Screenshots of the actual workflow",
    "Redacted worked examples",
    "Signed reviewer statement"
   ],
   "update_cadence": "Regulatory pages reviewed quarterly; commercial pages reviewed twice yearly.",
   "monetization_disclosure": "Public documentation that leads convert to paid engagements; no undisclosed affiliate content.",
   "ymyl_notes": "This is YMYL. Language stays cautious ('may', 'depends on facts'); no legal/medical advice framing; disclaimer near CTA."
  },
  "ai_search": {
   "principles": [
    "Answer the exact question in the first paragraph",
    "Provide a 40–60 word extractable definition near the top",
    "Structured lists and tables for facts",
    "Cite named primary sources",
    "Author + reviewer names on-page"
   ],
   "tactics": [
    "FAQPage schema for genuine FAQs (not stuffed)",
    "HowTo schema for real workflow pages",
    "Consistent entity naming across the site",
    "Concise summaries at the top of long guides"
   ],
   "do_not": [
    "Write pages targeting AI systems instead of humans",
    "Insert hidden 'AI-only' content",
    "Create bespoke llms.txt / manifests that bypass normal quality",
    "Mass-generate answers to invented questions"
   ]
  },
  "conversion": {
   "primary_cta": "Book a validation conversation (calendar link).",
   "secondary_cta": "Download the evidence checklist (email capture).",
   "lead_magnets": [
    "applicant PA Cost Documentation evidence checklist (PDF)",
    "Rule-to-artifact mapping table",
    "Quarterly the applicant's counsel change-log subscription"
   ],
   "trust_elements": [
    "Named reviewer + credentials",
    "Rule citations visible on-page",
    "Change-log timestamps",
    "Contact + address in footer"
   ],
   "per_page_paths": [
    {
     "page_type": "Homepage",
     "path": "Hero CTA → validation call. Secondary → guides pillar."
    },
    {
     "page_type": "Pillar",
     "path": "TOC → deep sub-pages. End-of-page → validation call."
    },
    {
     "page_type": "Cluster / how-to",
     "path": "In-content 'related tool' link → product. End-of-page → checklist download."
    },
    {
     "page_type": "Product / service",
     "path": "Above-the-fold CTA → calendar. Objection-handling block → FAQ."
    },
    {
     "page_type": "Rule page",
     "path": "Sidebar → related workflow (product). Bottom → subscribe to change-log."
    }
   ],
   "tracking": "GA4 events: cta_click, checklist_download, calendar_book. Server-side dedupe. Weekly funnel review."
  },
  "link_earning": {
   "digital_pr_ideas": [
    "Annual \"applicant PA Cost Documentation\" readiness benchmark report",
    "Cost-of-non-compliance calculator with a shareable result page",
    "Disaster-event counsel-change tracker with an RSS feed"
   ],
   "original_research": [
    "Small operator survey (n≥30) once per year",
    "State-by-state (or agency-by-agency) rule variation index"
   ],
   "directories": [
    "G2 / Capterra category pages",
    "Industry disaster event recipient lists",
    "Disaster-event counsel resource pages when eligible"
   ],
   "expert_contributions": [
    "HARO / Qwoted / Featured expert responses",
    "Bylined articles in industry trade press",
    "Podcast interviews with practitioners"
   ],
   "partnerships": [
    "Disaster-event CLE / CPE sponsorships",
    "Co-authored guides with adjacent (non-competing) vendors"
   ],
   "avoid": [
    "Paid link schemes",
    "PBNs",
    "Mass guest posting",
    "Fake reviews",
    "Reciprocal link exchanges"
   ]
  },
  "roadmap_90d": [
   {
    "phase": "Days 0–30: Foundation",
    "goal": "Establish trust + ship product page + first pillar.",
    "pages": [
     "Homepage",
     "Product page",
     "Pillar: applicant PA Cost Documentation — definitive guide",
     "About + reviewer bio",
     "Editorial policy",
     "Contact"
    ],
    "keywords_targeted": [
     "applicant PA Cost Documentation",
     "applicant PA Cost Documentation guide"
    ],
    "why_first": "Without a trust surface + a real product page, everything else is unmoored.",
    "difficulty": "medium",
    "business_value": "high",
    "required_assets": [
     "Reviewer bio",
     "Editorial policy",
     "One workflow diagram"
    ],
    "internal_links": [
     "Homepage ↔ Product ↔ Pillar"
    ],
    "conversion_goal": "First validation calls booked"
   },
   {
    "phase": "Days 31–60: Topical authority core",
    "goal": "Publish the first cluster of 5–7 supporting pages under the pillar + evidence checklist lead magnet.",
    "pages": [
     "applicant PA Cost Documentation edge cases",
     "applicant PA Cost Documentation workflow step by step",
     "applicant PA Cost Documentation FAQs",
     "Evidence checklist (lead magnet)",
     "distribution deadlines"
    ],
    "keywords_targeted": [
     "applicant PA Cost Documentation edge cases",
     "documentation checklist",
     "PAPPG V5 2 CFR 200 deadlines"
    ],
    "why_first": "Easy-win SERPs that assist conversion to the product page.",
    "difficulty": "low",
    "business_value": "medium",
    "required_assets": [
     "Checklist PDF",
     "Rule table"
    ],
    "internal_links": [
     "All clusters ↔ pillar ↔ product"
    ],
    "conversion_goal": "Checklist downloads + assisted conversions"
   },
   {
    "phase": "Days 61–90: Reference & freshness",
    "goal": "Ship the rule library + first the applicant's counsel change-log post + first comparison page.",
    "pages": [
     "Statute page: Civ. Code 2 CFR 200",
     "Statute page: Civ. Code 2 CFR 200",
     "Statute page: Civ. Code the warranty of eligibility (§38-12-503)",
     "Comparison: PA cost documentation recovery file vs applicant software templates",
     "Q1 leginfo change-log"
    ],
    "keywords_targeted": [
     "crs 2 CFR 200 annual recovery report",
     "crs 2 CFR 200 PA cost documentation",
     "federal warranty of eligibility assessment authority"
    ],
    "why_first": "Reference pages compound in authority; change-log establishes freshness signal.",
    "difficulty": "medium",
    "business_value": "medium",
    "required_assets": [
     "Primary-source citations",
     "Reviewer sign-off"
    ],
    "internal_links": [
     "Rule pages ↔ pillar ↔ product; comparison → product"
    ],
    "conversion_goal": "BOFU comparison conversions"
   }
  ],
  "roadmap_12m": [
   {
    "phase": "Months 4–6: Linkable assets",
    "goal": "Ship the annual State of CA PA Cost Documentations benchmark, the warranty of eligibility (§38-12-503) authority-loss explainer, and the cost-documentation-study vendor format guide.",
    "pages": [
     "Annual applicant PA Cost Documentation benchmark",
     "Cost-of-non-compliance calculator",
     "State variation index"
    ],
    "keywords_targeted": [
     "applicant PA Cost Documentation benchmark",
     "applicant PA Cost Documentation cost",
     "applicant PA Cost Documentation state comparison"
    ],
    "why_first": "Linkable assets drive referring domains and topical authority signals.",
    "difficulty": "medium",
    "business_value": "high",
    "required_assets": [
     "Survey data",
     "Named methodology",
     "Reviewer sign-off"
    ],
    "internal_links": [
     "From every pillar + product"
    ],
    "conversion_goal": "Calculator → validation call handoff"
   },
   {
    "phase": "Months 7–9: Depth + freshness cadence",
    "goal": "Expand each pillar with 3 more cluster pages + quarterly the applicant's counsel change-log.",
    "pages": [
     "Additional cluster pages (per pillar)",
     "Q3 the applicant's counsel change-log",
     "First case study (with permission)"
    ],
    "keywords_targeted": [
     "Long-tail cluster expansions"
    ],
    "why_first": "Compounding topical coverage + freshness moat.",
    "difficulty": "low",
    "business_value": "medium",
    "required_assets": [
     "Customer approval for case study"
    ],
    "internal_links": [
     "Sibling cluster interlinking"
    ],
    "conversion_goal": "Assisted conversions"
   },
   {
    "phase": "Months 10–12: Scale + prune",
    "goal": "Consolidate weak pages, refresh top pages, expand into 1 adjacent topic only if authority is proven.",
    "pages": [
     "Consolidation redirects",
     "Top-10 page refreshes",
     "Adjacent topic scoping"
    ],
    "keywords_targeted": [
     "Existing top-10 clusters"
    ],
    "why_first": "Optimization > net-new after a critical mass is reached.",
    "difficulty": "low",
    "business_value": "high",
    "required_assets": [
     "Analytics review",
     "Consolidation plan"
    ],
    "internal_links": [
     "Redirect audit"
    ],
    "conversion_goal": "CTR + conversion-rate lift"
   }
  ],
  "priority_pages": [
   {
    "rank": 1,
    "page_title": "Civil Code PA cost documentation recovery file requirements",
    "slug": "/guides/crs-2 CFR 200-cost-documentation-documentation-requirements/",
    "page_type": "Pillar / evidence guide",
    "primary_keyword": "crs 2 CFR 200 PA cost documentation recovery file requirements",
    "secondary_keywords": [
     "assessment and cost-documentation funding documentation summary form",
     "2 CFR 200(b) annual recovery report requirements"
    ],
    "intent": "commercial",
    "scope": "national",
    "funnel": "BOFU",
    "difficulty": "medium",
    "business_value": "high",
    "conversion_potential": "high",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Book validation call",
    "production_priority": "P0",
    "why_opportunity": "High buyer intent + weak SERP + our unique proof"
   },
   {
    "rank": 2,
    "page_title": "PA cost documentation recovery file vs applicant software templates",
    "slug": "/guides/cost-documentation-documentation-vs-pm-software/",
    "page_type": "Comparison page (honest, evidence-based)",
    "primary_keyword": "PA cost documentation recovery file vs applicant software templates",
    "secondary_keywords": [
     "PA cost documentation recovery file service alternatives",
     "applicant documentation comparison"
    ],
    "intent": "commercial",
    "scope": "national",
    "funnel": "BOFU",
    "difficulty": "medium",
    "business_value": "high",
    "conversion_potential": "high",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Book validation call",
    "production_priority": "P0",
    "why_opportunity": "Late-funnel intent with weak competition"
   },
   {
    "rank": 3,
    "page_title": "applicant PA cost documentation checklist",
    "slug": "/guides/federal-cost-documentation-documentation-checklist/",
    "page_type": "Resource / lead magnet page",
    "primary_keyword": "applicant PA cost documentation checklist",
    "secondary_keywords": [
     "PA cost documentation recovery file checklist",
     "2 CFR 200(b) completeness checklist"
    ],
    "intent": "informational",
    "scope": "national",
    "funnel": "MOFU",
    "difficulty": "low",
    "business_value": "medium",
    "conversion_potential": "medium",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Download checklist",
    "production_priority": "P0",
    "why_opportunity": "Easy win + strong lead-magnet fit"
   },
   {
    "rank": 4,
    "page_title": "Annual recovery report distribution deadlines (2 CFR 200 pre-project window math)",
    "slug": "/guides/annual-recovery-report-distribution-deadlines/",
    "page_type": "Data table page (updated quarterly)",
    "primary_keyword": "pre-project documentation deadlines",
    "secondary_keywords": [
     "2 CFR 200 pre-project 30–90 day window",
     "december project signing documentation dates"
    ],
    "intent": "informational",
    "scope": "national",
    "funnel": "TOFU",
    "difficulty": "low",
    "business_value": "medium",
    "conversion_potential": "medium",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Download checklist",
    "production_priority": "P0",
    "why_opportunity": "Recurring seasonal traffic + easy freshness moat"
   },
   {
    "rank": 5,
    "page_title": "applicant PA cost documentation edge cases",
    "slug": "/guides/federal-cost-documentation-documentation-edge-cases/",
    "page_type": "How-to cluster page",
    "primary_keyword": "applicant PA cost documentation edge cases",
    "secondary_keywords": [
     "variable assessment PA cost documentation recovery file",
     "phased recovery PA cost documentation"
    ],
    "intent": "informational",
    "scope": "national",
    "funnel": "MOFU",
    "difficulty": "low",
    "business_value": "medium",
    "conversion_potential": "medium",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Download checklist",
    "production_priority": "P0",
    "why_opportunity": "Easy win + high assist to product page"
   },
   {
    "rank": 6,
    "page_title": "applicant documentation software (honest comparison)",
    "slug": "/guides/cost-documentation-documentation-vs-pm-software/",
    "page_type": "Product page (defer)",
    "primary_keyword": "applicant documentation software",
    "secondary_keywords": [
     "PA cost documentation recovery file automation",
     "PA cost documentation tools"
    ],
    "intent": "commercial",
    "scope": "national",
    "funnel": "BOFU",
    "difficulty": "high",
    "business_value": "high",
    "conversion_potential": "high",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Book validation call",
    "production_priority": "P1",
    "why_opportunity": "Long-term play — do not chase before authority is built"
   },
   {
    "rank": 7,
    "page_title": "applicant PA cost documentation definitive guide",
    "slug": "/guides/federal-cost-documentation-documentation-definitive-guide/",
    "page_type": "Pillar page",
    "primary_keyword": "applicant PA cost documentation definitive guide",
    "secondary_keywords": [
     "federal cost-documentation project documentation guide",
     "crs 2 CFR 200 PA cost documentation guide"
    ],
    "intent": "informational",
    "scope": "national",
    "funnel": "TOFU",
    "difficulty": "medium",
    "business_value": "medium",
    "conversion_potential": "low",
    "required_proof": [
     "Named reviewer",
     "Primary-source cites",
     "Worked example"
    ],
    "internal_links": [
     "/guides/federal-cost-documentation-documentation/",
     "/product",
     "/rules/specific-federal-state-the applicant's counsel-per-topic/"
    ],
    "schema": [
     "Article",
     "BreadcrumbList"
    ],
    "cta": "Download checklist",
    "production_priority": "P1",
    "why_opportunity": "Anchors topical authority for the whole cluster"
   }
  ],
  "competitor_gaps": {
   "typical_competitor_types": [
    "PM software (AppFolio/Buildium) vendors",
    "law-firm client alerts",
    "cost-documentation-study firm blogs"
   ],
   "common_weaknesses": [
    "Outdated the applicant's counsel citations",
    "Missing last-reviewed date",
    "No named author or reviewer",
    "Copy-paste content across state / product variants",
    "No worked examples",
    "Thin FAQ padded with generic questions",
    "Poor mobile Core Web Vitals"
   ],
   "how_to_beat_them": [
    "Fresh citations with visited-on dates",
    "Named reviewer + credentials visible",
    "Real, redacted worked examples",
    "Better structured tables for rule comparisons",
    "Faster + more accessible pages"
   ]
  },
  "metrics": {
   "weekly": [
    "GSC impressions/clicks by pillar",
    "Top-20 keyword position",
    "New indexed pages",
    "Core Web Vitals regressions"
   ],
   "monthly": [
    "Organic sessions by hub",
    "Assisted conversions",
    "CTR by template",
    "Content decay list (positions dropped)",
    "Backlink net-new"
   ],
   "quarterly": [
    "Pillar coverage audit",
    "Rule freshness audit",
    "Consolidation / prune list",
    "Conversion path funnel review"
   ],
   "annual": [
    "Full topical authority audit",
    "Benchmark report refresh",
    "Editorial policy refresh"
   ]
  },
  "risks": [
   {
    "risk": "Thin content",
    "applies": true,
    "mitigation": "Minimum-word + reviewer-sign-off gate before publish."
   },
   {
    "risk": "Duplicate content across state/product variants",
    "applies": true,
    "mitigation": "One URL per topic; no auto-generated variants; canonical to pillar."
   },
   {
    "risk": "Doorway location pages",
    "applies": true,
    "mitigation": "Local pages are refused for this vertical — buyers search by the applicant's counsel, not city."
   },
   {
    "risk": "Keyword cannibalization",
    "applies": true,
    "mitigation": "Topic ownership map; kill or 301 the weaker duplicate."
   },
   {
    "risk": "AI-generated body without human edit",
    "applies": true,
    "mitigation": "Editorial policy forbids it; reviewer sign-off required."
   },
   {
    "risk": "Unsupported YMYL claims",
    "applies": true,
    "mitigation": "Cautious language + primary-source cites + reviewer credential."
   },
   {
    "risk": "Bad schema (marking up invisible content)",
    "applies": true,
    "mitigation": "Schema linter in CI; only markup what is on-page."
   },
   {
    "risk": "Link spam / paid link schemes",
    "applies": true,
    "mitigation": "Editorial link-earning only; documented policy."
   },
   {
    "risk": "Review manipulation",
    "applies": false,
    "mitigation": "Post-engagement organic prompts only; no incentives; no gating negatives."
   },
   {
    "risk": "Index bloat from tag/archive pages",
    "applies": true,
    "mitigation": "noindex utility archives; canonical to hub."
   },
   {
    "risk": "Compliance risk in claims",
    "applies": true,
    "mitigation": "Legal review of marketing claims; disclaimer near CTAs."
   },
   {
    "risk": "Programmatic doorway pages",
    "applies": true,
    "mitigation": "Programmatic refused unless per-page uniqueness rules are met."
   }
  ],
  "first_20_pages": [
   "Homepage",
   "Product / service page",
   "About + reviewer bio",
   "Editorial policy",
   "Contact / start a pack",
   "Privacy",
   "Pillar: applicant PA Cost Documentation — definitive guide",
   "The seven PA cost documentation recovery file items, step by step",
   "applicant PA cost documentation edge cases",
   "applicant PA cost documentation FAQs",
   "Pillar: Civil Code 2 CFR 200/2 CFR 200 evidence & completeness",
   "Civil Code PA cost documentation recovery file requirements",
   "applicant PA cost documentation completeness checklist",
   "Annual recovery report distribution deadlines (2 CFR 200 pre-project window math)",
   "PA cost documentation recovery file source-trace template (lead magnet)",
   "Statute page: Civ. Code 2 CFR 200",
   "Statute page: Civ. Code 2 CFR 200",
   "Statute page: Civ. Code the warranty of eligibility (§38-12-503)",
   "Comparison: PA cost documentation recovery file vs applicant software templates",
   "Quarterly leginfo change-log post"
  ],
  "first_10_tech_fixes": [
   "XML sitemap generated at build",
   "robots.txt reviewed + sitemap referenced",
   "Self-referencing canonicals",
   "GSC + GA4 verified with server-side events",
   "Core Web Vitals baseline (LCP, INP, CLS)",
   "Structured breadcrumbs sitewide",
   "Author + editorial-policy pages published",
   "404 + 410 patterns defined",
   "Redirect audit (no chains)",
   "Semantic HTML + accessibility landmarks"
  ],
  "first_10_authority_actions": [
   "Publish named reviewer bio(s)",
   "Public editorial policy + correction policy",
   "Cite primary the applicant's counsel sources with visited-on dates",
   "Launch checklist lead magnet",
   "Pitch 3 HARO / Qwoted responses per week",
   "Publish 1 original data point / benchmark",
   "Reach out to 5 non-competing directories",
   "Guest post on 1 industry disaster event blog",
   "Podcast interview outreach (5 shows)",
   "Set up quarterly the applicant's counsel change-log post cadence"
  ],
  "final_recommendation": "Build a statute-fluent authority site around \"applicant PA Cost Documentation\". Ship the trust surface, the product page, and the 2 CFR 200 pillar first; earn links with the source-trace template and the annual benchmark; keep every statute page primary-source-cited with a change log. Do not build city pages, programmatic doorways, or national content — the buyer searches by statute and form, and the season decides the calendar.",
  "disclaimers": [
   "All volume/difficulty/CPC labels are RELATIVE ESTIMATES (low/medium/high), not exact numbers. Validate with Semrush, Ahrefs, or Google Search Console before committing spend.",
   "This brief is deterministic per blueprint — it will not shift between renders. Any changes should be made in code, not in prompts.",
   "YMYL topic: language must stay cautious; nothing here is legal/medical/financial advice."
  ]
 },
 "microsite": {
  "category": "FEMA Public Assistance documentation, recovery & appeals",
  "shortTitle": "Reoblige",
  "audience": "Recovery coordinators, grants managers, and CFOs at mid-market FEMA Public Assistance applicants — private nonprofit hospitals, private colleges, electric and water co-ops, special districts, and small municipalities",
  "problem": "The pattern at every mid-market applicant: the eligible work is done, but the cost records live in scattered payroll exports, invoices, force-account timesheets, PO systems, and insurance settlements. FEMA obligates the dollars fast and reconciles them slowly, and when a cost \"cannot be verified with the documentation provided\" it gets deobligated at closeout — often years later, on a hard 60-day clock nobody was watching.",
  "offer": "On Reoblige, recovery teams stop hand-assembling FEMA binders and start defending obligated dollars. Cost records land at intake; every cost line is mapped to PAPPG V5 eligibility and 2 CFR 200 cost principles; the gap scan flags exactly what FEMA will cite; a senior PA specialist releases; the authorized representative certifies and submits the Recovery File.",
  "faq": [
   {
    "q": "Which teams get value from Reoblige on day one?",
    "a": "Reoblige sits between the recovery coordinator who owns the FEMA relationship and the finance office that certifies the numbers. The coordinator hands off cost records and prior FEMA letters; the desk hands back a certification-ready Recovery File — both sides work from the same source-trace record."
   },
   {
    "q": "What makes a Recovery File defensible when FEMA or a Single Audit reads it closely?",
    "a": "The record an auditor would ask for is the record the file already carries: every cost line → source document → page → eligibility basis → specialist release, tied to the Project Worksheet and held through the grant period plus the retention window. The completeness checklist shows green, yellow, or red per cost category, with a named owner for anything open."
   },
   {
    "q": "What do I actually get back from Reoblige?",
    "a": "A closeout-grade Recovery File: every reimbursable cost (labor, equipment, materials, contracts, force account) mapped to PAPPG V5 and 2 CFR 200, the insurance-offset reconciliation, procurement checks, a drafted Project Worksheet or Request for Information response, a source-trace appendix, the statutory completeness checklist, and — where FEMA has denied or deobligated — a drafted first or second appeal with correct policy citations, filed before the 60-day clock."
   },
   {
    "q": "Is there a shelf price for the work?",
    "a": "Yes — fixed fees, never hourly and never contingency. A Deobligation Defense appeal package runs $6,000–$18,000 by project size; a Closeout Documentation Package runs $2,500–$9,000 per project; a FEMA HQ second appeal runs $10,000–$30,000; a Managed Recovery retainer runs $4,000–$15,000 per month capped to the management-cost budget. The Deobligation-Risk Scan is free."
   },
   {
    "q": "Why fixed fee instead of a percentage of what you recover?",
    "a": "Because 2 CFR 200.459 makes contingency and percentage-of-recovery professional fees unallowable for federally reimbursed grant work. A contingency consultant can quietly make your own recovery unreimbursable. Our fixed fees are scoped to fit inside the 5% subrecipient management-cost pool, so the fee itself is reimbursable."
   },
   {
    "q": "Do you file with FEMA on our behalf?",
    "a": "No — you stay the applicant of record. We prepare the Recovery File, the Project Worksheet, and the appeal; your authorized representative certifies and submits to the Recipient and FEMA. We never certify or file, and we do not provide legal advice or represent you in arbitration."
   },
   {
    "q": "We already hired a big disaster-recovery consultant — how are you different?",
    "a": "The national firms serve the large state and county programs. Mid-market private nonprofits and small governments are too small for them to prioritize, so the evidence file gets built half-way. Reoblige is built for exactly that under-served applicant: the same PAPPG-grade file, at a fixed reimbursable fee, without the national-program minimum."
   },
   {
    "q": "How fast can you move when a deobligation letter shows up?",
    "a": "The 60-day appeal clock starts the day you receive the Determination Memo. Send it to the free Deobligation-Risk Scan the same week; a scoped Deobligation Defense engagement can begin within 3 business days of complete intake so the drafted appeal reaches your authorized representative with time to certify."
   },
   {
    "q": "What happens to our records — is the data handled securely?",
    "a": "Cost records enter through a secure intake portal, are processed to a canonical cost-line schema, and are retained only through the grant period plus the required 2 CFR 200 retention window. Access is limited to the analysts and the senior PA specialist assigned to your disaster event."
   }
  ],
  "process": [
   {
    "title": "Intake",
    "body": "Cost records, prior FEMA letters, and insurance settlements land in the secure portal against a structured checklist per Project Worksheet."
   },
   {
    "title": "Normalize",
    "body": "Every document is parsed to a canonical cost-line schema — source doc, date, amount, category, project, facility."
   },
   {
    "title": "Eligibility map",
    "body": "Each cost line is mapped to PAPPG V5 eligibility and 2 CFR 200 cost principles; ineligible and edge-case work is flagged."
   },
   {
    "title": "Gap scan",
    "body": "The engine tests cost reasonableness, runs the insurance-offset math and procurement checks, and predicts exactly what FEMA will cite."
   },
   {
    "title": "Specialist release",
    "body": "A senior PA specialist reviews flagged items, the drafted Project Worksheet or appeal, and red-teams the file: \"will FEMA cite this?\""
   },
   {
    "title": "Certify & submit",
    "body": "The authorized representative certifies; the Recovery File and submission checklist go to the Recipient and FEMA with a full audit trail."
   }
  ],
  "northStarCta": {
   "label": "Get a free Deobligation-Risk Scan",
   "href": "#diagnostic",
   "secondary_label": "View the full operating blueprint dossier",
   "secondary_href": "/fema-public-assistance-recovery-engine/blueprint/"
  },
  "ubiquitousLanguage": {
   "audience": "recovery coordinator",
   "domain": "FEMA Public Assistance documentation, recovery & appeals",
   "deliverable": "Recovery File",
   "reviewer": "senior PA specialist",
   "record": "cost line",
   "unit_of_work": "Project Worksheet",
   "cta_primary": "Get a free Deobligation-Risk Scan",
   "cta_secondary": "View the full operating blueprint dossier",
   "regulator": "FEMA",
   "regulator_full": "Federal Emergency Management Agency",
   "statute": "PAPPG V5 & 2 CFR 200",
   "trigger_moment": "a Determination Memo, deobligation letter, or approaching closeout deadline",
   "event_intake_started": "domain.intake_started",
   "event_conversation_requested": "domain.diagnostic_requested"
  },
  "trust": {
   "standards": [
    "Fixed, reimbursable fees — never hourly, never contingency (2 CFR 200.459)",
    "Prepared by a senior PA specialist; certified and filed by your authorized representative",
    "Built to survive a 2 CFR 200 Subpart F Single Audit and DHS OIG review"
   ],
   "response_time": "Deobligation-Risk Scan returned within 5 business days; scoped engagements begin within 3 business days of complete intake.",
   "data_handling": "Cost records enter a secure intake portal and are retained only through the grant period plus the 2 CFR 200 retention window."
  },
  "hook": "FEMA obligated your disaster money. Keeping it is a documentation problem.",
  "sub_headline": "Reoblige builds the PAPPG-grade evidence file — and drafts the appeal — that keeps obligated FEMA Public Assistance dollars from being deobligated at closeout.",
  "dream_outcome": "Every eligible federal dollar survives audit and deobligation, and denied dollars come back on appeal — with a file your board and your auditors can trust.",
  "specific_pains": [
   "Labor and equipment costs deobligated because they \"could not be verified with the documentation provided\".",
   "A Determination Memo lands and the 60-day appeal clock is already running.",
   "A contingency consultant's fee turns out to be unallowable under 2 CFR 200.459, putting your own recovery at risk.",
   "Insurance proceeds not reconciled, triggering a Stafford Act §312 duplication-of-benefits recovery.",
   "Procurement defects under 2 CFR 200.317–327 surface at closeout and unwind reimbursement."
  ],
  "cost_of_inaction": "Six- and seven-figure reimbursements are recovered by FEMA at closeout, the 60-day appeal window closes, and the finance office is personally accountable for federal dollars that were eligible but never defensibly documented.",
  "mechanism": {
   "name": "The Deobligation-Defense Engine",
   "steps": [
    {
     "title": "Aggregate",
     "body": "Pull every reimbursable cost from payroll, invoices, timesheets, PO systems, and insurance settlements into one canonical cost ledger."
    },
    {
     "title": "Map",
     "body": "Classify each cost line against PAPPG V5 eligibility and 2 CFR 200.404 reasonableness."
    },
    {
     "title": "Reconcile",
     "body": "Run insurance-offset math and procurement checks so no duplication or defect survives to closeout."
    },
    {
     "title": "Predict",
     "body": "Red-team the file against FEMA's own appeal record to surface exactly what would be cited — and fix it first."
    },
    {
     "title": "Defend",
     "body": "Draft the Project Worksheet, RFI response, or first/second appeal with correct citations for your authorized representative to certify."
    }
   ]
  },
  "offer_stack": [
   {
    "item": "Deobligation-Risk Scan",
    "note": "Free — portfolio-level read of where obligated dollars are exposed."
   },
   {
    "item": "Closeout Documentation Package",
    "note": "$2,500–$9,000 per project — closeout-grade Recovery File."
   },
   {
    "item": "Deobligation Defense (MVP)",
    "note": "$6,000–$18,000 per appeal package — binder plus drafted first appeal."
   },
   {
    "item": "Second Appeal (FEMA HQ)",
    "note": "$10,000–$30,000 per second appeal."
   },
   {
    "item": "Managed Recovery Program",
    "note": "$4,000–$15,000/mo per disaster event, capped to the management-cost budget."
   },
   {
    "item": "Source-trace appendix & audit trail",
    "note": "Included — every cost line traced to its source page and release."
   }
  ],
  "guarantee": "If the Deobligation-Risk Scan finds no recoverable exposure in your obligated projects, there is nothing to buy and you owe nothing. Every engagement is a fixed, reimbursable fee agreed before work begins — never hourly, never a percentage of what FEMA restores.",
  "urgency": "FEMA administrative appeals run on a hard 60-day clock from the date you receive the Determination Memo. Miss it and the written record closes.",
  "objections": [
   {
    "q": "Isn't this just something our accountant can do?",
    "a": "A general accountant knows GAAP; they do not know PAPPG V5, 44 CFR Part 206 Subpart G, or which cost narratives survive a FEMA second appeal. Deobligation is a policy-citation problem, not a bookkeeping one."
   },
   {
    "q": "Can we afford it in a disaster year?",
    "a": "The fee is scoped to fit inside the 5% subrecipient management-cost pool that FEMA itself funds — so in most engagements the file that defends your dollars is paid for with FEMA-funded dollars, not your general fund."
   },
   {
    "q": "Do we hand over control of our FEMA relationship?",
    "a": "No. You stay the applicant of record and your authorized representative certifies every filing. We are the invisible production engine; the specialist is your file's last set of eyes before you sign."
   },
   {
    "q": "What if FEMA still denies the appeal?",
    "a": "The appeal is argued on the written record against the PAPPG and 2 CFR 200. We build the strongest record the facts support and tell you honestly when an appeal is not winnable — including when to escalate to arbitration with counsel, which is outside our scope."
   },
   {
    "q": "We are a small applicant — are we too small for this?",
    "a": "That is exactly who Reoblige is for. The national consultancies prioritize large programs; the mid-market self-serves and bleeds recoverable dollars. Fixed per-deliverable pricing means a single Project Worksheet is a viable engagement."
   },
   {
    "q": "Is the AI making the eligibility calls?",
    "a": "No. The engine extracts, classifies, reconciles, and drafts; a senior PA specialist makes every eligibility and appeal-strategy judgment, and your authorized representative certifies. Two human chokepoints gate the file."
   }
  ],
  "who_this_is_not_for": [
   "Large state or county programs already served by a national disaster-recovery consultancy.",
   "Applicants seeking a percentage-of-recovery or contingency arrangement — that fee structure is unallowable here.",
   "Matters already in Civilian Board of Contract Appeals arbitration or litigation, which require counsel."
  ],
  "proof_pillars": [
   {
    "title": "Reimbursable by design",
    "body": "Fees are scoped to the 5% subrecipient / 7% recipient management-cost pool under Stafford Act §324 and DRRA §1215 — the fee source FEMA funds."
   },
   {
    "title": "Policy-current",
    "body": "Every file is built to PAPPG Version 5, effective for declarations on or after January 6, 2025 and amended August 2025 — the ruleset every applicant now files under."
   },
   {
    "title": "Audit-survivable",
    "body": "Deliverables are constructed to withstand a later 2 CFR 200 Subpart F Single Audit and DHS OIG review, not just the FEMA reconciliation."
   }
  ],
  "stakes_line": "FEMA recorded billions in Disaster Relief Fund deobligations in FY2025 (CRS) — much of it for documentation gaps, not ineligible work.",
  "deliverable": "Recovery File",
  "unit_of_work": "Project Worksheet",
  "lexicon": {
   "regulator": "FEMA",
   "regulator_full": "Federal Emergency Management Agency",
   "statute": "PAPPG V5 & 2 CFR 200",
   "statute_frame": "Stafford Act §§406/407, 44 CFR Part 206 Subpart G, 2 CFR Part 200, and the Public Assistance Program and Policy Guide Version 5",
   "persona": "recovery coordinator",
   "persona_moment": "staring at scattered cost records with a closeout or appeal deadline approaching",
   "trigger_moment": "a Determination Memo, Request for Information, deobligation letter, or approaching project closeout",
   "enforcement_stakes": "FEMA deobligates obligated funds — recovering six- and seven-figure reimbursements — when costs cannot be verified or tied to eligible work.",
   "retention": "the grant period plus the 2 CFR 200 record-retention window",
   "cta_verb": "scan",
   "intake_checklist": [
    "Force-account and contract labor records for each Project Worksheet",
    "Equipment usage logs and applicable FEMA equipment rates",
    "Materials invoices and inventory of consumed stock",
    "Executed contracts and the procurement file (solicitation, bids, award)",
    "Insurance policies and settlement statements for offset reconciliation",
    "Prior FEMA letters — Determination Memos, RFIs, deobligation notices",
    "Damage descriptions, scope-of-work, and supporting photos"
   ],
   "trust_standards_specific": [
    "Fixed per-deliverable fees, reimbursable within the 5% subrecipient management-cost pool",
    "Never hourly, never cost-plus, never percentage-of-recovery (2 CFR 200.459)",
    "Prepared for certification by your authorized representative — we never file",
    "Insurance-offset reconciliation to prevent Stafford Act §312 duplication of benefits",
    "Deadline tracking against the 60-day appeal clock at each tier"
   ],
   "regulator_faqs": [
    {
     "q": "What is a deobligation?",
     "a": "When FEMA reconciles a Public Assistance project and finds claimed costs it cannot verify as incurred, reasonable, and tied to eligible work, it deobligates — recovers — those funds, even years after the money was first obligated."
    },
    {
     "q": "What is the management-cost pool?",
     "a": "Under Section 1215 of the Disaster Recovery Reform Act, subrecipients may receive up to 5% and recipients up to 7% of their PA award for the costs of administering the grant — including professional documentation help, which makes our fee reimbursable."
    },
    {
     "q": "What changed with PAPPG Version 5?",
     "a": "PAPPG V5 is effective for disasters declared on or after January 6, 2025 (amended August 2025). It is the current, mandatory policy guide for eligibility, cost, and closeout — the ruleset every new applicant files under."
    },
    {
     "q": "How long is the appeal window?",
     "a": "Applicants have 60 days from receipt of a FEMA determination to file a first appeal, and 60 days from the first-appeal decision to file a second appeal to FEMA HQ. Both run on the written record."
    }
   ]
  },
  "proof_angle": {
   "id": "deobligation-defense",
   "headline": "The evidence file that keeps obligated dollars obligated",
   "lever": "documentation completeness against PAPPG V5 and 2 CFR 200",
   "outcome_verb": "defend",
   "outcome_frame": "obligated FEMA dollars that survive closeout, and denied dollars restored on appeal",
   "proof_promise": "Pilot outcomes will appear here as the first Recovery Files clear FEMA reconciliation — real determinations only, never fabricated."
  },
  "indexable": true
 },
 "evidence": [
  {
   "id": "ev-1",
   "business_slug": "fema-public-assistance-recovery-engine",
   "area": "market",
   "claim_or_finding": "FEMA recorded billions in Disaster Relief Fund deobligations in FY2025 — recoveries of previously obligated grant funds.",
   "status": "verified",
   "evidence": "Congressional Research Service — Disaster Relief Fund State of Play (R47676).",
   "verification_command": "Review CRS R47676 DRF recovery/deobligation figures",
   "fix_owner": "research",
   "remediation": "Refresh figure against latest DRF monthly report each run.",
   "severity": "info"
  },
  {
   "id": "ev-2",
   "business_slug": "fema-public-assistance-recovery-engine",
   "area": "regulatory",
   "claim_or_finding": "PAPPG Version 5 is effective for disasters declared on or after January 6, 2025 (amended August 2025).",
   "status": "verified",
   "evidence": "Federal Register 2024-30084; FEMA PAPPG V5; ICF PAPPG V5 summary.",
   "verification_command": "Confirm PAPPG V5 effective date and amendment on fema.gov / federalregister.gov",
   "fix_owner": "research",
   "remediation": "Track future PAPPG amendments.",
   "severity": "info"
  },
  {
   "id": "ev-3",
   "business_slug": "fema-public-assistance-recovery-engine",
   "area": "fee-source",
   "claim_or_finding": "Management costs under DRRA §1215 allow up to 5% (subrecipient) and 7% (recipient) of the PA award for grant administration — the reimbursable fee source.",
   "status": "verified",
   "evidence": "FEMA Section 1215 Management Costs policy page; DRRA 2018 provisions.",
   "verification_command": "Confirm 5%/7% split on fema.gov Section 1215 Management Costs",
   "fix_owner": "research",
   "remediation": "Monitor any interim-policy updates to management costs.",
   "severity": "info"
  },
  {
   "id": "ev-4",
   "business_slug": "fema-public-assistance-recovery-engine",
   "area": "pricing-constraint",
   "claim_or_finding": "Contingency and percentage-of-recovery professional fees are unallowable for federally reimbursed grant work under 2 CFR 200.459.",
   "status": "verified",
   "evidence": "eCFR 2 CFR 200.459 Professional service costs.",
   "verification_command": "Read 2 CFR 200.459 on ecfr.gov",
   "fix_owner": "research",
   "remediation": "None — foundational pricing rail.",
   "severity": "info"
  },
  {
   "id": "ev-5",
   "business_slug": "fema-public-assistance-recovery-engine",
   "area": "proof-gap",
   "claim_or_finding": "No client outcomes, testimonials, or win-rates exist yet; all proof slots are placeholders keyed to real future FEMA determinations.",
   "status": "placeholder",
   "evidence": "Pre-launch — pilot Recovery Files not yet filed.",
   "verification_command": "Populate only from real FEMA determinations after pilots close",
   "fix_owner": "owner",
   "remediation": "Replace placeholders with real determinations post-pilot; never fabricate.",
   "severity": "high"
  }
 ],
 "seo_pages": {
  "id": "seo-fema-public-assistance-recovery-engine",
  "business_slug": "fema-public-assistance-recovery-engine",
  "route": "/microsites/fema-public-assistance-recovery-engine",
  "title": "Reoblige — FEMA Public Assistance deobligation defense & appeals",
  "description": "Reoblige builds the PAPPG V5 / 2 CFR 200 evidence file and drafts FEMA Public Assistance appeals for mid-market applicants — fixed, reimbursable fees, before the 60-day clock.",
  "canonical": "/microsites/fema-public-assistance-recovery-engine",
  "og_title": "Reoblige — FEMA PA documentation, recovery & appeals",
  "og_description": "Keep obligated FEMA disaster dollars from being deobligated at closeout. Fixed reimbursable fees, senior PA specialist review, drafted appeals before the 60-day clock.",
  "schema_type": "FAQPage",
  "schema_status": "pending-owner-facts",
  "sitemap_include": false,
  "noindex": true
 },
 "vertical_style": {
  "accent": "federal-navy",
  "signature": "Recovery-File tabs with cost-category completeness chips",
  "layout": "Deobligation-defense dossier index",
  "anti": "Cartoon disaster or hurricane mascots"
 },
 "canva": {
  "slug": "fema-public-assistance-recovery-engine",
  "territory": "Deobligation-Defense Dossier",
  "family": {
   "id": "legal-compliance",
   "name": "Legal / Compliance",
   "motion": "calm"
  },
  "tokens": {
   "brand": "208 74% 18%",
   "brand-fg": "210 33% 97%",
   "surface": "210 30% 98%",
   "ink": "212 40% 12%",
   "muted": "212 12% 40%",
   "accent": "28 78% 44%"
  },
  "type": {
   "display": "Libre Caslon Text",
   "body": "Source Sans 3",
   "fonts_url": "https://fonts.googleapis.com/css2?family=Libre+Caslon+Text:wght@400;700&family=Source+Sans+3:wght@400;500;600&display=swap"
  },
  "scale": {
   "h1": "clamp(2.5rem, 5.5vw, 4.25rem)",
   "h2": "clamp(1.75rem, 3vw, 2.5rem)",
   "h3": "clamp(1.25rem, 2vw, 1.5rem)",
   "body": "clamp(1rem, 1.1vw, 1.125rem)",
   "small": "0.8125rem",
   "tracking_display": "-0.02em",
   "tracking_body": "-0.005em",
   "weight_display": 700,
   "weight_body": 450
  },
  "spacing": {
   "card_padding": "1.75rem",
   "card_radius": "0.46rem",
   "card_shadow": "0 0 0 1px hsl(var(--ink) / 0.08)",
   "section_gap": "clamp(3.5rem, 8vw, 6.5rem)",
   "hero_gap": "clamp(1.25rem, 2vw, 2rem)"
  },
  "layout": {
   "hero": "centered-editorial",
   "card": "gradient-frame",
   "cta": "outlined-brand",
   "archetype": "stacked-editorial",
   "card_silhouette": "flat-outline",
   "button_geometry": "sharp"
  },
  "background": {
   "hero_gradient": "radial-gradient(1200px 600px at 10% -10%, hsl(15 64% 36% / 0.18), transparent 60%), radial-gradient(900px 500px at 90% 10%, hsl(217 46% 21% / 0.12), transparent 55%)",
   "cta_gradient": "linear-gradient(135deg, hsl(217 46% 21%), hsl(15 64% 36%))",
   "section_wash": "linear-gradient(180deg, hsl(40 25% 97%) 0%, hsl(217 46% 21% / 0.04) 100%)"
  },
  "motif": "Brief header + exhibit list"
 },
 "capabilities": {
  "marketing": true,
  "portal": true,
  "ops": true,
  "chatbot": true,
  "payments": false
 },
 "generated_at": "2026-07-16T00:48:41Z",
 "checksum": "sha256:85135adb320d415d62d39a41788e1ad5"
}