cortex: let a human file a materialized copy back, without losing the anchor
The automatic pass-through still skips documents that came FROM Cortex - same bytes, same sha, a no-op. But an explicit "File to Cortex" on one is exactly what §5.S4 is for: once a corpus document has been edited in a matter it is a work product, and refusing to publish it would leave the best case for the button unserved. Unedited, Cortex just dedupes it. The filing result is recorded as cortex_filed_id rather than overwriting cortex_id. cortex_id is the staleness anchor pointing at the ORIGINAL corpus document; repointing it at the copy's own filing would make the copy look permanently up to date against itself. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
| Repository | emileriksenkeev/sydOS |
|---|---|
| Author | emileriksenkeev <emil@keev.co> |
| Authored | |
| Parents | cc7b9f0a |
| Stats | 4 files changed , +40 , -13 |
| Part of | Cortex - company-wide document corpus integration |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-653ea76e.md
from inside the repo you want the change in.