The situation
The archive already stores an audited contact_frequency interval and derives a person's cadence from their last contact. Finding everyone due to reach out still means opening people one at a time.
What works today, and why it is not enough
An interval can be edited on an individual profile, and the contact-state read derives its due date. The Directory cannot filter or order the roster by that cadence, so it cannot serve as a reach-out queue. Common A/B/C/D intervals also have to be entered as raw days.
Ask
Add shared Sivers-style defaults of 21/60/180/365 days, across-people cadence queries through the API, CLI and MCP, and a Directory view with coverage and profile, brief and draft actions. Keep custom day intervals and the existing audited attribute writer.
Open Loops and Signal tier integration is follow-up work. Preserve both loop directions and source freshness, and make tier-suggested lists a reviewed queue rather than automatic assignments.
Activity
0No activity yet.