Diamond Dog IN THE WORKS

COMING SOON · OPEN SOURCE

Delegate work,
not your identity.

A delegation-first operating environment for giving software a job. And being quite particular about what else it may do.

Meet Diamond Dog

First experiment under way.
Good work takes a little groundwork.

A sturdy black dog with folded ears and a diamond collar tag, carrying a very long receipt.
FETCH THE WORK. BRING THE RECORD.

01 / THE ARRANGEMENT

A job should come
with a clear brief.

You already know what you want the tool to do. The question is how much else you have to hand over.

01

Give it a specific job.

A bounded activity defines what software may read, what it may change, and what needs your sign-off first.

02

Keep the scope in view.

The inspector is designed to show what a job can still do, what you approved, and what cancelling would prevent.

03

Get the whole story.

A record separates what was claimed, what was observed, what a service accepted, and what remains unknown.

02 / A LITTLE LESS BLIND FAITH

A receipt.
Including the
unknown bits.

Three contracts. One message. Your sign-off.

In this design scenario, you choose the contracts, a tool summarizes them, and the exact email goes out only after your approval. The record says what was seen.

ILLUSTRATIVE SCENARIO · NOT A SHIPPED WORKFLOW

ACTIVITY RECORD014

Send the contract summary.

Scope
3 selected documents
Action
1 reviewed email
Recipient
Your accountant

The service accepted the request. That tells us something useful. It does not establish delivery.

Select either statement to read what it means.

03 / FAIR QUESTIONS

Still in
the workshop.

The design is written down. A first experiment is under way. Nothing has shipped yet.

Can I try it yet?

Not yet. We’re testing the design on existing platforms first. This page introduces the project; it isn’t an invitation to hand over an account.

Is this just for AI?

No. The same rules apply to apps, scripts and AI participants. Diamond Dog is about the arrangement for delegated work, whoever—or whatever—is doing it.

Where will it run?

The intended environment is an open-source layer on Linux: a headless runtime and an inspector for seeing what a job may still do and what happened. It isn’t a new desktop.

What does cancelling mean?

The design aims to make clear which future work cancellation would prevent. It cannot promise to reverse something that has already happened in an outside service.

Good work.
Clear boundaries.

Explore the project The tool currently lives on GitHub as OrcaOS.