Current Coverage
Coverage means what public-service path UMMAYA can represent with evidence. It does not mean every task in a domain can be completed today.
Read coverage by user outcome and state label. Live, Mock, Handoff, and Planned are different promises, and the docs should not blur them.
The new Live Adapters page explains the existing KMA, KOROAD, HIRA, NMC, NFA, and MOHW surface together with the public-data expansion wave. Read the count as the current registry evidence: 42 live find adapters and 5 live locate provider adapters, not merely “thirty new APIs.”
Coverage Summary
Section titled “Coverage Summary”| User outcome | Current state | Evidence source |
|---|---|---|
| Weather, forecast, warning, public safety, and air-quality lookup | Live | KMA, AirKorea, and MOIS public-data adapters where configured |
| Road, bus, subway accident/hazard/arrival/fare lookup | Live | KOROAD, TAGO, and DJTC public-data adapters where configured |
| Hospital, emergency, AED, and drug-information lookup | Live | HIRA, NMC, NFA119, and MFDS public adapters where configured |
| Location and administrative area resolution | Live | JUSO, Kakao, SGIS-style location adapters where configured |
| Welfare, public jobs, business support, and procurement lookup | Live for public lookup | MOHW, MPM, MSS, MSIT, and PPS public-data surfaces where configured |
| Legal, public records, statistics, utility/public-corporation lookup | Live for public lookup | MOJ, CCOURT, FTC, REB, KCUE, KEPCO, KSD, BFC, and MOF adapters where configured |
| Traffic fine payment and welfare application submission | Mock | Shape-faithful send adapters |
| Digital OnePass, simple auth, mobile ID, certificates, MyData | Mock or Handoff | check mock adapters and scenario docs |
| Government24/Hometax final submissions | Handoff or target-state | Requires official callable channel, credential, consent, and artifacts |
The table is a current-state map, not a product promise for every subtask. A domain can be represented in a target-state scenario and still be Handoff today.
How To Read A Coverage Claim
Section titled “How To Read A Coverage Claim”A strong coverage claim has three parts: user task, state label, and evidence. “Healthcare is supported” is too broad. “Nearby public hospital lookup is Live where the configured public adapter returns evidence” is a better claim.
This wording protects the user from assuming that public lookup, personal medical records, triage, and emergency dispatch are the same capability. It also gives evaluators a concrete artifact to inspect.
What Evaluators Should Check
Section titled “What Evaluators Should Check”Evaluators should look for false promotion. A page is wrong if it describes Mock as official completion, protected workflow without consent evidence, public-data answer without a source, or target-state channels as current Live capability.
The adapter matrix, generated metadata, scenario matrix, and architecture pages should agree. If one surface says Live and another says Handoff, treat that as documentation drift until the underlying evidence is reconciled.
What Users Should Do Next
Section titled “What Users Should Do Next”Start with Live public lookup tasks, then try Mock or Handoff flows only after reading the trust pages. If you need a binding official action, continue through the official service unless UMMAYA shows live authority and receipt evidence.