Factory docs, home
Page navigation

See the input → responsibility → output diagram.

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. Beside the ledger, it keeps the rules you confirm, so the Factory will check whether an action still needs you when callers adopt them.

A slate-blue bob with spectacles, a blank notebook and a pencil.

Meet the clerk. Every ask and minute, noted. Keeps a ledger of the asks Factory puts to you, the minutes each takes and the rules you state. Meet the whole Plumb family.

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".

Your rules are kept apart from the ledger. The Factory drafts a rule in words, for one class of ask and the Products it names, with how many days it lasts (at most 92). It counts only once you confirm that exact wording live. When callers adopt the protocol, the Factory will check before acting: the answer is "ruled" only while a confirmed rule covers the class and Product and the action involves no push, payment, account or terms. If it cannot tell whether the action involves one of those, or cannot read your rules, the answer is "unknown". Otherwise it asks you. Each action a rule allowed is recorded, and one "should have asked me" from you demotes the rule for good. Room for that is kept with each action, and an action is recorded only if its "should have asked me" can be, so it is never refused because the rules are full or an ID is too long. A rule lapses when its days run out, until you confirm the same wording again. A new record of an action cannot claim an instant after its recording clock; past records and an original retry keep their recorded history.

No study yet: this module has no plate position.

  • It records into the Command journal.
  • It works out Monday-to-Sunday weeks with the shared calendar, without starting a schedule.
  • Its counts share the reporting 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.
  • Your rules never read the ledger's answers. Repeating the same rule in many answers makes no rule: only a draft you confirm does.
  • The Owner digest module does not read this ledger itself. The local digest command takes its open asks from it, and can record a formed digest as the week's digest update once you say it was sent; it sends nothing.
  • The local commands can also show the ledger, a page of asks, a week's counts, the measurement windows, your classes and your rules, without writing anything. With no ledger they say so, never zero asks. A rule recorded while the ledger rehearses is shown as having no standing.

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 written in an answer is recorded, never applied. It needs your class, and it never covers a push, a payment, an account or terms.
  • A confirmed rule has run only on test data. Nothing in the Factory checks it yet, there is no command for it, and the digest does not yet show its actions with a "should have asked me" button. A demotion does not undo what the rule allowed.
  • A confirmation counts only for the exact words you saw: any change to the words, class, Products or days needs a new confirmation. A rule confirmed while rehearsing has no standing.
  • Anyone who can write the journal could confirm a rule in your name, so a confirmation is a statement, not proof.
  • 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 Ask Ledger 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.
  • One journal file holds one ledger. To keep separate ledgers, such as one per owner, use separate journal files: sharing one journal between ledgers is not yet supported.
  • The first week of 1970 (1970-W01, which begins on Monday 29 December 1969), given to a report, an ask listing or a weekly note, is refused with the scheduling error the Factory has always used; earlier weeks are refused with the ledger's own error. This module now offers that scheduling error itself, so code using it can recognise the refusal without loading the scheduler.

Status: Accepted local implementation before this extraction: independent Astra reviews and combined checks passed. No live asks or applied rules. Acceptance and evidence. The rules you confirm are built on test data. The fresh-use time correction passed affected native checks and distinct independent source review; wider caller and live-host adoption remain open.

Contract and limits

Run the local commands. Live use remains separately commissioned.

A private package draft records caller-owned asks without Factory setup. Existing counts and recorded weeks remain unchanged. It was accepted locally on 1 October 2026.

Shared value implementation: common contracts. Owning errors, limits, stored identities and authority remain as specified above.

Source: docs/guide/owner-policy.md