Skip to main content

Documentation Changelog

Phase 6B — Full localization and linguistic QA

  • Replaced all 134 localized summary candidates with full semantic translations in Spanish and Brazilian Portuguese.
  • Preserved heading hierarchy, internal links, images, code fences, tables, public-review notices, and controlled UbID terminology.
  • Added structural translation-parity QA and localization metadata validation.
  • Distinguished model-assisted linguistic review from formal human linguistic approval.
  • Added a bilingual terminology guide, localization QA register, and updated publication-readiness controls.
  • Kept all canonical documents at foundation, all specialist approvals pending where required, and public indexing blocked until formal authorization.

Phase 6A — Localization candidates and approval controls

  • Added Spanish and Portuguese localization candidates for all 67 canonical documents.
  • Distinguished present files, candidates, complete translations, and formal linguistic approvals.
  • Added editorial, localization, and specialist-approval registers.
  • Kept all documents at foundation and kept public indexing blocked.

Phase 5 — Validation, accessibility, localization, and publication readiness

  • Added reproducible content QA for terminology, headings, descriptions, alternative text, link labels, exposure, and high-risk public claims.
  • Added localization QA for homepage interface catalogs and document translation coverage.
  • Added generated publication-readiness reports and a strict release gate.
  • Added explicit preview and public modes for robots.txt and environment-controlled Docusaurus indexing.
  • Added specialist-review, accessibility, localization, and release-governance documentation.
  • Added accessible localized labels for the homepage principles and trust-fabric visualization.
  • Hardened Nginx response headers and changed CI deployment to an explicit manual preview action.
  • Kept all 67 documents at foundation and kept public indexing blocked because editorial approvals and Spanish/Portuguese document translations are still pending.

Phase 4 — Visual design, diagrams, and editorial experience

  • Rebuilt the homepage around a clear institutional narrative, audience pathways, documentation domains, the trust lifecycle, and design principles.
  • Added a public UbID Trust Fabric visual language with a vector logo, favicon, social card, icons, and consistent color tokens.
  • Added nine public-safe SVG diagrams covering platform layers, roles, selective disclosure, lifecycle, products, recovery, standards, integration, and governance.
  • Integrated the diagrams into the principal conceptual pages.
  • Refined navbar, sidebar, table of contents, document typography, tables, admonitions, code blocks, pagination, and footer.
  • Added responsive layouts, dark mode refinement, visible keyboard focus, and reduced-motion behavior.
  • Expanded Spanish and Portuguese interface catalogs for the homepage.
  • Kept public indexing disabled and excluded production topology, customer configurations, secrets, recovery structure, thresholds, dashboards, incidents, and runbooks.

Phase 3G — Governance, regulatory alignment, and resources

  • Completed the public governance model for accountability, decision rights, policy lifecycle, implementation phases, and evidence packages.
  • Expanded regulatory alignment without presenting UbID as an automatic compliance, certification, or legal-recognition product.
  • Added versioned jurisdiction-profile structure and a concise baseline for the European Union, United Kingdom, Canada, United States, Latin America, and Asia-Pacific jurisdictions in the institutional study.
  • Documented biometric necessity, alternatives, isolation, retention, human review, accessibility, vendor governance, and decision boundaries.
  • Distinguished account closure, local deletion, credential status, biometric deletion, verifier retention, and privacy-right workflows.
  • Added controlled assurance, assessment, certification, registration, and public-claim terminology.
  • Expanded capability, editorial, architecture-source, and exposure status governance.
  • Completed the public glossary, FAQ, and primary-reference catalog.
  • Kept legal opinions, customer policies, exact retention periods, biometric thresholds, regulator submissions, audit findings, certifications, and operational procedures outside the public portal.

Phase 3F — Build and Partner Integration

  • Expanded the public integration model from endpoint-oriented guidance to role, policy, lifecycle, and evidence contracts.
  • Completed issuer, verifier, and wallet/holder integration guidance.
  • Added trust-policy architecture, metadata discovery, and controlled partner onboarding.
  • Added readiness checklists, negative-test expectations, failure behavior, and public/partner documentation boundaries.
  • Kept customer schemas, production metadata, credentials, trust lists, key operations, and operational procedures outside the public portal.

Phase 3E — Standards and interoperability

  • Completed the public standards section for DIDs, verifiable credentials, SD-JWT, OpenID4VC, WebAuthn, OpenID Connect, OAuth, DIDComm, and MCP.
  • Separated specification maturity from UbID architecture alignment, implementation status, production availability, and independently assessed conformance.
  • Clarified that DID resolution is not trust, signature validity is not acceptance, authentication is not authorization, and protocol compatibility is not semantic or policy compatibility.
  • Distinguished the final SD-JWT mechanism from the evolving SD-JWT VC credential profile.
  • Documented OpenID4VCI and OpenID4VP as preferred interoperability contracts while requiring deployment-specific profile and feature declarations.
  • Defined DIDComm messaging, mediation, and pickup boundaries without exposing routing or recovery topology.
  • Applied the prepare–validate–approve–execute–evidence model to MCP and trusted agents.
  • Added version pinning, profile governance, conformance, privacy, and migration requirements across the standards portfolio.

Phase 3D — Trust, privacy, and security

  • Completed the public trust model across privacy, minimisation, defense in depth, proofing, authentication, verification, recovery, cryptographic protection, blockchain, post-quantum readiness, and observability.
  • Distinguished proofing, authentication, credential verification, authorization, and final institutional decision.
  • Defined proportional disclosure, scoped identifiers, minimised evidence receipts, lifecycle-specific retention, and privacy-preserving operational evidence.
  • Documented guarded recovery as a staged and distributed security protocol without publishing release structure or operational ceremonies.
  • Clarified the UbID blockchain position: public cryptographic linkage with private keys, credentials, biometrics, recovery material, and presentation history kept off-chain.
  • Described post-quantum readiness as a progressive, hybrid, format-aware migration program rather than a universal production claim.
  • Classified sensitive trust pages as public-reviewed and excluded thresholds, topology, secrets, fraud rules, private policies, dashboards, incidents, and runbooks.

Phase 3C — Solutions and use cases

  • Completed the public solution pages for education, government, financial services, healthcare, enterprise access, professional certification, document credentials, and trusted digital agents.
  • Applied one consistent trust pattern across sectors: purpose, minimum evidence, assurance, holder-controlled presentation, policy-based verification, and institutional decision.
  • Clarified sector boundaries so that credential validity is not presented as automatic admission, licensing, healthcare access, financial approval, enterprise authorization, or public-service eligibility.
  • Added explicit privacy, lifecycle, human-review, accessibility, and institutional-accountability controls.
  • Kept financial-services, healthcare, and trusted-agent pages under public-reviewed exposure because their claims require additional legal, privacy, security, and sector review.
  • Excluded customer rules, source records, clinical data, financial controls, fraud thresholds, private registries, protected endpoints, and privileged agent action paths.

Phase 3B — UbID product portfolio

  • Completed the ten public product pages across identity, credentials, holder control, recovery, interoperability, security, operations, and AI assistance.
  • Defined the responsibility, lifecycle role, trust boundary, related products, and public documentation limit for each product.
  • Clarified that product names identify domains and do not imply universal deployment or commercial availability.
  • Preserved separation between proofing, authentication, credential trust, authorization, cryptographic operations, observability, and AI assistance.
  • Excluded customer configuration, operational endpoints, private schemas, key material, recovery parameters, anti-abuse rules, and internal topology.

Phase 3A — Foundational narrative

  • Expanded the public introduction to UbID and its documentation boundary.
  • Completed the Learn section covering the trust model, participants, digital identity, credentials, selective disclosure, credential lifecycle, and the end-to-end trust lifecycle.
  • Expanded the public product portfolio overview and clarified product boundaries and availability terminology.
  • Preserved non-technical language and excluded sensitive implementation details.

Phase 2 — Editorial architecture

  • Established the definitive public information architecture.
  • Adopted the UbID Trust Fabric product portfolio and public role terminology.
  • Defined capability, editorial, and exposure classifications.
  • Separated public documentation from partner and internal material.
  • Reorganized navigation into Learn, Products, Solutions, Trust, Standards, Build, Governance, and Resources.
  • Retained public indexing restrictions while the content remains under review.

Phase 1 — Technical modernization

  • Migrated the portal to Docusaurus 3.
  • Prepared English, Spanish, and Portuguese builds.
  • Added static production build, Docker, validation, and publication controls.

Phase 6C — Controlled approval workflow

  • Added attributable publication, specialist, and linguistic approval records.
  • Bound approvals to semantic SHA-256 values and reviewed commits.
  • Added stale-approval detection and discipline-based specialist gates.
  • Added release preflight, manifest-bound release authorization, and guarded public-mode activation.
  • No approvals are granted automatically by this release.