Repository navigation
Description
Acceptance Criteria
- Select exact additional identities and required branches from demonstrated publisher demand and pilot findings, recording endpoints, settings, sync, schemas, resource needs and acceptance producers.
- Review a nonempty finite queue and generate actual per-family sub-issues from it. Record later-feature-dependent identities under M20; relisting the shipped 14 is not expansion.
Blocking And Review Gates
- Blocked by: #108.
- Review gates: Approve an exact finite wave from publisher demand and pilot findings before generating per-family implementation Tasks.
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: roadmap section 3 and the M7 bidder ownership/import/onboarding contracts.
Activity