The mechanics,
in full.
Nothing here is a metaphor. These are the actual rules the network runs on — the unit, the tiers, the gate, the audit, and the line where the machine stops and a human decides.
A goal is never
one thing.
Every engagement is broken into a graph of nodes. Leaves are the priced, estimated units of work — each with an owner and an hour count. Branches are pure rollup containers whose hours are exactly the sum of their children, and which are never separately priced.
That last rule matters more than it looks. It means no oversight multiple, no management surcharge, and no layer that bills for existing above the work. If someone designs the graph, that design is its own leaf sitting beside the others — not a percentage skimmed off the top.
| Execution class | LOG budget | Note |
|---|---|---|
| Mini | 1 | A single hour of qualified work |
| Micro | 4 | One BSize — a standard focused work block |
| Minor | 8 | Two BSizes |
| Medium | 16 | Four BSizes |
| Major | 32 | Eight BSizes — the ceiling for a single leaf |
One LOG =
one confirmed hour.
The LOG is the atomic unit of account. Not a point, not a token, not a score — one hour of qualified member work. The dollar figure is a conversion rate applied to it, never the starting point. We size the work first; the price follows.
The cycle, running now
A cycle is the network's heartbeat. Work happens, verification closes, settlement runs, the arithmetic is audited, and the cycle seals. A sealed cycle is immutable — the record of what happened cannot be edited afterward.
The price is an output,
never an input.
Most operations name a number before they understand the work, then spend the engagement discovering what they agreed to. We derive the number from the map: every unit of work carries an hour estimate and an owner, and the price is what those add up to. If the map changes, the derivation changes with it — visibly, and before anyone signs.
The reserve that funds the network is built into that figure off the top rather than added on afterward, so there is no second number appearing later. The client sees one flat number, and the derivation behind it is available on request.
The window, and the gate
Before a price exists, the work is measured against the time available. Where the estimated work cannot fit the window — where the critical path alone runs past the deadline — the network declines to quote and states what it would actually take: more members, or a longer window.
Earned,
never assigned.
Four tiers, each with a published rate and a cycle commitment. Rates are fixed and disclosed before a member accepts work, and they do not change mid-engagement. Commitments run 1 : 2 : 3 across the top three tiers.
| Tier | Cycle commitment | The work |
|---|---|---|
| Apprentice | 58 LOGs | Supervised execution, building standing |
| Wrangler | 116 LOGs | Execution — defined work, done |
| Architect | 232 LOGs | Design & structure — the decomposition itself |
| Operator | 348 LOGs | Judgment & ownership — the calls that carry consequence |
The math decides,
not the relationship.
Reputation is computed identically for every member at every cycle close. No one enters the network at a high standing; everyone begins provisional and builds from there.
Four things feed it: whether the work was delivered, whether it was on time, whether the member kept it up across consecutive cycles, and whether anything went to dispute. Delivery carries the most weight by a wide margin. There are no hidden inputs and no discretionary adjustment — the same calculation runs for everyone.
Two views, never conflated
Every decomposition maintains a pricing view — as fine-grained as the work honestly requires, feeding price alone — and a standing view, a small fixed number of collapsed checkpoints feeding the reputation formula alone. However finely the pricing view splits, it is never the structure standing is scored against.
Once a cycle closes,
it doesn't change.
Work is verified, then paid. Before a cycle closes, the books are checked — every figure has to add up to the total, exactly, or it doesn't close. Once it does close, the record of what happened is fixed and cannot be quietly edited afterward.
Rails
Bixxville acts as the direct counterparty to every payment — never as an intermediary holding someone else's money in between.
| Rail | Instrument | Note |
|---|---|---|
| Bank transfer | ACH, wire, direct deposit | Primary rail |
| Card | Debit / credit | Fees borne by the engagement, never deducted from member pay |
| Cash & check | In-person, local | Recorded to the ledger on receipt, same as any inflow |
| BTC | Self-hosted BTCPay Server | Optional |
| USDC | Ethereum node or API provider | Optional |
The machine plays.
The human authors.
The system acts freely wherever a mistake is cheap, reversible, and checkable by an objective gate. It stops and waits for a person wherever a mistake is permanent, or cannot be honestly verified.
Five decisions reserved to humans, permanently
Artificial intelligence is admitted on three conditions: it accelerates but does not govern; its work is gated and inspectable by the same objective standard as any member's; and the network runs on its own logic without it. The analog system is the real one. The network is never hostage to a model, a cost, or an outage.
What every member
is owed.
Nine guarantees that cannot be abridged by the runtime, by Land of Geb, LLC, or by the Bixxville Foundation — except by formal amendment.
See the model on a contract.
How a federal task order runs through decomposition, the gate, the wage floor, and the audit — and what we can and can't bid today.
Contracting →Join the network.
Four tiers, standing earned on delivered work, and the lanes the network currently runs.
The Network →