V6.1 VALIDATION STATUS · CONTROLLED LEDGER PROJECTION
See what is released to public production, what is qualified, and what still lacks private or external authority.
This page joins the exact public-production release receipt to the repository's controlled v6.1 conformance ledger. It keeps public deployment, source construction, migration qualification, human acceptance, and external authority separate instead of compressing them into one completion percentage.
Software checks, physical bench qualification, and authorized release answer different questions. Passing software tests does not validate a connection setup or approve a calibration method.
REVIEWED PUBLIC-PRODUCTION RELEASE RECORD
Recorded qualification evidence for a named historical source and deployment.
Historical qualification evidence is not automatically valid for a later deployment.
Current build versus reviewed record: Historical receipt — production differs
Reviewed on 2026-10-06 for a different source or deployment. Not evidence of qualification for this build.
Source in this build: 46230ccf5a9207139d30941235a2a6f95e47b1b8. Reviewed source: 371a5ced280e67b264053500002508663f02d154.
Release statePUBLIC_PRODUCTION_VERIFIED · reviewed 2026-10-06
Canonical URLhttps://metraxiom.com
Deployment
dpl_8nswi5JdBSb2n4JBCkEcQ4PGQLo3Source commit
371a5ced280e67b264053500002508663f02d154Validation338 test files · 2,552 unit tests · lint, types, build and dependency audit passed
Hosted qualification63/63 strict gates · 58 staged and 58 production browser tests · zero retries · Chromium, Firefox and WebKit
Released scopePublic Builder with browser-local worksheets; Public uncontrolled PDF export; Context Twin context from NOAA/NWS and NOAA/SWPC
Held scopeAuthoritative measurement release; Certificate issuance and signing; Private workspace; Billing and commercial enrollment; Public search indexing; Live Acquisition; Public AI and MCP
Database / branch boundaryNo production database changes and no main-branch merge were performed by this public release.
Candidate distinction
A later source change is not this release until its exact commit completes candidate qualification, protected deployment, post-deployment verification, and explicit promotion.
Current authority boundary
Repository source head
0156_dueproof_contest_correction_ledger.sqlIncremental qualification head
0155_calculation_independent_review_authority.sqlFresh production-derived replay head
0144_iso17025_readiness_fk_index_hardening.sqlProduction database head
0089_procedure_authority_expectation_lock.sqlCurrent clean-replay tail
0145–0155 · 11 migrationsSource-only unqualified tail
0156–0156 · 1 migration · source_controlled_not_executedQualification status: repository source is contiguous through migration 0156. Purpose-specific/incremental qualification is retained through 0155, while the latest fresh production-derived full-chain replay stops at 0144. Migration 0156 remains source-only and unexecuted with no qualification or replay credit. A fresh exact ordered Production-derived replay of 0090–0156 remains required before production promotion can be considered. Existing incremental evidence receives no final-replay credit.
Production universal authority: false. Production certificate issuance: false. Production execution and post-deploy acceptance remain separate gates.
The controlled calculation-verification ledger records 14,224 deterministic evaluations in its current profile. Numerical verification does not create laboratory competence, ISO/IEC 17025 accreditation, issuer authority, or physical measurement truth.
WORLD-CLASS RELEASE GATES
16 gates. No single green build means “done.”
Each row below comes from the same controlled conformance registry used by repository checks. Remaining evidence is shown rather than hidden.
UG-01 · Architecture
SatisfiedThe current controlled ledger records this gate as satisfied. Future changes can still reopen it.
UG-02 · Metrology
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: The canonical/public calculation engine is numerically verified and the universal pressure path has source/runtime evidence, but first reference-quality DC electrical, temperature and dimensional controlled profiles still require competent SME review, controlled procedures/specifications, uncertainty budgets and domain golden fixtures (OPEN-05).
UG-03 · Point grid
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Universal-grid keyboard traversal and paste/import plan-revision behavior now have retained browser acceptance on the synthetic controlled-workspace preview, and the canonical 10,000-point grid/model proof remains machine-gated. Full promoted controlled 10,000-point persistence/API/end-to-end operability and human technician acceptance remain unearned.
UG-04 · Environment
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Typed A-F environment authority semantics, the NOAA/NWS observation adapter, freshness/missingness handling and fail-closed non-escalation tests exist in source. A provider-neutral global portfolio now separates station observation (Class D, context-only), forecast/model context (Class E, context-only) and geocoding (location-resolution-only); all non-U.S. providers remain candidate/default-off. Deployed provider credentials, outage/privacy acceptance, customer location-retention policy, global fixture validation and production execution evidence remain incomplete.
UG-05 · As-found/as-left
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Separate session/evidence identities, retest lineage and no-rewrite semantics exist in source and runtime harnesses; full controlled intervention/restabilize/as-left human workflow acceptance is still unretained and production universal writes remain unpromoted.
UG-06 · References
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Capability/readiness snapshots and reliance structures exist, and U4C recall lifecycle was exercised in isolation; reference invalidation-to-reliance traversal across a promoted production package population is not yet acceptance-proven.
UG-07 · Certificate
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: ReportModel, deterministic PDF rendering, artifact schemas, issue allocation and isolated hosted issuance/lifecycle evidence exist. The public fixed-layout renderer now has canonical single-page proof plus deterministic 512-result annex pagination proof. Customer issuer/legal authority, production migration promotion, certificate feature-gate activation and exact promoted post-deploy proof remain unearned.
UG-08 · Integrity mark
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Package/artifact hash separation, lifecycle-aware verification receipt projection and opaque-token substrate exist, but the cryptographic signing/KMS/timestamp profile (OPEN-04), deployed public-verifier abuse/rate-limit/timing evidence and external trust-distribution review remain open.
UG-09 · Authority
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Technical completion, review, release and issuance are separate and fixture-backed issuer/reviewer/idempotency paths passed in isolation; customer legal authority, production role/MFA policy acceptance and exact promoted separation-of-duty evidence remain gated.
UG-10 · DCC
GatedThe capability is deliberately blocked from an authoritative production claim until named release evidence exists.
Remaining: A PTB DCC v3.3.0 candidate downstream projection and fail-closed unmapped-semantics checks exist. Official schema/vocabulary/unit conformance, known authoritative fixtures, round-trip semantic validation, signature profile and any production DCC claim remain unvalidated and unauthorized.
UG-11 · Security/privacy
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Universal RLS/direct-DML denial, private issuance boundaries and isolated U4C transaction negatives exist; deployed verifier enumeration/abuse/timing/logging, signing-key controls and external independent assurance (OPEN-09) remain incomplete.
UG-12 · Accessibility
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Public mobile task cards, sticky session context, visible keyboard focus, keyboard grid traversal, textual lineage alternatives and semantic HTML output exist in source acceptance. A PDF 2.0 conformance lane now identifies PDF/A-4 and PDF/UA-2 as candidate archive/accessibility targets, but the current PDF is not claimed conformant. Retained exact-byte validator evidence, VoiceOver/screen-reader execution and actual 200-400% zoom acceptance remain incomplete.
UG-13 · Performance
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: The selected renderer has 1,000- and 10,000-result benchmark evidence, the public fixed-layout PDF now proves deterministic 512-result annex pagination, and the universal 10,000-point grid/model test is machine-gated. Promoted private large-job persistence/API p95, end-to-end issuance/verifier load and production memory budgets remain unproven.
UG-14 · Claim truth
PartialMaterial implementation or evidence exists, but one or more required acceptance conditions remain unresolved.
Remaining: Core v6/public-builder/calculation/DCC boundaries are registered and enforced, but claim truth remains a continuing release obligation and must be re-audited as every gated capability changes state.
UG-15 · Production
GatedThe capability is deliberately blocked from an authoritative production claim until named release evidence exists.
Remaining: Repository source reaches migration 156, while the retained fresh Production-derived ordered replay stops at migration 144. Migrations 145–155 have incremental/purpose-specific qualification but no final full-chain replay credit. Migration 156 remains source-only and unexecuted with no qualification or replay credit. Production remains at migration 89; production promotion, controlled-write acceptance, certificate/verifier activation, smoke testing, monitoring, rollback validation, and post-deploy acceptance remain open.
UG-16 · Human acceptance
OpenThe remaining decision or acceptance depends on real external evidence, authority or human action.
Remaining: Representative technician, reviewer, laboratory manager and first-time buyer acceptance evidence has not been formally retained. Architecture or automated testing cannot substitute for this gate.
WHAT “COMPLETE” MEANS HERE
Construction completion and production authority are deliberately different states.
A capability may be extensively implemented, simulated and build-gated while remaining Partial, Gated or Open because the remaining proof requires a promoted production environment, a competent metrology SME, a real technician/reviewer, assistive-technology execution, independent security work, customer legal authority, or a named cryptographic/DCC profile.
Not claimed by this page
Accreditation · ISO/IEC 17025 conformance · Part 11 validation · DCC conformance · universal certificate-issuance authority · independent security assurance · reference-quality validation of every discipline.