Reading your files
In your inbox
none✓
Needs you
none
What the archive says
nothing yet From filed documents only. No model call.Arriving on a rhythm
Three documents establish a patternDates ahead
Also added to your Google CalendarWhat it came to
Recurring and one-off, per currencyWhat Orden decided
noneWhat you have taught it
Corrections become rulesEvery decision
Newest firstSettings
What comes next
Not built yetOrden reads a folder and files what it finds. Everything below widens one of those two ends: where the documents come in, or what it is allowed to do once it has understood one.
Calendar that stays in step
Today a date read off a document is written to the Orden calendar once. Next it keeps step both ways: a renewal that moves in the amended contract moves the event, a deleted file takes its dates with it, and an event you edit by hand is left alone.
Needs: a stored link from each event back to the document and the sentence that produced it, so a change can be traced rather than guessed.Attachments straight from email
The invoice that arrives in your inbox is the one document that never reaches the folder Orden watches. An address of its own, so forwarding a message puts its attachments in the queue with the sender, subject and date already known, and the body read as context for where the file belongs.
Needs: the sender proved, not trusted. An address anyone can post to is an address anyone can file into your Drive with.Decisions that do more than file
Filing and renaming are the two safe things to do with an understood document. There are others: reply to the sender that a bill was received, flag a contract to somebody before it lapses, hand the figures to a script you already run. Each would be a named action you switch on one at a time, never a general licence to act.
Needs: the same ledger these already have. An action that leaves the Drive has to be reviewable before it runs and undoable after, or it does not ship.