Account profileIn this appthe edit is written through a store writer and reaches the store that produces this section
/settings — Settings → Personalization → display name You can change your display name, as our account settings hold it.
Limit: The username beside it has no write route: PATCH /api/user/profile answers 501, so a username can be read but not corrected here. The write is forwarded to our backend, which is a separate system this repo does not verify, and copies cached on other devices are not reached.
Consent decisions recorded on your accountNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a recorded consent decision
Limit: A consent decision is the record of a legal act. /user/controls records a NEW decision and keeps the earlier one as evidence, so nothing here rewrites the earlier record — the correction is the new decision, not an edit of the old row.
Capability consent historyNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a capability consent event
Limit: The capability consent history is append-only by design: each entry records that a consent was given or withdrawn. No surface in this app edits an entry, and granting again adds a row rather than correcting one.
ConversationsIn this appthe edit is written through a store writer and reaches the store that produces this section
/chat — Chat → a conversation's title (sidebar session detail, or the ⌘K session list) You can change a conversation's title and its workspace assignment.
Limit: The PATCH answers whether the request succeeded; nothing here reads the conversation back, and the backend is a separate system this repo does not verify. The messages inside it are a different record and are not corrected by this.
Chat messagesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a sent message
Limit: A message can be deleted but not edited: the only write verb this app has for a message row is deleteMessage, and editing one would rewrite the record of the conversation. Correcting it means writing a new message.
Earlier chat history recordsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits an earlier-history record
Limit: The earlier-history route exposes GET, POST and DELETE only — there is no PATCH on it — so a legacy history record can be cleared but never corrected.
Sign-in historyNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a sign-in record
Limit: Sign-in history is a security log. The settings surface reads it; nothing writes or rewrites one, because a log that can be edited is not evidence of anything.
Your section records held on our serversNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface addresses a single server sync-table row
Limit: Each section's server table has a per-row delete and a sync verb, but nothing in this app lists the tables or offers a per-row editor, so a correction cannot be addressed to one. The surfaces that edit section records edit the local copy, which is the next row's question.
Files you stored — the list, not the filesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface renames a stored file row
Limit: The library's rename verb returns early for every corpus but Office, so a stored file's name cannot be corrected there. Uploading a replacement creates a new file; it does not correct the old row.
API tokens — names and dates, never the secretsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a token's metadata
Limit: Token metadata (name, dates) is readable in your export and has no editor in this app; the remedy for a wrong token is to stop using it, not to rename it here.
Security eventsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a security event
Limit: Security events are retentive by class and have no edit endpoint. The export reads them; nothing here writes one, and correcting a log entry is not an operation this product offers.
When our servers assembled this partNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
Nothing to edit — this block is a timestamp, not a record about you
Limit: This block is the servers' own export timestamp. There is no personal data in it, so there is nothing to rectify.
Research workspace (reports, threads, collections, schedules, history, templates, workspaces, activity, canvas)Not herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a research record in this app
Limit: The research workspace is a run-and-read surface: reports are backend-authored, and the store's own edit actions (updateWorkspace, updateThread) have no caller anywhere in this app — a writer with no control is not an edit path. The library's rename verb reaches Office documents only.
Psychology data held in this browserIn this appthe edit is written through a store writer and reaches the store that produces this section
/psyche/journal — Psyche → Journal → an entry's Edit form You can change a journal entry's title and text — the writable part of this section.
Limit: Scores, test results, reading reflections, check-ins and the activity log are derived or append-only records with no editor. This row names only the part a person can rewrite; the rest of the section cannot be corrected from here.
Journal entries (all four journals)In this appthe edit is the record — the writer changes the row itself, with no separate publish step
/psyche/journal — Psyche → Journal → Edit, or the correction form on this page You can change a journal entry's title and text, in this browser's journal store.
Limit: The local row is the record the export's journal reader reads, so the edit is the record. When journal sync is on, an encrypted copy also goes to our servers and older server versions are not reachable from here — this page does not confirm that copy. An incognito session, a sealed entry, or a newer document on the row refuses the write, and a refusal is reported as not performed.
Conversation list held in this browserNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits this device's conversation directory
Limit: This browser keeps a directory of conversation titles and previews for the export. It has a reader and no writer, so nothing in it can be corrected here; the conversation itself is corrected at /chat.
Records of how items in this export were madeNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a provenance record
Limit: A record says what made an item and when this device recorded it. Editing it would rewrite the record rather than correct it, so the correction is a new turn — and the record for the new turn says so. Deleting the conversation removes its records.
Journal archive (Markdown / JSON download)Not herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits the journal archive bundle
Limit: The archive is a download composed from the journal entries; it has a collector and no editor. Correct the ENTRY (the journal spine row), then download a new archive — the old file stays as it was.
Finance dataIn this appthe edit is the record — the writer changes the row itself, with no separate publish step
/trading — Finance → a transaction → edit amount, description, category, date or type You can change a transaction's own fields in this browser's finance store.
Limit: The finance writers are network-free, so nothing here reaches our servers and no server copy is claimed. The retired budgets slice has no editor, and the export does not read this section at all.
Research session history backupNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits the session-history backup
Limit: The backup is download-only: the panel reads the newest sessions and offers a download. It has no editor, and the records it holds are copies of research sessions.
Studio library and device projectsIn this appthe edit is the record — the writer changes the row itself, with no separate publish step
/studio — Studio → Film → rename a film You can change a film's title in this browser's studio store.
Limit: Only the film family has a rename verb wired to a control; the other device libraries (draw, voice, products, images) browse without one. The rename updates this browser's session list in place and also cloud-puts a copy through the library store — this app does not read that copy back, and the server-side projects and tickets are the `server_studio` row.
Reading and learning dataNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a reading record
Limit: The reading inbox's store exposes status and highlight actions, but no surface in this app calls them, and the learn schedule has no editor. A writer that no control reaches is not an edit path.
Browser consent choicesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a recorded browser consent
Limit: The cookie/analytics choice is a live control: changing it records a NEW choice. The ledger's earlier decisions are the receipt for the choice that was made and are never rewritten, so this row has no rectification path.
Data you imported from another serviceNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits an imported conversation or message
Limit: An imported row is a copy of something you brought in from elsewhere. Correcting it here would make this app a second source for content it did not author, so the remedy is the erasure path: delete the import (which removes exactly the rows it created) and import a corrected file.
Office documents, boards, sheets and foldersIn this appthe edit is written through a store writer and reaches the store that produces this section
/office — Office → open a document → edit it and save You can change a document's title and body.
Limit: The save goes to PolyBackend's `office_documents`; that server is a separate system this repo does not verify, and the export omits Office entirely (`not-built`), so your export file will not show the correction. Document versions and trash copies are not rewritten.
Saved memoriesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a saved memory
Limit: A memory has no in-place update verb: the client has a store verb and a delete verb, and an edit SUPERSEDES the old row through the corrections seam — which this build calls but which no backend branch serves yet, so the memory manager falls back to delete + re-store while that route is unavailable. The export's own read is bounded at 2 000 rows per run.
Projects and their itemsIn this appthe edit is written through a store writer and reaches the store that produces this section
/projects — Projects → a project → rename You can change a project's name.
Limit: The rename is queued to our backend through the projects hub store; this app does not read the project back, and the backend is a separate system. Items, to-dos and flows inside a project are their own records and are not reached by this.
Canvas projects and scenesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a server canvas project
Limit: Server-side canvas projects and scenes have no rename or edit client in this app. The canvas window store edits local windows, which are a different record and are not named by any export section.
Agent runs and agent logsIn this appthe edit is written through a store writer and reaches the store that produces this section
/agents — Agents → an agent → its settings You can change an agent's name, description and prompt.
Limit: The agent's RUNS and logs are append-only records with no editor, and the export omits this section, so a correction to an agent will not appear in your export file. The write is forwarded to our backend, which this repo does not verify.
Subscription, payments and usageNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a billing record
Limit: Subscription, payment and usage records are kept for statutory retention. The settings surface reads them; changing plan creates new billing events rather than correcting the old ones.
Connected sign-in accountsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a connected sign-in account
Limit: Connecting and disconnecting a provider adds or removes a grant. The profile data behind it belongs to that provider, which this app cannot edit, and there is no field here to correct.
Call transcriptsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a call transcript
Limit: Transcripts are written as content-addressed records; the contract names them and nothing in this app offers an editor. A transcript is a record of what was said.
Deletion requests and account lifecycle recordsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a lifecycle record
Limit: A lifecycle record is the receipt that a request was made. Withdrawing a request is a new act with its own record; rewriting the earlier one would destroy the evidence that it happened.
Files attached to chat messagesNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits an attachment
Limit: An attachment has no edit verb: it goes with its message, and a message can only be deleted. Uploading a corrected file creates a new attachment rather than fixing the old one.
Chat tags and tag assignmentsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a tag
Limit: The API client has a tag PATCH, but no surface in this app calls it, so a tag name cannot be corrected from here. A writer with no control is not an edit path.
Studio projects and tickets held on our serversIn this appthe edit is written through a store writer and reaches the store that produces this section
/studio — Studio → a project → its settings You can change a project's, ticket's, column's or label's own fields.
Limit: This app does not read the project back, and the backend is a separate system. The media artifacts behind a ticket have no update verb, and the export omits this section.
Other section records on our serversNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No reader, so no editor
Limit: The section tables beyond the ones this app reads have no reader here — and no reader means no editor and no way to address a row. Nothing was corrected.
Records of what was made from whatNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface edits a derivation record
Limit: The writer only appends a row: it never rewrites one, and no surface corrects a recorded derivation — editing it would rewrite the record of what happened rather than correct it. This page therefore offers no edit and no removal; the deletion row owns the removal question and says what this app does and does not have.
The contents of files you storedNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
No surface rewrites a stored object
Limit: Stored bytes are immutable here: the storage client can list, preview and upload, but nothing rewrites an object. Upload a corrected file and delete the old one — that is a new record, not a correction of the old bytes. The export withholds contents by design.
API token secretsNot herenothing propagates that this app can state — there is no path, or the target store is outside this repo
Nothing to edit — a secret is never displayed again
Limit: A token's secret is shown once and never editable: no surface can correct it. The remedy is revoke-and-create, which retires the old token instead of correcting it — and the export withholds the value by design.