Repository navigation
Qualify the selected actual deployment under Q2-D #99
Description
Acceptance Criteria
- Run the six retained load/overlap/debug/auxiliary/saturation/recovery families with predeclared windows, repetitions and thresholds against the production-intended artifact/config and real meter.
- Require accounted fit/headroom, applicable verified SDK capabilities and actual serving eligibility (#72 for native; #73/#88, #74/#89 or #75/#90 for the selected guest). Do not depend on aggregate completion of unrelated target rows.
Final Artifact And Configuration Identity
- Carry the selected unchanged release artifact, accepted operator configuration, runtime/SDK identities and actual installed profile into the qualification report and applicable Certify native configured-ceiling fit and resource ownership #72–Certify Akamai Functions hosted Spin fit #75 accounting inputs. Reuse Execute selected-path handler and config failure/recovery acceptance #100 or matching Close the remaining Cloudflare deployed-handler acceptance rows #101–Close the remaining hosted Spin deployed-handler acceptance rows #103 handler observations, but do not substitute a local configuration regression or another artifact's old measurements for the final release. This retains the final-artifact requirement transferred from Wire operator runtime configuration into Axum startup #131–Wire operator runtime configuration into hosted Spin settings #134 without reopening shared accounting (Account for runtime-owned configuration and bootstrap limits #130) or duplicating provider fit work.
No new configuration implementation or all-provider dependency is implied.
Blocking And Review Gates
- Blocked by: #52, #91.
- External blockers: Authorized selected deployment, actual meter and applicable SDK attestations.
- Conditional blockers: #52 selects one path: native #72, Fastly #73/#88, Cloudflare #74/#89 or hosted Spin #75/#90. Do not AND all paths.
Use native blocked-by/blocking links for unconditional issue relationships. Conditional target gates are not universal blockers; link only the selected applicable path after its contract is frozen.
- Configuration plumbing is already delivered through EdgeZero for all four standalone adapters; superseded Wire operator runtime configuration into Axum startup #131–Wire operator runtime configuration into hosted Spin settings #134 are not implementation prerequisites. Remaining selected-path config/isolation/failure/recovery acceptance is owned by Execute selected-path handler and config failure/recovery acceptance #100 and the applicable Close the remaining Cloudflare deployed-handler acceptance rows #101, Close the remaining Fastly deployed-handler acceptance rows #102 or Close the remaining hosted Spin deployed-handler acceptance rows #103. For an embedded path, Provide the typed in-process host bridge #51 owns host-policy/service binding and Link the bridge into an actual Trusted Server artifact #76 owns actual host ingestion/adoption; superseded Expose host-supplied runtime configuration for embedding #135 is not a separate prerequisite. Do not require all adapters or completion of Release operator-neutral binaries with runtime configuration #124 for a selected path.
Shared Acceptance Requirements
Every implementation issue ships its own unit/conformance, failure, resource and privacy tests. A later integration issue does not postpone those checks. New untrusted decoders include generated hostile-input controls; changed hot paths include repeatable measurements. Use the existing engine, host services, validated config/push path and EdgeZero handler registration. Preserve privacy, authorization, cookie integrity, HTTPS/SSRF protections, deadlines, exact sent coverage, authoritative bidder/alias attribution and bounded work/storage. Standalone and embedded behavior share policy rather than fork implementations.
No issue may claim a missing capability from metadata import, compilation, observed allocations, a signed cookie, or a different artifact's old evidence. New public/configuration behavior requires its reviewed design before execution. No workload reduction, raised ceiling or replacement budget equation is implied. Bodies and evidence must not publish credentials, identifiers, raw consent, private provider addresses or customer configuration.
Technical Ownership
Sources: roadmap sections 6 and 8 and the existing M6 contracts/runbooks.
Activity