Ledger

Concentration

Figures below are the published rule run over the example chain, not the real record, which has not opened.

Contributors on this record: 1.

Tripwire

State: escalated. The tripwire adopted in socaity-19p escalates entries once the founder share of an epoch rises above a published threshold. No threshold value is published in the parameter set yet — and the founder share is 50 of the 50 vu in epoch 0, or 100% of it, which is above any threshold a value could be set to. So the state is escalated by construction, and it stays escalated until the number falls, which requires somebody else's entry.

Your epoch

Epoch 2 has not opened. Founder hours recorded in it: 0 vu. Epochs are separate pools — an epoch's denominator sums that epoch's entries and no others — so a hypothetical entry run through the published rule in epoch 2 returns a founder share of 0%. Epoch 0's concentration is arithmetically incapable of reaching it. The founder's share of the epoch you contribute to starts at 0% and rises only if he logs work in that epoch too, on the same rate table, with the same evidence bar.

Computed the same way as the calculator below: one hypothetical entry, the published rule, nothing recorded. Recompute: python3 tools/render/generators/ledger.py your-epoch

The rule that converts a contribution into a share

One screen, whole. The conversion schedule V is a table keyed by category and native unit; a contributor does not declare a rate and cannot propose one.

Then, for an epoch that has closed and been audited: the weight of an entry is its quantity times its rate; the denominator D_e is the sum of the weights of every included entry of that epoch, counted the same way whichever mode was elected; the epoch share of an entry is its weight over D_e, as an exact fraction. That is the whole conversion. It is rule/distribute.py, rule/valuation.py and rule/params.py, published as code, pinned by hash on the record at the event marked "the rule is published": rule version 308296bd81fc, parameter set 5633b6fcaebb, both resolvable in rule/RULE_VERSION.json.

An epoch weight is not money and confers no right to any. There is no transfer operation in the code, in either mode, and there is no per-unit price. Whether an amount is ever declared against this record is discretionary and remains so.

The parameter values above are the development placeholder set. That is why the real record has not opened: the rule refuses to open epoch 1 under a parameter set that still carries placeholders.

Recompute the whole page

git clone https://github.com/socaity/socaity.dev
cd socaity.dev
python3 tools/render/generators/ledger.py

That command prints every figure on this page. It is the same file that renders the page, calling the same functions: there is one implementation, not a page and a copy of the page's arithmetic.

The attestation statement

The record carries a signed attestation before an epoch may open. It is reproduced whole; its digest 9b38fdeb8762 is the statement_hash on the "the attestation statement is signed" event.

ATTESTATION ACCOMPANYING THE OPENING OF AN EPOCH
socaity.dev — example artifact (ledger/example/seed.py)

This statement is the artifact behind the statement_hash carried by the
rule.attested event that precedes epoch.opened(1) in the example chain. It is
an example instance of the attestation gate adopted in socaity-19p: an epoch
may not open until the person signing the record has said, in public and in
their own name, the four things below.

I attest, as the person who signs the events in this record:

1. The conversion schedule V that this epoch opens under was published before
   any observation it prices was recorded. Its exact bytes are committed, and
   the hash of the parameter set is on the record ahead of every entry it
   values.

2. The same table applies to my hours and to everyone else's. It prices one
   contributor-hour as one valuation unit, in every category, for every
   contributor, including me. There is no founder column, no multiplier, and
   no discretionary adjustment available to me at entry time. My own rate is
   therefore at or below the referent this schedule is pinned to, because it
   is the only rate the schedule has.

3. I have no interest that a change to V would advance and no one else's does
   not. I am not a beneficiary of the rate I set beyond being one of the
   people it prices, and I gain nothing from this schedule that a later
   contributor recording the same hours does not gain identically.

4. When I find an error in my own entries — and I will — I will correct it
   through the public challenge machinery on the record, not by quietly
   amending anything. Nothing on this record is edited; corrections are new
   events with their own signatures.

An epoch weight is not money and confers no right to any. Whether anything is
ever distributed against this record is discretionary and remains so; this
statement binds how the record is kept, not what anyone receives.

Source: ledger/example/attestation.txt.

What would a contribution of mine be worth?

Two inputs, because the rule takes two: a category and a number of hours. There is no rate field — the rate is published, not declared. There is no mode field — accepted contributions are recorded in the epoch-share mode as a published constant. There is no epoch field — an entry's epoch is its position on the record, not a choice.

8 vu
If epoch 1 closed on this record: 40% of it
8 h × 1 vu per hour; denominator D₁ would be 20 vu

The vu figure is final at entry: it is fixed by the hours and the published rate, and nothing later changes it. The percentage is an upper bound, quoted only as "if epoch 1 closed on this record" — the numerator is fixed and the denominator only grows, so the only direction it can move is down. That is the honest version of the answer, and it is the reason the next line of this record is worth writing: entry two does not exist yet.

How this works, exactly: the page is static, so there is no rule engine running in your browser and this page does not contain a second implementation of the rule. All 48 combinations below were computed when the page was built, by calling rule/distribute.py and rule/valuation.py — once per combination, over the chain, with one hypothetical entry appended and the epoch flipped to closed. The script on the page does a table lookup and no arithmetic. Recompute any cell yourself: python3 tools/render/generators/ledger.py hypothetical code 8