Eggs are continuous output from a producing asset. The batch does not close, nothing transfers to COGS, and the flock keeps amortizing.

FCR, growth curves and lay % are all rate-per-day. Storing 42 bags on one date puts a spike in every chart and makes the day-14 sampling weight meaningless.

The feeding counts on Tuesday — that's the day FCR, stock and the ledger use. Thursday is only the audit fact of when it was typed.

occurredAt is captured on the phone, recordedAt on the server. A queued entry that sends 6 hours later still lands on the right day.

Same rule as a correction: the past is never edited in place. Reopening writes a reversal and a replacement; posting to August writes a fresh entry. Both leave a trail.

The demo seed already covers all eight enterprise types. Letting someone evaluate before typing a single number costs nothing to build.

The system stores a location of type house. The farmer sees whatever they already shout across the yard. Forcing "Poultry House 01" makes every later screen read like someone else's farm.

These birds have already eaten 22 days of feed. If we pretend they haven't, the first cost-per-bird you see will be a lie.

Not in a wizard. The first time this farmer opens cost-per-bird, the question comes back — because that is the first moment the answer changes anything.

Farm name → one enterprise → one place → one batch → one entry. Chart of accounts, contacts, workers and cash balances are all deferred, and none of them blocks anything.

Only two concepts genuinely need explaining: basis, and that fixing a number reverses and reposts rather than overwriting. Each gets one inline moment the first time it happens.

Each of these becomes a question in Today at the moment it first matters — not a checklist nagging from day one. Onboarding ends; setup keeps going quietly.

The owner knows. Making the worker find a language setting before they can read the language setting is a loop worth avoiding.

Same binary, and almost nothing in common with what the owner opened. Worker onboarding is not a shortened owner onboarding — it is its own thing, and treating it as a subset is how it ends up with a farm-creation form in it.

The question was deferred at signup and returns at the exact moment the answer changes something the farmer is looking at. Now they have a reason to go and find the receipt.

Derived from the active batches: what each one expects today. A farmer arrives with one job. Charts are for people who browse.

No farmer goes looking for a "capitalize asset" button. The system raises what it needs, on the right week, in the farmer's words — and keeps asking.

The farmer says "Pond 3". The system means FSH-2026-02. For a smallholder they are 1:1 nearly always, so navigate by place and resolve to the batch.

The FAB knows where you are and what this batch usually gets. The full log-type list is the fallback, not the front door.

Entry count and measured-share are the worker's performance in terms they control, and the only feedback loop that improves data quality.

One field resolving contacts, batches, places and entries. Everything a three-tab structure necessarily hides is reachable in one field — which is what makes three tabs defensible.

Iya Basira buys fish from one and maize from the other. She is entered once for the business, not per farm.

It should. The farmer's mental model is "change the number". What the system does underneath is not their problem — but it must never be a lie about what the books now say.

Because someone acted on it. Feed was ordered against a 3.1 FCR. The trail is how you find out that a bad decision came from a typo rather than a bad bird.

Conversions are per item. A basket of tomatoes is 24 kg; a basket of pepper is 18 kg; a bag of maize is not a bag of NPK. One global unit table would be wrong within a week.

A buyer becomes mandatory the instant payment is anything other than paid-in-full. You cannot chase a debt owed by nobody.

The sale is recorded either way. Revenue and stock movement happen on delivery; the payment is a separate record that may arrive weeks later — or in three pieces.

Held credit is money you owe her, not a sale. Booking it as income inflates this month's profit and understates next month's.

A quantity dispute changes stock and revenue. A price dispute changes revenue only. Collapsing them into "adjust the amount" silently loses 9 kg of fish.

Same shape as grading a harvest: inputs, a criterion, several outputs, losses, and a cost that has to follow. The difference is that fish can be moved back, and that handling them kills some.

Exactly as waste and packaging sit on a processing run. Handling mortality is caused by the sort — attributing it to the pond's background death rate hides that grading day was rough.

This is the only place a farmer is ever asked about costing, and they are not asked in those words. They are asked "which of these will lay?"

No new batch, no cost split, no new cost pool. The 22 birds are located elsewhere and are expected back.

Whatever the default, the merged batch must record which rule was applied. Six weeks later, "why is FCR 1.1?" has no answer without it.

The farmer never sees this word. They chose "broilers" or "layers" at setup and the archetype came with it.

One harvest, and the batch is over. Every cost it ever absorbed is now carried by 1,036 kg of meat, waiting to be sold.

Not automatically — nobody can compute point of lay from a calendar. It has to be observed and told.

A farmer will not go looking for a "capitalize asset" button. The system must raise it, on the right week, in the farmer's language — "have they started laying?"

The birds are not the product any more. The eggs are. The flock is a machine that makes them, and it wears out.

Amortization, in words a farmer already uses. The birds are 3 months closer to being spent, and that has a price whether or not anyone writes it down.

Cull month is ordinary. All the cost was recognised while the eggs were being sold. If cull month is dramatic, the flock was mis-costed for a year.

Amina also produces assets. Her heifer calf is either capitalized into the herd or moved to inventory for sale — a decision, taken at birth, that the herd reconciliation depends on.