Submit
A known workload enters with a bounded payload.
Development system online
Compute should be
accountable.
Kalkey coordinates approved workers, records every attempt, and turns interrupted work into recoverable progress.
Execute
One worker owns the job for a limited time.
Verify
The result and its attempt history remain visible.
THE SYSTEM
Small control surface.
Small control surface.
Strong boundaries.
Kalkey starts with deterministic coordination—not an open-ended agent with unlimited reach.
Allowlisted work
Workers execute only workload types and payload shapes the operator has explicitly approved.
Exclusive leases
A job belongs to one worker at a time, preventing duplicate completion during concurrent operation.
Recovery by design
Expired leases return safely to the queue with bounded retries and a preserved attempt history.
Human authority
Operational improvements can be proposed with evidence; permission and spending changes remain human decisions.
OPERATING PRINCIPLES
Useful work.
Useful work.
No hidden authority.
- 01Evidence before action
Results, errors, and improvement proposals carry a record that can be reviewed.
- 02Failure is a state
Interrupted work is recovered deliberately instead of disappearing or running forever.
- 03Expansion is earned
New workers, capabilities, and costs arrive only after the smaller system has proved itself.
CURRENT STAGE
Controlled development proof
The coordinator, persistent job store, recovery loop, localhost console, and independent worker package have been exercised with synthetic workloads.
Core development services running
No customer data, public worker marketplace, or autonomous spending is enabled.