Associate history feedback: target, position and references checks
Later text is not necessarily feedback; an explicit link is not completion
CollieRadarReplyHistory associates only later-position updates whose references explicitly identify the reply’s request_id or, outside draft mode, its URL. History also checks target, entry identity, positions and URL components. This read-only structure is not reading, completion or truth certification. No history database/association engine is added.
Different from retrieval and request receipts
Retrieval checks coverage; receipts check submission. Here whether fetched history belongs to the target and which records associate with a reply matters. No original is fetched or private record edited.
| Check | Verified scope | Manual review | Not established |
|---|---|---|---|
| Entry identity | Nonempty unique id, reply/update kinds | Actual entries/loaded IDs | Identical text means same record |
| Target URL | Host/port/path/query checks | More than domain appearance | Any cross-task comment can be merged |
| Position | Order/loading counts consistent | Earlier/later relationship | Nearby times establish association |
| request_id | Reply has valid UUID | Actual explicit reference | UUID proves approval/signature |
| references | Count/uniqueness/reference shape | Canonical lowercase UUID or permitted comment reference | Body semantics guessed |
| Feedback | Later update explicitly references reply | Association versus meaning | Read/done/approved |
| Draft history | Specific URL/time-field conditions | Draft versus non-draft | Unconditional mixed history |
| Editorial retention | Target/original links/unknowns | Authorized scope only | Cross-account index/immutable log |
Synthetic association review
A later entry says seen but references do not identify the original sample reply. Prose alone does not establish feedback for that reply. Conversely, valid association still needs content review instead of automatic handled status.
Matching target components does not authenticate origin. Keep structural gaps instead of fabricating references. No real history read, account authorization or cross-target merge ran.
FAQ
Does any later mention establish feedback?
No. Explicit references, position and kind matter; no semantic guessing.
Do valid references mean handled?
No. Association differs from actual feedback, reading and completion.
Can all same-domain comments form one history?
No. Port/path/query, target and entry rules also apply.
Does UUID shape prove an approver?
No. Reference shape provides neither identity nor authority.
Can draft and formal history be freely combined?
No. URL/time and paging consistency need separate review.
Can invented references repair a failure?
Do not fabricate associations. Preserve originals/gaps and use real source maintenance.
Reading and source
Retrieval scope · Request receipts · Confirmation scope · Start · Privacy
