Real provider evidence · Live packet-engine replay

One sentence in.
The real work out.

A parent wanted piano lessons at Musicamente covered through OPWDD Self-Direction. A family reported that a separate Musicamente request was approved on its first submission. Run the evidence we can show through Kit below.

Verified in this replay: the provider-issued flyer, public evidence, policy route, and packet logic. Family-reported context: a separate first-submission approval whose family, exact FI, submitted packet, approval notice, and metadata remain with the family. The engine fails closed where those facts matter.
Parent submission

One sentence. No form maze.

Type the request exactly as a parent would. This is the input to the live packet engine, not a staged slide.

1 of 6
This public replay sends no family or health information.
Generated packet

The form is not the product.
The finished work is.

Run the case above to see the engine classify the request, map public evidence, create the work queue, and assemble the packet.

Inspect the public packet ↓
01Cover + requestRecipient, route, amount, review state
02Evidence indexEvery requirement mapped to a source or gap
03Provider sheetCurrent facts separated from requested confirmation
04Family addendumPrivate plan and budget facts stay private
05FI adapterSubmission method and correction path require the exact FI
06Family outcome ledgerReceipt, decision, dollars, labor, verification, and consent stay family-controlled
Sources used in this replay
OPWDD IDGS Addendum A.4Governing Community Classes rule ↗MusicamenteProvider identity and offerings ↗Musicamente · The SpacesPublic lesson-location page; differs from provider flyer ↗Musicamente class-approval flyerProvider-issued format, duration, rate, contact, and address ↗