bData

your files

what you have, who can get it and where it is kept.

nothing on this page can spend your money.
reading your files…
choose who can get it see every detail below

forever means it cannot be taken down.

pieces

tap a petal

who can get it the whole of my data
bdata://… reading bpay-invoice.json

object · bpay-invoice.json

store pipeline · public path

    sources · the receipt cites
      verify · receipt ↔ invoice, field by field, in this page
        verify · no trust in this page needed

          the whole of my data

          bData — the organism-level data surface

          My Data

          Your files — who can get them, and what it costs to keep them.

          How My Data works
          what you have · who can get it · what is happening to it · what your bees may do with it — economics live in bPay, invoked only when a data operation needs value, and the evidence returns here.
          changes what you can inspect — never the audience, never your authority

          🤖 Action policy — what may happen without asking

          The rules behind this
          a first-class policy dimension: autonomous actions are constrained by capability (only qualified paths) and by the economic bound you set. Changing it governs future decisions — yesterday's legitimate operations stay legitimate.
          Cypherpunk view — the whole anatomy