A2A approval command center
This dashboard keeps the IRS software testing work honest: no fake approvals, no browser secrets, and no claim that ATS XML is final until the current IRS schema package is received and mapped.
Current readiness
13%Ready
1Blocked
3Total
8Readiness gates
These buttons change only local dashboard status. They do not submit to the IRS and do not store secrets.
Submit and track the IRIS application for the Software Developer role before production transmission is possible.
Evidence: Application status, assigned TCC, and application signature are kept outside the public browser UI.
Owner: Business owner
Register UStaxefile as the software package and keep the package website pointed at the IRS reviewer page.
Evidence: Software package name, package type, public review URL, supported forms, and production lock status.
Owner: UStaxefile ops
Request and record the IRIS API Client ID after IRS authorization makes it available.
Evidence: Only masked identifier metadata belongs in this tracker; the actual client secret must stay server-side.
Owner: Authorized responsible official
Receive the IRS schema package, record its version/date, and map the ATS XML generator against it.
Evidence: Schema version, package date, checksum, and supported form mappings.
Owner: Engineering
Store IRIS credential metadata in the protected Worker environment, never in the static Next.js client.
Evidence: Credential fingerprint/KID, environment name, rotation date, and audit event ID.
Owner: Engineering/security
Generate IRS ATS test files only after the current schema package is mapped and the package is marked ready.
Evidence: Transmission ID, submission count, record count, generated package timestamp, and checksum.
Owner: Engineering
Record IRS acknowledgement IDs, status codes, received timestamps, and follow-up actions.
Evidence: Accepted/rejected acknowledgement records and related audit log IDs.
Owner: UStaxefile ops
Prepare a clean packet showing reviewer URL, software package data, ATS evidence, and secure contact details.
Evidence: Packet checklist, non-secret contacts, package status, and review notes.
Owner: Business owner
Reviewer website URL
Requiredhttps://ustaxefile.com/irs-software-test
Software product name
RequiredUStaxefile
Package type
RequiredOnline Package using IRIS A2A after approval
Supported forms shown in app
Required1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, 1098, 5498
Production lock explanation
RequiredLive filing remains disabled until IRS approval, ATS acceptance, credentials, and internal authorization are complete.
IRS schema package version
RequiredPending receipt from IRS; do not submit final ATS XML until mapped to current schema and business rules.
Credential handling note
RequiredActual API credentials are stored only in protected Cloudflare Worker secrets, not in the static browser app.
Protected backend work
/software-packages
Create or update the internal UStaxefile software package record.
Bearer token required; do not call from client-side JavaScript.
/iris/schema-packages
Register schema package metadata after IRS provides the current schema package.
No schema ZIPs or secrets in public storage; metadata and checksums only.
/a2a/credentials
Record non-secret credential metadata and audit the vaulting event.
Actual credential material must be Cloudflare Worker secrets or an approved secret manager.
/ats/readiness
Check whether package, schema, and credential prerequisites are ready.
Server-to-server only until real auth/session protection exists.
/ats/test-packages
Generate ATS package scaffolds after prerequisites are present.
Protected and rate limited; output must not contain real taxpayer data.
/ats/test-packages/:transmissionId/acknowledgements
Record IRS ATS acknowledgement metadata and status.
Sanitized audit logs only; no raw secrets or full taxpayer identifiers.
The dashboard intentionally avoids API tokens, API Client secrets, certificate material, TINs, SSNs, EINs, or raw IRS payloads.
Actual IRS/A2A actions must run through the protected Cloudflare Worker or another server-side service with authorization and audit logs.
Final ATS XML should not be represented as IRS-valid until the current IRS schema package and business rules are received and mapped.