INDORANIATry it

Show how the job was done · Oreoasis

Work receipts, for people and AI

A job by a person or an AI helper is recorded as its steps, never as keystrokes or screens. A person who answers for it signs it off.

built, not open yetBuilt, but you cannot use it yet.Try a practice run

Who does what

  • Peoplekeeps

    Keep the work you signed as your own record, whoever you worked for.

  • Institutionsconfirms

    As the client, accept the finished work with one tap.

  • Businessessigns

    Keep receipts for the steps of the jobs your team and your AI helpers do.

  • Communitiessigns

    A cooperative signs off its members' work.

who pays

Confirming, keeping and checking are free for everyone. An organisation pays to run its records and its requests, never for each receipt. Pricing

planned for this service

Who did it, and what they were allowed to doplanned

Each job names who did it, whether a person or an AI helper, and the limits set for it. A step outside the limits is marked, with the doer's reason, and never scored.

goes well with

Pay on proof: Money is released when the site visit is confirmed and the work is signed off.

What this receipt says

What’s on it
Each step, what went into it, the limits it worked within, and the sign-off. Never keystrokes or screens.
Who keeps it
The worker keeps their copy. An AI helper's key is tied to a person.
What it proves
Done this way, within these limits, and signed off by this person.
Who can check
Anyone, for free, without asking us.
Where
As exact as the keeper chooses: a river area, a kind of land, a town or an exact spot.
When it ends
It depends on the plan. Oreoasis is built to keep receipts for 30 days, 13 months or 3 years.
how it works, for builders
  • open@kashscript/attest

    Signs records as DSSE envelopes and checks them offline. [v 09-24] npm view: latest 0.1.8, which depends on identity-core 0.3.1 and installs from an empty folder; 0.1.5 is deprecated. Round trip on this app's own receipts: four verifies exit 0 (two signed under 0.1.3, two under 0.1.8) and a tampered ledger row exits 1 (PAYLOAD_HASH_VARIANCE). Tested on Windows only.

  • built, not open yet@kashscript/hudhud

    Signed action ledger, SOP compiler, work certificates. Published 0.1.1; one consumer, Oreoasis (STACK [v 07-27]).

  • built, not open yetOreoasis core-host and SDK

    Agent receipts, ingest, retention windows, billing through a Merchant of Record. [v 09-24] nslookup api.oreoasis.com: non-existent domain, and it is the SDK's default ingest host, so nothing can be sent yet. www.oreoasis.com serves its landing page (curl: HTTP 200). @oreoasis/sdk 0.1.0 now installs from an empty folder (npm i: 3 packages, resolving attest 0.1.8); it could not from 2026-08-01 (STACK [v 09-14]).

  • built, not open yet@kashscript/identity-server

    Guest countersignature by link, and agent tokens bound to an owner. [v 09-24] npm view: latest 0.2.0 (was 0.1.1 here), depending on attest 0.1.6 and identity-core 0.3.1. Built, not open: no ceremony host exists (this app has no route for one) and one must exist before anyone can confirm by link.

Shown as no more open than @kashscript/hudhud.

Who did it, and what they were allowed to do

  • open@kashscript/attest

    Signs records as DSSE envelopes and checks them offline. [v 09-24] npm view: latest 0.1.8, which depends on identity-core 0.3.1 and installs from an empty folder; 0.1.5 is deprecated. Round trip on this app's own receipts: four verifies exit 0 (two signed under 0.1.3, two under 0.1.8) and a tampered ledger row exits 1 (PAYLOAD_HASH_VARIANCE). Tested on Windows only.

  • built, not open yet@kashscript/hudhud

    Signed action ledger, SOP compiler, work certificates. Published 0.1.1; one consumer, Oreoasis (STACK [v 07-27]).

  • built, not open yetOreoasis core-host and SDK

    Agent receipts, ingest, retention windows, billing through a Merchant of Record. [v 09-24] nslookup api.oreoasis.com: non-existent domain, and it is the SDK's default ingest host, so nothing can be sent yet. www.oreoasis.com serves its landing page (curl: HTTP 200). @oreoasis/sdk 0.1.0 now installs from an empty folder (npm i: 3 packages, resolving attest 0.1.8); it could not from 2026-08-01 (STACK [v 09-14]).

  • plannedAttributed work record

    Names who did each step of a job and the limits set for it; a step outside them is marked with the doer's reason, never scored. [v 09-25] ECOSYSTEM d43 and ROADMAP S5(c) as read. Oreoasis's git log has commits dated 2026-09-24 on the work record, deviations and acceptance (git log); none was run or verified here, and nothing is reachable while api.oreoasis.com does not resolve.

Shown as no more open than Attributed work record.

Not yet true

This service is built, not open yet.

Built, but you cannot use it yet.

Nothing on this page is open to the public yet, except the practice run.