Release
All required controls are structurally complete, required gates passed, no blocking gap remains and any waiver is owned, evidenced and unexpired.
Delx Release Governance
Release is a decision, not a green build.
The executable Delx standard for release, hold and block decisions across scope, evidence, risk, authority, rollback, gaps and expiring exceptions. The current reference manifest evaluates to release; it remains first-party evidence, not certification.
Decision semantics
Release, hold and block are not synonyms.
The evaluator keeps missing evidence separate from failure. It never converts an unavailable gate into pass or lets a green build stand in for the full packet.
Hold
The packet is structurally complete, but a required gate is pending or unavailable. Missing evidence stays visible and the release does not advance.
Block
A required control is missing, a gate failed, a blocking gap remains, rollback is unverified or an exception is invalid, orphaned or expired.
Required packet 01–03
Name the thing before judging it.
A release starts with identity, exact scope and excluded claims. Ambiguous ownership or an unnamed version blocks the decision before technical theater can begin.
Identity and scope
Name the release, owner, exact version, artifact boundary, decision owner and decision date.
Capabilities and excluded claims
State what the artifact enables and what passing the release gate does not establish.
Evidence and gates
Every required gate has a status and public evidence pointer; green build or transport success never stands in for the full packet.
Required packet 04–07
Risk survives the checklist.
Mitigation does not erase residual risk. Data, authority, rollback, unresolved gaps and exceptions remain explicit in both human and machine output.
Risk, mitigation and residual risk
Each material risk retains a mitigation and the risk that remains after mitigation.
Data and authority boundaries
Name the data that enters or stays out, plus the actions the release can never authorize by itself.
Rollback and stop conditions
Name a verified rollback target, triggers, procedure and evidence before release.
Unresolved gaps and exceptions
Classify open gaps as blocking or non-blocking. A waiver needs an owner, reason, accepted risk, evidence, expiry and a named waived gate.
Reference manifest
One real release, evaluated in public.
The first manifest covers the live research-status release already promoted to production. It names the exact candidate, deployment, decision owner, boundaries and gaps rather than presenting a blank template.
Delx live research artifact status — release
Human, JSON and Markdown first-party reachability readbacks for the eight research artifacts present in catalog version 1.2 at release time. Declared decision: release; evaluated decision: release; declaration matches: true.
Inspect the immutable release →Exact identity
Source commit 7f63dbb2f3e934ddc7f6a4068ae0e637bcf414c2; deployment dpl_GVEREaWtYxeQFpZVRxNxMzo8ot7m; owner Delx Institutional; decision owner Founder / David Batista.
Inspect the live artifact →No borrowed assurance
External review: false. Independent validation: false. Evidence class: first_party_release_receipt.
Read the claim method →Six required gates
The same artifact survives local, candidate and production readback.
Each gate records its own status and evidence surface. The candidate was built once, tested at its immutable URL and promoted without a rebuild.
Lint, tests and production build — passed
npm run verify passed lint, 58/58 tests and the Next.js production build.
Inspect the evidence surface →Immutable candidate machine contract — passed
The exact candidate passed 252/252 contract surfaces.
Inspect the evidence surface →Candidate desktop and mobile review — passed
The candidate rendered eight artifact cards and four FAQs without overflow, clipping or attributable browser warnings/errors at 1280x720 and 390x844.
Inspect the evidence surface →Exact deployment promotion — passed
delx.ai resolved to deployment dpl_GVEREaWtYxeQFpZVRxNxMzo8ot7m, target production, status Ready.
Inspect the evidence surface →Production machine contract — passed
The promoted production deployment passed 252/252 contract surfaces.
Inspect the evidence surface →Production desktop and mobile review — passed
Production retained the canonical URL, eight artifact cards, four FAQs, zero horizontal overflow and no attributable browser warnings/errors.
Inspect the evidence surface →Risk register
Passing controls do not delete residual risk.
The release packet preserves the ways this surface can still mislead or fail after its gates pass.
A green HTTP read can be mistaken for scientific validity, permission, adoption or correct output.
Mitigation: The human, JSON and Markdown surfaces keep the claim boundary beside every read and publish explicit state semantics. Residual risk: A downstream consumer can still ignore the published limitation.
The same organization owns the probe and most sources, so correlated failure or bias can remain invisible.
Mitigation: Every surface identifies the monitor as first-party and independent monitoring as unavailable. Residual risk: The readback cannot establish independent availability or assurance.
External fetches can slow the page or end without a conclusive HTTP response.
Mitigation: Each probe has a 6,000 ms abort bound, no-store semantics and an explicit unavailable state. Residual risk: A transient network path can still degrade or make a single read unavailable.
Rollback and open state
Know how to stop before calling it ready.
The previous deployment remains the exact rollback target. Non-blocking gaps keep owners and readback dates; exceptions are an explicit empty list, not invisible discretion.
Rollback target — dpl_7TkipcVKaXVfVuAv6UdjHUUu3kpR
Verified: true. Triggers: The status schema or no-store contract regresses. Unavailable and failed are silently collapsed. The promoted deployment no longer matches the verified candidate. Procedure: Promote the preceding Ready deployment without rebuilding it. Run the complete machine-contract gate against https://delx.ai. Verify the restored deployment identity and public research routes.
Inspect the rollback artifact →independent-monitoring — non_blocking
No independent monitor or external availability history exists for this surface. State: unavailable. Owner: Delx Security. Next readback: 2026-09-02.
longitudinal-uptime — non_blocking
The release publishes point-in-time probes, not a longitudinal uptime series. State: unavailable. Owner: Delx Institutional. Next readback: 2026-09-02.
external-use — non_blocking
No reconciled evidence of external use of the status contract has matured. State: unavailable. Owner: Delx Research. Next readback: 2026-09-02.
Exceptions — 0
No exception was declared for this release. The standard requires every future waiver to name its gate, owner, reason, accepted risk, evidence and expiry; an orphaned or expired waiver blocks release.
Inspect the exception contract →Direct answers
Frequently asked questions.
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
Does a green build authorize release?
No. A build is one gate. The release packet also needs exact scope, capabilities, excluded claims, public evidence, risk and residual risk, data and authority boundaries, verified rollback, unresolved gaps and accountable exceptions.
What happens when required evidence is unavailable?
The evaluator returns hold. Unavailable is not pass, failure or zero. The release stays visible as waiting for evidence rather than advancing on an inferred healthy default.
Can an exception make a failed gate pass?
No. A failed gate blocks. A deliberately waived gate is a separate state and needs a named, evidenced and unexpired exception with accepted risk; invalid, expired or orphaned exceptions also block.
Is this independent assurance?
No. This is a first-party governance standard and executable validator. Independent assessment, certification or external review must be named only when it actually exists.
Why publish a real manifest instead of only a template?
A blank template proves formatting. The reference manifest shows the standard applied to one exact release with its deployment, gates, risks, rollback, gaps and decision.