Forwardable market-research kit · not a solicitation response
Research the document substrate beneath federal signing.
Use this package to ask whether exact-state, machine-readable, portable documents can improve provenance while preserving existing credentials and compatibility requirements.
Reference architecture
CAC/PIV credential → exact canonical UDR state → signature evidence → completed UDS → independent verification → amendment as a new UDR.
CAC/PIV concept
The credential remains authoritative for authentication/signing. UD supplies the document object, lifecycle and portable evidence boundary. Real credential integration is unverified.
Capability matrix
| 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. |
Security and trust
Report mathematical signature validity, credential trust, identity verification, time assurance, revocation and document integrity separately. Never collapse these into one green badge.
Privacy
Local verification and offline BrowserCarrier reading remain possible. Public forms prohibit document content, classified information, CUI, source-selection and procurement-sensitive material.
Accessibility status
Semantic UD structure is designed to support adaptable presentation. Section 508 conformance is not claimed and requires evidence-based evaluation.
Interoperability and PDF compatibility
UDR, UDS and BrowserCarrier remain primary. PDF remains a secondary compatibility copy for systems that require it. A pilot must test actual receiving systems.
Pilot model
One team, one non-sensitive document family, fourteen days, controlled credentials, explicit measures, documented limitations and a stop/continue decision.
Known limitations
- No real CAC/PIV production integration or federal PKI validation profile.
- No federal approval, ATO, FedRAMP authorization, agency endorsement or procurement eligibility.
- No verified Section 508 conformance.
- No claim of production scale, mature federal integrations or autonomous deployment.