It keeps a ledger of the asks the Factory puts to you, the minutes each takes, and any rule you state in your own words.
What it does
An ask is anything that needs you: an item only you can do, an agent's question, or a time you stepped in unasked. Parked items and defaults used live without your answer count too. Each week counts your asks, repeats and minutes, including reading the updates at 175 words a minute. Your weekly note gives your minutes outside asks and one tap: delight, frustration or neither. A count is exact only when nothing the ledger can see is missing; otherwise it says "at least".
No study yet: this module has no plate position.
How it links
- It records into the Command journal.
- It works out your Monday-to-Sunday weeks with the Lifecycle schedule's calendar.
- Its counts take the form Portfolio uses: exact, "at least" a number, or unknown.
- Each gap in a count has one plain phrase, so the digest and the dashboard will word it the same way.
- Intelligence declares that it uses no AI model.
- The Owner digest does not yet read this ledger.
Limits and status
Honest limits:
- It has run only on test data, built from GitHub runs recorded on 29 September 2026. No real ask is recorded, and no channel writes to it.
- A count is only as complete as the list of channels that reach you, which the ledger takes as stated. A listed channel marked as not writing makes the counts "at least". So does an ask through a channel the list misses, for every week of that list. A channel left off the list that records nothing, or one wrongly marked as writing, cannot be seen.
- A week's counts can read exact only once the week after it has ended. Anything reported later is still counted, and the week, with any measurement window holding it, then says "at least", naming the late report, or the clocks if they disagree about it.
- An ask's minutes are settled only when its answer gives them; until then they read "at least". Your minutes are what you or a channel report, and reading time assumes 175 words a minute.
- The measurement windows start in the two weeks after the one in which your first live ask is recorded. The evaluation weeks come thirteen weeks later. The ledger does not judge whether the targets are met.
- A rule is recorded, never applied. It needs your class, and it never covers a push, a payment, an account or terms.
- Your do-it-yourself estimate is taken once for each class, with your first live answer in it, before you have seen what the class costs. Estimates and rules given while the ledger rehearses have no standing: they are kept, and shown apart.
- The records are statements, not proof: anyone who can write the journal could change them.
- Each record keeps the times its clocks showed, and none is turned away for them, except an answer timed before its own ask, or an ask or update timed before the ledger opened. Clocks that disagree matter only where a record could land in another week, a report could be late or not, or the measurement windows could move. There the counts say "at least" for good and name who recorded the records. A disagreement inside a week changes nothing.
- Where a record's time is ahead of your clock, the weeks it could belong to say so while it is. A clock error nothing contradicts goes unseen.
- It keeps the words it is given, so it cannot tell whether a subject or a rule holds something private.
- It holds about 30 weeks of 30 asks a week. When full, it refuses new asks and updates, and every count except your weekly note's says so. Moving to a new ledger is not built.
Status: Accepted local implementation: independent Astra reviews and combined checks passed. No live asks or applied rules. Acceptance and evidence.
Run the local commands. Live use remains separately commissioned.