A file rename should update how users find and recognise the source without accidentally creating a second document. Preserve stable identity and distinguish a metadata change from a content or permission change.
Names and resource identity differ
A filename is a display and discovery attribute. A stable source identifier represents the resource under the source system’s documented lifecycle. Some moves or copies may create new identities, so verify actual provider semantics.
For a proposed connector, track source namespace, resource identifier, current title, location, content version, permission state, and known aliases. Update only the derived attributes affected by the change, while preserving source lineage.
Do not assume a new filename means new content or that an unchanged filename means unchanged content. A user can replace a document’s body without renaming it, and a rename can leave every passage identical.
Test a fictional policy rename
A file called “Travel notes final” becomes “Approved travel policy.” Its source identity and content remain unchanged. Search should show the current title and preserve links from existing references according to the supported design, without doubling the indexed passages.
A second fixture renames a draft to include “approved” in the title without changing its governance status. The assistant must not infer authority from the new name. Publication status comes from trusted policy metadata.
| File change | Connector decision |
|---|---|
| Name only | Update display metadata and relevant search representation |
| Content and name | Reprocess affected content under current version |
| Move with same identity | Update location and re-evaluate inherited access |
| Copy creating new identity | Treat as distinct until approved relationship established |
| Misleading title | Preserve actual authority status |
Replay old and new change notifications out of order. The final title and source link should reflect the current supported state, not whichever event arrived last.
Keep alias handling bounded
An old title can help users discover renamed material, but aliases should not override current status or reveal restricted historical names to unauthorised audiences. Apply permission controls to suggestions and previews too.
Metadata-only updates can reduce unnecessary extraction and embedding work when the representation does not depend on the title. If title text is included in indexed content, re-evaluate the affected representation explicitly. Document the actual pipeline rather than assuming rename is always free.
This rename design is proposed. The voice integration case study describes related retrieval work. Pair it with changing source URLs.
Renamed-file FAQ
Should the filename be the primary key?
Prefer the source’s documented stable identity where available.
Does renaming to approved publish a policy?
No. Trusted ownership and publication state determine authority.
What should be tested after a move?
Check identity, current location, inherited permissions, aliases, citations, and duplicate passage count.