Skip to content

fix(archivist): let the family retry a filing the AI could not classify - #170

Merged
arthware-dev merged 6 commits into
mainfrom
fix/classify-retry-and-empty-diary
Sep 27, 2026
Merged

arthware-dev merged 6 commits into
mainfrom
fix/classify-retry-and-empty-diary

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

Summary

  • A filing the AI could not classify says to reply in its thread to try again, and that reply reclassifies it; the error is logged. It used to advise ./stack up ai on a stack that uses a server elsewhere.
  • A fresh install no longer logs a failed diary compile while the memories room is empty; ./stack ai switch managed --model <id> installs that model; ai switch prints its report over ssh.
  • Em dashes removed from the installer's sign-in hint and from answer evidence lines; the driver posts files under their own name.

When the AI server failed, the filing reply told the family to set up
AI with `./stack up ai`, which is wrong on a stack that uses a server
elsewhere. It also carried no filing envelope, so a reply in its
thread was taken as a search, and the error itself was never logged.

The reply now says the AI could not read the document and that a
reply in the thread tries again. It carries the filing's envelope, so
that reply reclassifies the document. The classifier's error is
logged with the document id.
With nothing recorded in the memories room yet, the diary published
its empty page and returned without the `--json` report. The
archivist posts cards from that report and took its absence for a
failed compile, so every fresh install logged `diary job: compile
failed rc=0` until the family recorded something.

An empty room now reports no cards.
`./stack ai switch managed --model <id>` wrote the model only after
`./stack up ai` had installed the engine, and the install downloads
the model `[ai] default` names at that moment. After a switch from
another server that was the other server's model id, which the
install could not download.

The model is now written before the engine comes up, and put back
with the rest of `[ai]` when that fails. The command also prints its
report without a terminal, so an admin over ssh sees what it did.
The installer's closing screen is product text and follows the project's writing rule.
An answer's evidence lines joined the title and its details with an em dash. They use the middle dot the details already use.
Files were copied to the instance's Mac as `driver-<time>-<name>` and posted under that name, so a filing without a title showed the driver's name instead of the file's, unlike an upload from a phone.
@arthware-dev
arthware-dev merged commit 1d8bede into main Sep 27, 2026
1 check passed
@arthware-dev
arthware-dev deleted the fix/classify-retry-and-empty-diary branch September 27, 2026 15:21
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