Repository navigation
Description
Acceptance Criteria
- Close per-call cache, hostname, fallback/quit, work and stack obligations reachable from the shipped closure; extend nested literal-owner reports only where that closure requires them.
- Deliver shared V/admission derivations and independent boundary controls; actual target bindings/execution are owned by #72 through #75. Do not substitute benchmarks for worst-case bounds or change the serving engine without review.
Blocking And Review Gates
- Blocked by: #33.
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.
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: M7-R0 design/plan, ISSUES.md resource rows and schema qualification record.
Approved Integration Contract
PR #152 merged the specification and delivery plan at 9b83deaa680ad8e867169db3b4ebb195b8a1b33c. Their shared requirements apply: whole-catalog reports with verified skipped: not_implemented rows, positive qualification of every implemented identity/alias on all four adapters, existing build discovery and the qualified common native_only retirement. The first Trusted Server host remains Fastly display; Trusted Server #1505 coordinates host-owned work. The planning merge is not implementation or qualification evidence and changes no workload limit, resource ceiling or configuration mechanism.
Discovery And Execution Scope
- Qualify the discovery-selected implemented validator closure, including every declared alias, without retaining cohort-selected schema initialization/admission or a replacement target bidder list.
- Preserve under/at/over input/work/cache/stack boundaries, original deadlines, bid-local error handling and exact release. Bind shared derivations to each actual adapter implementation through Certify native configured-ceiling fit and resource ownership #72-Certify Akamai Functions hosted Spin fit #75 and Enable qualified Fastly guest schema and registry serving #88-Enable qualified hosted Spin guest schema and registry serving #90; native observations are not guest proof.
Source Contracts
- Approved roadmap
- Product vision
- Issue ledger and qualification limitations
- Schema qualification record
Resource Proof Responsibilities
Responsible technical role: schema/compiler maintainers.
Next verification action: complete shared V evaluation-work, mutable cache/scratch and stack proofs for the discovery-selected closure, including hostname/UUID callbacks and simultaneous cache owners. Preserve existing engine and limits; #72 through #75 own actual target binding and execution rather than treating native measurements as guest proof.
Source: approved shared resource ownership contract, delivered for review in #162. This records responsibility and the next verification action, not completed proof, target qualification, changed workload limits or permission to close this issue.
Activity