Skip to content

feat: an agent can say a document has had its day, and the archive - #66

Merged
rgdevment merged 4 commits into
mainfrom
rgdevment/Flag-And-Return
Sep 23, 2026
Merged

rgdevment merged 4 commits into
mainfrom
rgdevment/Flag-And-Return

Conversation

@rgdevment

Copy link
Copy Markdown
Owner

No description provided.

…eps where it came from

flag_doc marks a document an assistant found is no longer worth keeping, with the
why; archiving it, deleting it and taking the mark off stay the person's, from the
window. A document put away on its own now hangs from the folders it came from
inside the archive, and unarchiving asks where it lands. The Documents heading
stays at the edge of the scroll, so the archive below it is never read as the
other Archive.
…stops inventing folders

Archiving a marked document takes the mark off, so nothing is left asking and the
archive carries no mark of its own. What the archive keeps of a deleted folder is the whole
way down to it, and a folder made again under that same way is the one the document
hangs from rather than a second one beside it. Unarchiving asks with a list that
fits. The cache holds the document whole, so its schema moves with it: mixed builds
were rewriting rows without the mark and reading them back as the truth.
… a filing that fails

An assistant can put a document away, so archiving only takes the mark off when the
hand is the person's — otherwise an assistant could bury what it had just asked. What
the archive keeps of a deleted folder now lives until the document lands somewhere,
not until it leaves the archive, and making that folder again makes the whole way down
to it rather than a loose one at the root. A mark inside a folder the person archived
is no longer announced to agents while nothing can show it, a destination that went
away while the dialog was open falls back to where it came from, and the room a pinned
heading needs is measured from the heading itself and asked only of the rail.
Asking the Store what it has wakes its own errand and answers with the state from
before it ran: the log has it saying nothing for this package nineteen times at
15:06 and the Store staging the newer one at 15:07. A person who pressed the button
now waits that errand out, up to a minute and a quarter, and is told what came of it.

A package of ours already registered beside the one in use is the Store's errand
finished — it cannot replace a running copy, so it waits for the window to close and
the Store's own answer never mentions it, having nothing left to fetch. That is now
read off the machine and said plainly, with no button offering to fetch it again.
@rgdevment
rgdevment merged commit 566d686 into main Sep 23, 2026
12 of 13 checks passed
@rgdevment
rgdevment deleted the rgdevment/Flag-And-Return branch September 23, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant