Week of 2034-07-31 — 2 dates

• KD-01 — Ground lease expiry (reviewed): 2034-07-31 — Conditional, human-checked — Expiry per fictional lease v3; renewal terms unconfirmed. — reviewer N. Rahbar Sato
• CTR-GND-001 expiry (distinct from notice deadline): 2034-07-31 — Conditional

No fixed date — tracked via finding (4)

Standing items have no fixed date (event-relative durations, supervisor-specified dates, or Unknown deadlines). They stay honestly dateless — each is tracked via an open finding, never an invented date.

• KD-02 — Renewal notice deadline (NOT confirmed — do not diary as fact): Unknown — Unknown, NOT checked — do not rely — Notice deadline is separate from expiry and is Unknown until the clause is confirmed. — reviewer Unassigned — tracked via finding (file from the queue or the deadline register)
• CTR-GND-001 notice deadline (separate field, never inferred): Unknown — NOT checked — do not rely — tracked via finding (file from the queue or the deadline register)
• CTR-FUND-002 expiry (distinct from notice deadline): Unknown — Disputed — tracked via finding (file from the queue or the deadline register)
• CTR-FUND-002 notice deadline (separate field, never inferred): Unknown — NOT checked — do not rely — tracked via finding (file from the queue or the deadline register)

Gap detection lives engine-side (15-minute reconciler). This feed shows staged-vs-queued presence only — it never claims delivery, it stages nothing, and no external send leaves from here.

Counsel-flagged items stay human-check-gated: findings stay open + owned until a named human clears them. This surface never auto-settles them.

0 staged alert refs in the current digest preview. Preparing a digest is never sending it — no external send leaves from here.

Showing 0 of 0 change feed rows (0 with missed-linkage status, counts only).