CLAIR
03Current LedgerCurrent-first horizontal bands + temporal spine
Clair product concept — not current implementation.Compare all five
Consumer Engagement — H2What's New — Menu AnnouncementsCurrent question firstCheckpoint 04
NOWCheckpoint 04Current
Open questionHighest-value questionNeeds Priya + Evan; Maya only if evidence is insufficient

Should relevance use a fixed radius, delivery zones, or a user-selected neighborhood?

Blocks readiness

Blocks the geo-relevance readiness condition and the targeting acceptance criteria.

Add meaning, not a reaction.

Priya Raman · Initiative Lead
18 MIN AGOObserved
Current code evidence

Existing subscription matcher supports bounded geographic predicates

github.com/acme/dining · 8f31c2a · src/subscriptions/matcher.ts:84Observed 18 minutes ago · current actor access verified
Changed since checkpoint

The source was rehydrated and actor access verified. The locator did not change.

Unavailable source

Prior planning transcript access could not be verified. It was not used; continue from current verified evidence or request access.

PRIORIntake v2
Carried assumption

A fixed 3-mile radius is sufficient for relevance.

New contradiction

Restaurant delivery boundaries are already normalized as delivery zones; radius coverage can cross service boundaries.

Showing live workflow state for Current Ledger.