issues Search Results · language:Edge language:Python language:JavaScript language:JavaScript language:JavaScript linked:pr
Filter by
4.5M results
Requirement: Per-channel consent enforcement — fail closed from the latest immutable record
Metadata
- ID: REQ-ENG-034
- Title: Affirmative per-channel consent required for delivery; evaluated only ...
area:engine
priority:critical
privacy
security
Requirement: Reminder actions — snooze, dismiss, mark-as-contacted
Metadata
- ID: REQ-ENG-033
- Title: User can snooze, dismiss, or mark a reminder contacted; mark-as-contacted resets the cadence ...
area:engine
priority:high
Requirement: Per-user reminder generation cap per scheduler window
Metadata
- ID: REQ-ENG-032
- Title: Scheduler caps reminders per user per window to prevent runaway generation and notification ...
area:engine
priority:high
security
Requirement: Scheduler cadence evaluation — idempotent, bounded, horizontally scalable
Metadata
- ID: REQ-ENG-031
- Title: Scheduler emits a reminder when cadence elapsed AND in-window AND consent ...
area:engine
priority:critical
Requirement: Google People contact import — least-scope, minimal fields, bounded streaming
Metadata
- ID: REQ-CON-030
- Title: Import contacts from Google People (read-only scope, name/phone/email/provider-id ...
area:contacts
priority:medium
security
Requirement: Per-user resource quotas on contacts, categories, and import batch size
Metadata
- ID: REQ-CON-029
- Title: Fail-closed per-user quotas bounding contacts, categories, and single-import ...
area:contacts
priority:medium
security
Requirement: Last-contact logging with distinct asserted vs. server record time
Metadata
- ID: REQ-CON-028
- Title: Log contact event (mark contacted) resets cadence clock; asserted and server times ...
area:contacts
priority:high
Requirement: Cadence configuration with override precedence and fail-closed quiet hours/timezone
Metadata
- ID: REQ-CON-027
- Title: Per-category and per-contact cadence, quiet hours, timezone — ...
area:contacts
priority:high
Requirement: Relationship categories — defaults, custom CRUD, fail-closed delete
Metadata
- ID: REQ-CON-026
- Title: Default + custom categories with per-category default cadence and reassignment-on-delete ...
area:contacts
priority:high
Requirement: Single-contact deletion cascade in one transaction
Metadata
- ID: REQ-CON-025
- Title: Contact deletion removes all associated data, reminders, and outreach history atomically
- Version: ...
area:contacts
priority:high
privacy

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.