Nobody here has a password
Four kinds of actor touch a workspace: people, the devices they carry, the agents working for them, and the nodes beside your systems. People and machines hold keys. Agents borrow authority through grants that expire and only ever narrow.
Every action knows who allowed it.
Sign in to Daslab
Losing a laptop is boring
The phone, the laptop, and the command line each enroll their own key on first sign-in, kept in the device's secure hardware. Keys never travel; each device proves itself.
So revoking the lost one is the whole procedure. Its sessions end, its key stops verifying, and no other device notices. There is no shared secret to rotate, because two devices never shared one.
Agents own nothing
An agent has no account, no API key, no standing permission. Every run borrows its authority from whoever started it, through a grant: a signed note saying exactly how far it may act, and until when.
A schedule is a standing instruction, not a standing credential. Each run it starts gets a fresh grant at start time, under whatever access its author holds that day, not the day it was written.
When a run starts a sub-agent, the child's grant is cut from the parent's, and the cut only removes.
| grant | g_7f3a · run “margin analysis” |
| scope | cable-line-3 |
| reads as | Mirko · Private |
| tools | read · write:private · sandbox |
| expires | 12:47 · in 9 min |
| grant | g_81c0 · from g_7f3a |
| scope | cable-line-3 |
| reads as | Mirko · Private |
| tools | read · write:private · sandbox |
| expires | 12:47 · inherited |
History shows the chain
Every entry answers two questions on the same row: who did this, and who let them. A human edit names the person. An agent's write names the run, the grant it ran under, and the person or schedule the grant descends from.
So audit is not a report you request. The chain of authority sits on the history everyone already reads, and it says the same thing to you, to a reviewer, and to the person whose name is on the grant.
Nodes verify on their own
A node beside your ERP checks grant signatures itself rather than calling home for every action. Work continues through a dropped uplink.
Expiry is what gives revocation teeth: a grant that cannot be recalled from a node dies on its own within minutes. The node itself enrolls like a device, with one key, minted at install and revoked when the machine retires.
A company brings its own sign-in
Attach your identity provider and its rules take over: people sign in through your SSO, joiners and leavers follow your directory, and group membership decides what grants issuance will write. Daslab keeps no second list of your employees to drift out of date.
Nothing else changes shape. A solo account and a thousand-seat tenant use the same keys, the same grants, and the same history; a company adds rules at the one place rules exist, the moment a grant is issued.
Not policy, absence. Nothing to phish, reuse, rotate, or leak, for people and agents alike.
Standing access is re-earned at issuance, every time. What cannot be recalled dies on its own.
Not a side ledger bolted on for reviewers. The history that runs the workspace is the audit: the chain of authority is written on every entry.