Data model
The skill is Markdown-driven, but its output follows a stable conceptual model.
Decision context
Section titled “Decision context”type DecisionContext = { decision: string quantity: string unit: string timeHorizon: string threshold: number | string | null costOfBeingWrong: string estimateMode: string}Evidence
Section titled “Evidence”type Evidence = { label: string value: number | string sourceUrl?: string observedAt?: string classification: "confirmed" | "assumption" | "inference" quality: "high" | "medium" | "low" freshness: "current" | "aging" | "stale" | "unknown"}Decomposition
Section titled “Decomposition”type ComponentEstimate = { component: string low: number central: number high: number confidence: string basis: string whatWouldTighten: string}Remaining uncertainty
Section titled “Remaining uncertainty”type MeasurementCandidate = { uncertainty: string measurement: string costOrEffort: string expectedDecisionImpact: string stopWhen: string}Result relationships
Section titled “Result relationships”Decision context │ ├── Evidence ──> Component estimates │ │ │ └──> Calibrated interval │ │ └── Threshold ──────────────────┤ ├──> Decision implicationRemaining uncertainty ────────────────┘ │ └──> Next measurement step
All sections ──> Written memo + HTMA_RESULTThe written memo preserves reasoning and provenance. HTMA_RESULT preserves stable fields for scoring, automation, and later calibration review.