START HERE

GCD-OHR-031 evaluates supplied notification facts; it does not authenticate, store consent, verify destinations, send messages, or persist receipts.

1. Read the README boundaries.
2. Complete Sections A–G.
3. Run all 18 tests and the example.
4. Define bounded channel, freshness, cooldown, cap, and quiet-hour policy.
5. Integrate behind server authentication, tenant isolation, consent, and verified destinations.
6. Reserve durable receipts and record provider outcomes atomically.
7. Use timers only for cancellable deployment checks, never permission to send.
8. Publish only after every verification gate passes.

Final step — Publish your changes. When your build is ready, use the Floot Update/Publish control to push the latest version live. Until you publish, visitors may still see the previous version.