CIO / CTO
Can the document remain portable, machine-readable and independently verifiable?
Open the one-page brief →Federal Bug Light 2 · research and controlled evaluation
Keep the credential. Upgrade the document.
CAC/PIV is the identity and signing credential. Universal Document is a proposed better document substrate underneath it—one that can preserve revision lineage, bind a signature to an exact state, become a sealed UDS, and carry portable evidence.
Do not replace CAC. Give CAC a better document to sign.
What works now, and what remains proposed?
| Capability | Status | Boundary |
|---|---|---|
| CAC/PIV credential use | PROPOSED / UNVERIFIED | The profile preserves CAC/PIV as the credential. No real credential integration has been production-tested. |
| Exact-state signature binding | CONTROLLED DEMO | A local test key signs the hash of one exact controlled document state; mutation fails verification. |
| UDR revision lineage | CURRENT UD CAPABILITY | A living UDR can preserve version and parent lineage before signature. |
| UDS finality and verification | CURRENT UD CAPABILITY | A completed UDS is tamper-evident and locally verifiable using the existing canonical verifier. |
| Signing evidence | CURRENT FOUNDER-PILOT CAPABILITY | UD Sign can carry signing evidence; federal credential evidence remains a proposed profile. |
| PDF compatibility | CURRENT UD CAPABILITY | Print/Save as PDF remains available as a secondary compatibility copy. |
| Federal approval / ATO / FedRAMP | NOT ESTABLISHED | No approval, ATO, FedRAMP authorization or agency endorsement is claimed. |
| Section 508 conformance | NOT VERIFIED | Accessibility is a required evaluation track, not a current conformance claim. |
Start with your responsibility
CISO / Digital Identity
What is authenticated, signed, verified and still unverified?
Open the one-page brief →General Counsel
Can the signed record preserve the exact agreement and its lineage?
Open the one-page brief →Records Management
Can the record carry history, finality and supersession state?
Open the one-page brief →Program / Operations
Can one document family be tested without replacing the current workflow?
Open the one-page brief →Acquisition
Can requirements remain vendor-neutral and outcome-based?
Open the one-page brief →Accessibility
Does structured content improve access without unsupported conformance claims?
Open the one-page brief →Technical and evaluation paths
Federal claims boundary
No CAC/PIV production integration, agency interest, government adoption, federal approval, procurement eligibility, FedRAMP authorization, ATO or Section 508 conformance is claimed.