Fields verified Proven correct by the verifier
Wrong mappingsRejected after testing
Waiting for a personHuman review required
Typical cost per fieldMedian final map + verify
Recorded API costThis run, incl. re-runs during fixes
How the system fits together
The Dot maps each field once per ProSeries version. Every client return then reuses the verified map.
Once per ProSeries version
The Dot finds the fieldLocates the input and records how to reach it by keyboard
→
A separate verifier tests itTypes test values and checks the result on the return
→
Verified mapPlain code decides the status, never a model
Every client return
ExtractRead W-2s and 1099s into values
→
Look up the mapWhere each value goes
→
EnterFollow the known keystrokes
→
CheckConfirm each value landed
Highlighted steps are what this pilot builds. Extraction exists; entry is the next module.
Progress by form
The 50 benchmark fields, grouped by the tax form they come from.
VerifiedHuman review
RejectedMapped, not verified
Not started
What "verified" means
A field is verified only when every check that applies to it passes. One failed check sends it to a person.
All 50 fields
Select a row to see where the field lives in ProSeries and how to reach it.