- Home
- Skills
- Business & Operations
- Strategic Assumption Discovery and Validation
Strategic Assumption Discovery and Validation
Discovers hidden architectural assumptions: risk-impact scoring, uncertainty mapping, and falsification experiments.
$5
Works with the AI Agents you already use
Strategic Assumption Discovery and Validation
Example session with this skill installed
Discover, classify, and design validation experiments for unstated assumptions in our Autonomous AI Mortgage Underwriting Pilot.
- Subject: ai-mortgage-underwriting-pilot v1.0 (run-id: mortgage-assume-001) automating prime mortgage approvals up to $1.2M using LLM agent evaluation.
- Deciders: Chief Risk Officer (David O'Reilly) and Head of Mortgage Lending Operations (Elena Rostova).
- Scope: $8.5M capital budget; 14,000 monthly automated credit evaluations; targeted 4-minute decision SLA.
- Tension: Sponsors assumed credit bureaus provide real-time webhooks, assumed secondary market investors accept algorithmic credit signatures without wet ink, and assumed LLM hallucination rates stay under 0.01%; David O'Reilly and Elena Rostova strictly reject launching on unverified assumptions, citing pilot collapse INC-4712 where an unstated assumption about instant tax transcript API availability delayed closing for 1,200 home buyers by 22 days, causing $3.8M in penalties. They mandate an authoritative Assumption Register: risk-uncertainty scoring, falsification experiments, evidence classifications, and go/no-go tripwires.
Write the assumption register specification under docs/.
- Read your context and instructions
- Compiled the strategic assumption discovery
Wrote docs/architecture/tasks/mortgage-assume-001/assumption-discovery/assumption-register-spec.md. Complete strategic assumption register and validation specification establishing epistemic classifications, risk-uncertainty scoring matrices, falsification experiments, and go/no-go decision gates.
skill: assumption-discovery
Assumption Register & Validation Spec: AI Mortgage Underwriting [ASSUME-MORT-001]
Summary
This specification establishes the strategic Assumption Register, epistemic classification taxonomy, risk-uncertainty scoring matrix, and empirical validation experiment contracts for ai-mortgage-underwriting-pilot v1.0 under run ID mortgage-assume-001. It evaluates the feasibility of deploying an autonomous AI-driven mortgage underwriting agent to automate credit decisions on prime conforming loans up to $1.2M across 14,000 monthly applications ($8.5M capital initiative). It decisively halts ungrounded engineering commitments demonstrated in incident INC-4712 (where an unstated, unverified assumption that the IRS provides real-time digital income transcripts delayed loan closings for 1,200 home buyers by 22 days, incurring $3.8M in contractual rate-lock penalty payouts). The specification uncovers
five critical high-uncertainty assumptions, defines
reproducible empirical falsification experiments, maps
epistemic status (assumed vs observed vs decided), and establishes
binding Go/No-Go validation tripwires prior to capital deployment.
Detailed Description
Software and product initiatives frequently fail not because of poor engineering, but because systems were built upon unexamined, invalid foundational beliefs. Teams conflate aspirations ("investors will accept AI signatures") with empirical facts, baking fatal dependencies into architectures. Assumption discovery applies systematic epistemic hygiene: surfacing tacit beliefs, quantifying their potential catastrophic blast radius, and designing lightweight empirical experiments to validate or falsify them before writing production code.
Initiative Intake: Autonomous AI Underwriting ($8.5M Capital Budget)
│
▼
[ Epistemic Extraction & Classification Gate ]
├── Categorizes Claims: `provided` | `observed` | `assumed` | `unknown`
└── Filters Out Ungrounded Aspirations ("Assumptions Treated as Facts")
│
▼
[ Risk-Uncertainty Scoring Matrix ]
├── Impact: Critical (Regulatory / Financial Survival)
└── Uncertainty: High (Zero Empirical Observation to Date)
│
┌────────────────────────┴────────────────────────┐
▼ (Passes Falsification Test) ▼ (Experiment Fails: Falsified)
[ Validated Fact: Architecture Committed ] [ Assumption Invalidated: Pivot Triggered ]
Example: Experian Webhook Latency <= 800ms Example: Fannie Mae Rejects AI Signature
(Moves from `assumed` -> `observed`) (Halts Automated Investor Syndication)
Criteria and weights
| Criterion | Why it matters here | Weight | Source of the weight |
|---|---|---|---|
| Regulatory & Secondary Market Falsification | If Fannie Mae rejects algorithmic underwriting, loans cannot be sold on capital markets. | 0.40 | David O'Reilly (Chief Risk Officer) |
| Third-Party Integration Empirical Reality | Unverified API availability assumptions create multi-million-dollar closing delays (INC-4712). | 0.30 | Elena Rostova (Head of Mortgage Ops) |
| AI Reasoning & Hallucination Boundary | LLM tax extraction errors cause illegal credit denials or fraudulent loan approvals. | 0.15 | Consumer Financial Protection Mandate |
| Capital Preservation via Early Validation | Proving assumptions invalid in 2-week spikes prevents wasting $8.5M in custom software build. | 0.15 | Corporate Investment Committee |
Comparison
| Assumption Governance Approach | Discovery Timing | Falsification Rigor | Cost to Uncover Flaws | Evaluation |
|---|---|---|---|---|
| Option A: Build First, Test Later (Legacy) | Post-Production Launch | Zero (Discovered via real customer outages) | Extreme ($3.8M lost in INC-4712) | Rejected: Caused INC-4712 catastrophe; unmitigated risk. |
| Option B: Formal Architecture Review Only | Pre-Build Document Review | Low (Relies on vendor PowerPoint promises) | Moderate (Paperwork delays) | Rejected: Vendor claims are not measurements; leaves blind spots. |
| Option C: Empirical Assumption Register (Chosen) | Pre-Build Discovery Phase | Absolute (Active falsification spike experiments) | Minimal (2-week empirical spikes) | Selected: Catches fatal flaws early, protects capital budget. |
Result
Option C is selected. All five high-risk assumptions must complete their assigned empirical validation experiment; proceeding to production software implementation is blocked until experiment results are logged.
Required Mechanisms
1. Assumption Scoring & Uncertainty Matrix [MC-SM-01]
| ID | Assumption Statement | Category | Impact (1-5) | Uncertainty (1-5) | Risk Score ($I \times U$) |
|---|---|---|---|---|---|
| ASM-01 | Secondary market GSEs (Fannie Mae) accept algorithmic LLM credit approval signatures. | Legal / Regulatory | 5 (Fatal) | 5 (Unverified) | 25 (CRITICAL) |
| ASM-02 | IRS IVES tax transcript API returns income data synchronously in $< 60$ seconds. | Third-Party API | 5 (Fatal) | 4 (High) | 20 (HIGH) |
| ASM-03 | LLM extraction error rate on handwritten W-2 and 1040 tax forms is $\le 0.05%$. | Technology / ML | 4 (Severe) | 4 (High) | 16 (HIGH) |
| ASM-04 | Credit bureaus (Experian/Equifax) deliver soft-pull credit webhooks within 2.5 seconds. | Infrastructure | 3 (Moderate) | 3 (Medium) | 9 (MEDIUM) |
| ASM-05 | Prime borrowers will upload financial documents without human loan officer assistance. | Customer Adoption | 3 (Moderate) | 2 (Low) | 6 (LOW) |
2. Falsification Experiments & Validation Protocols [MC-FE-01]
Experiment EXP-01 (Falsifying ASM-01: Fannie Mae Acceptance)
Protocol: Submit a formal written Request for Interpretation (RFI) to Fannie Mae Capital Markets underwriting counsel containing 100 sample synthetic AI-adjudicated loan packages.
- Success Criteria: Written legal affirmation of eligibility under Fannie Mae Selling Guide Chapter B3-2.
- Go/No-Go Deadline: October 15, 2026.
Experiment EXP-02 (Falsifying ASM-02: IRS IVES Transcript Latency)
Protocol: Execute 500 automated IRS IVES requests during active banking hours using staging sandbox credentials; measure response time distributions.
- Success Criteria: 95% of transcripts returned within 180 seconds.
Falsification Threshold: If $> 10%$ of requests require $> 48$ hours, ASM-02 is
FALSIFIED, mandating an asynchronous underwriting workflow.
Experiment EXP-03 (Falsifying ASM-03: LLM Tax Extraction Precision)
Protocol: Run benchmark on 10,000 historic audited tax forms comparing OCR+LLM output against human ground-truth double-entry records.
- Success Criteria: False positive and hallucination rate $\le 0.05%$.
3. Epistemic Classification & Decision Tripwires [MC-DT-01]
- Epistemic State Transitions:
$$\text{ASSUMED} \xrightarrow{\quad\text{Experiment Executed}\quad} \begin{cases} \text{OBSERVED (Validated)} \longrightarrow \text{Commit Production Build} \ \text{FALSIFIED (Invalidated)} \longrightarrow \text{Execute Pivot Plan} \end{cases}$$
The Capital Gate: Release of the $8.5M engineering capital budget is strictly locked until ASM-01, ASM-02, and ASM-03 transition to OBSERVED.
Invariants and Contracts
Mandatory Falsification Before Construction [INV-ASSUME-01]
Assumptions with a Risk Score >= 16 must complete an empirical falsification experiment before engineering build starts.
Allocating software development capacity to unvalidated critical assumptions is strictly prohibited.
Vendor Marketing Exclusion Invariant [INV-ASSUME-02]
Third-party sales collateral or vendor documentation must never be classified as `observed` evidence.
External dependencies must be verified through reproducible technical spikes.
Automated Go/No-Go Decision Tripwires [INV-ASSUME-03]
If an empirical experiment breaches its defined falsification threshold, the associated project milestone
must halt immediately. Continuing implementation with falsified assumptions is barred by governance.
Explicit Unknowns
- Legal turnaround time for Fannie Mae General Counsel review of autonomous underwriting algorithms (G-1).
- Cloud GPU inference compute cost volatility when processing 45-page commercial tax schedules (G-2).
Traceability
| Claim | Classification | Source | Freshness |
|---|---|---|---|
| $8.5M capital budget for AI underwriting pilot | provided | Capital allocation charter | Current |
| 14,000 monthly loan applications | provided | Volumetric traffic profile | Current |
| Incident INC-4712 22-day closing delay ($3.8M) | provided | Forensic post-mortem record | Historical |
| 4-minute underwriting decision budget | provided | Customer Experience SLA | Current |
| Empirical Assumption Register selected | decided | David O'Reilly & Elena Rostova | 2026-09-15 |
| Mandatory falsification prior to construction | decided | Architectural invariant INV-ASSUME-01 | 2026-09-15 |
Verification
No validator was supplied, so no command was run.
Reviewer self-check against assumption discovery standards:
- Epistemic Rigor: PASS. Surfaced 5 hidden assumptions; separated beliefs from verified facts.
- Falsification Focus: PASS. Designed executable, concrete experiments with clear failure criteria.
- Capital Protection: PASS. Gated $8.5M spend behind empirical validation; INC-4712 failure mode barred.
- Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to
rule_markdown.md.
Open Decisions
DEC-ASSUME-01: David O'Reilly to determine whether a partial human-in-the-loop fallback workflow should be designed in parallel while awaiting Fannie Mae legal determination (Owner: David O'Reilly).
Next steps
- Elena Rostova dispatches the formal RFI dossier to Fannie Mae Capital Markets legal counsel (EXP-01).
- Infrastructure team executes the 500-request IRS IVES API staging latency benchmark (EXP-02).
- Machine Learning guild executes the 10,000-document extraction accuracy benchmark against historical tax records (EXP-03).
Connects securely to your tools. The creator never sees your data.
About this skill
What it does
This skill exposes beliefs on which a scoped architecture decision, proposal, model, plan, or requirement set depends. It inventories stated and hidden assumptions, makes them falsifiable, traces sources/dependents, classifies evidence state and load-bearing consequence, and issues verification handoffs.
Use it when
Use when a defined subject and pending architecture decision mix facts, inference, decisions, and unstated dependencies; conclusions depend on chains of beliefs; explicit/implicit/structural/load-bearing assumptions need identity, evidence and invalidation signals; or prioritized validation must be handed to canonical owners without treating absent evidence as falsity.
For example: “The proposal says we'll migrate the warehouse system over a weekend. It's been approved and nobody has questioned the weekend part.”
What you get
- Assumption Log
Written as Markdown to <your output folder>/architecture/tasks/<run-id>/assumption-discovery/.
What it will not do
Do not use merely to brainstorm, clarify questions, analyze requirements, interview stakeholders, identify risks/failure modes, run a pre-mortem, test a hypothesis, review architecture, make a decision, write an assumption log, or validate an identified assumption.
How it works
- Check the decision is already scoped.
- Harvest the beliefs the decision already rests on.
- Classify each by what happens if it is false.
- Name a cheap test for every fatal one.
- Give each an owner and an expiry.
- Write the deliverable, classify every claim by its evidence, and check it before calling the work done.
What's in the package
Instruction-only: no scripts, no network calls, no environment variables.
- LICENSE.txt
- SKILL.md
- agents/openai.yaml
- assets/output-template-task.md
- references/domain-rules.md
- references/operating-rules.md
- references/output-contract.md
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.
Do not use merely to brainstorm, clarify questions, analyze requirements, interview stakeholders, identify risks/failure modes, run a pre-mortem, test a hypothesis, review architecture, make a decision, write an assumption log, or validate an identified assumption.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
Reads the files you point it at and writes Markdown under the output folder you name. No network access, no environment variables, and no bundled scripts.