Readable explanation for customers, reviewers, procurement teams and evaluators.
ĐANG TẢI DỮ LIỆU
Đang chuẩn bị nội dung.
Vui lòng chờ trong giây lát. Hệ thống chưa ghi nhận thao tác này là hoàn tất cho đến khi trang được tải đầy đủ.ĐANG TẢI DỮ LIỆU
PUBLIC ASSURANCE RECORD · HUMAN-READABLE VIEW
This page explains the same public assurance contract exposed to machines by the JSON API, without requiring a reader to inspect raw structured data.
Readable explanation for customers, reviewers, procurement teams and evaluators.
Structured JSON remains the machine-readable authority for integrations and automated checks.
Certification, registration, approval and awards require separately verifiable external evidence.
01 · RELEASE CONTRACT
Private engineering and provenance authority
Public binary distribution boundary
Default claim policy
02 · QUALIFICATION
Product identity, owner, source revision, build identity and immutable evidence links.
Market need and product requirements trace to implementation and tests.
Architecture, trust boundaries, data flow and threat model are reviewable.
Type, unit, integration, interaction and production-build evidence exists.
Quality characteristics, acceptance thresholds and regressions are measured.
Secure-development, dependency, vulnerability, provenance and incident controls are evidenced.
Data inventory, purpose, retention, consent, export and deletion boundaries are documented.
AI risk, impact, intended use, limitations, evaluations and human oversight when applicable.
Keyboard, focus, responsive, reduced-motion and accessibility requirements are verified.
Applicable jurisdiction obligations are classified and evidence-linked.
Authorship, ownership, dependencies, third-party rights and registration readiness are traceable.
Price, tax, billing, refund, cancellation and consumer disclosures are defined when sold.
Platform packaging, signing, store metadata and compatibility requirements are satisfied or explicitly pending.
Observability, backup, restore, incident, continuity and rollback evidence exists.
Support, warranty, updates, migration, repair and end-of-life duties are defined.
Claims link to versioned, timestamped, digest-bound evidence.
External review is required for claims that cannot be self-attested.
The exact accepted revision is the revision actually released.
03 · ASSURANCE LEVELS
Design references a standard or requirement; no conformity claim.
D’AUBE has internal test or review evidence.
Required evidence for the declared internal scope is present.
A separate qualified reviewer has assessed the declared scope.
A recognized conformity-assessment route has been completed for the stated scope.
Only shown when a valid certificate or accreditation record exists.
Only shown when a competent authority has registered or approved the item.
Only shown with a verifiable external award, recognition or citation.
04 · CARE & CONTINUITY
Installation, compatibility, migration, account setup and guided first value.
Knowledge base, diagnostics, case tracking, escalation and human support when required.
Feature, compatibility and security update policy with release notes and rollback boundaries.
Warranty scope, diagnosis, repair/replace, service history and spare-part policy for hardware.
Backup, restore, export, transfer, deletion and safe account exit.
Advisories, revoked builds, emergency patching, incident communication and recovery.
Support windows, deprecation, migration, end-of-life and archival policy.
Usefulness, reliability, support outcomes and post-market signals feed product improvement.
Cancellation, export, ownership transfer and account deletion without dark patterns.
Right to enter. Right to operate safely. Right to receive support. Right to migrate. Right to leave.
05 · INTERNATIONAL REFERENCE MAP
QMS architecture, controlled processes, CAPA and continual improvement.
Innovation-management system architecture and evidence lifecycle.
Software lifecycle processes from concept through retirement.
Requirements engineering and traceability.
Product quality characteristics and evaluation targets.
Information-security management and cybersecurity outcomes.
Secure SDLC, mobile verification and application-security testing.
Privacy information management and accountability.
AI management, accountability and responsible lifecycle controls.
AI risk and impact assessment with evidence-based evaluation.
Service design, transition, delivery, support and improvement.
BIA, recovery, continuity, drills and recovery objectives.
Accessible web/ICT interaction and procurement evidence.
Human-centred product and interaction design lifecycle.
Measurement-system credibility, repeatability and traceability.
External accredited testing when independent laboratory evidence is required.
Compliance obligation registry, controls and evidence.
Environmental-management architecture when scope warrants it.
Learning-service governance; does not by itself create accredited academic credit.
SBOM, VEX, build provenance and software supply-chain trust.
Cardholder-data controls; preferred design minimizes PCI scope.
06 · TWO-VIEW CONTRACT