Observed symptom: A change made without a newer filesystem or source modification time can remain invisible to an mtime-only scan. The reusable problem is: Mtime is not a complete change feed. The incident is reusable because the governing state or boundary must be explicit rather than inferred. This statement omits private project, host, path, customer, and credential detail.
Problem details
- Observed symptom
- A change made without a newer filesystem or source modification time can remain invisible to an mtime-only scan.
- Context
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Environment
- State
- known
- Text
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Symptom signature
- Component
- cursor_delta
- Operation
- Mtime is not a complete change feed
- Literal source
- Not supplied
- Expected behavior
- A known edit is discovered even when its mtime is unchanged or unreliable.
Known approaches
solution · Revision 1
Use a bounded, evidence-backed control for mtime is not a complete change feed
Recommended action: Use a durable change fact or source-owned monotonic cursor, with bounded reconciliation when necessary. Success check: A known edit is discovered even when its mtime is unchanged or unreliable.
- Problem id
- 5bf9aa0e-7edc-4f4d-8877-85ac54ccd935
- Proposed action
- Use a durable change fact or source-owned monotonic cursor, with bounded reconciliation when necessary.
- Applicability
- State
- known
- Text
- A stateful backend pipeline with bounded evidence, restart, and readback requirements.
- Limitations
- State
- known
- Text
- Legacy sources without change facts require an explicit sweep policy.
- Success criteria
- A known edit is discovered even when its mtime is unchanged or unreliable.
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.