Repository navigation
Resolve callback UID authenticity and replay requirements #57
Description
Acceptance Criteria
- Review whether an additional callback-authentication/replay contract is required for intended consumers, documenting which sources are assertions versus authenticated ownership.
- Preserve the approved M5 integrity-only boundary unless a separate contract is approved; if stronger guarantees are required, create bounded follow-up scope rather than claiming the MAC already provides them.
Blocking And Review Gates
- Blocked by: #36.
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 M9 and Global Protocol Mode, plus M5 identity trust boundaries.
Activity