GTM samples · continuous RADV
Redacted RADV demo walkthrough
What SIU, compliance, and counsel actually open when Horizon Aegis is working. Four RADV profiles of one CREB template on the same demo member: CREB-RADV (unsupported), AREB-RADV (supported), PIEB-RADV, and RREB-RADV (RRADV). Audit model is V24 (V22/V24 live; V28 ready, not active). No live PHI. No contingency recovery story. Shadow mode is the default.
ready_not_active. CourtChain™ public blocks are S3 encrypted custody for filing digests, not L1 BFT consensus. Simulation outputs are model exposure, not a CMS recovery guarantee. Default evaluation mode is shadow (no payment rail impact).
1. Scenario (synthetic)
Contract H0000-DEMO, payment year 2025, member member-demo-001. Horizon Aegis scores documentation support on V24 while claim traffic continues. V28 is not applied. Nothing holds or denies payment until a customer elevates governance out of shadow.
- Mode
shadow(default)- Cycle
- Shadow → Package → Seal → Act
- Seal path
POST /v1/profiles/radv/sealon creb-service- Ownership
- Institution owns packages; JIL is the neutral sealer
2. Side by side
CREB-RADV — findings issued
Adverse / unsupported path. Sample HCC18 (diabetes with complications framing) lacks contemporaneous assessment, monitoring, or treatment documentation in the evaluation window—only a historical mention.
- Disposition
FINDINGS_ISSUED- Support score
- 0.15 · evidence strength
none - Action
escalate_to_siu- Simulated impact
- $2,400 (illustrative model exposure, not recovery)
- Seal status
ready_for_seal· schemacreb-radv-1.0
AREB-RADV — supported
Affirmative path. Same demo estate, HCC19 with a progress note that assesses type 2 DM, monitors glucose, and continues metformin—documentation spans present for the evaluation window.
- Disposition
SUPPORTED- Support score
- 0.92 · evidence strength
strong - Summary
- 1 HCC evaluated · fully supported
- Doc elements
- Assess · Monitor · Treat (clinical note fields—not a CMS “MEAT standard” claim)
- Seal status
ready_for_seal· schemaareb-radv-1.0
3. How a buyer walks the demo
- Open the JSON samples — confirm fields counsel care about: disposition, evidence excerpts, content_hash placeholder, sealing_metadata.
- Map to continuous readiness — packages draft while charts are still current, not after the CMS sample letter.
- Seal narrative — creb-service validates the RADV profile and seals a
legal_evidence_bundle(lob=radv). Optional CourtChain public block for filing digest match without decrypting PHI. - Act in SIU — prioritize escalate paths, keep supported packages for sample-day handoff, never invent a recovery guarantee from simulation alone.
- Commercial posture — flat platform fee for contracted scope. No contingency cut of recoveries. Diligence packet + MSA/DPA samples linked below.
4. Related institutional resources
Inside a CREB™
What MFCU, auditors, and counsel receive as the sealed record structure.
Vendor diligence
Procurement and security packet; sample MSA & DPA drafts.
One-pagers & briefs
Institutional briefs library for SIU, finance, and counsel audiences.
The output is the product
Request an Evidence Audit
Bring a RADV exposure question or MCO claim pattern. We return sealed sample paths and architecture—not a spreadsheet of flags.