What Camden Work is trying to establish
The worker is replaceable. The operator should not become the recovery mechanism.
That is a measurable research target. The current product is a small trusted-local Python/SQLite controller. Its useful unit is the retained obligation: authority, occurrence, owner, uncertain effect, evidence, unfinished work and verified local return.
Where Camden is not unique
Transactions, idempotency, reference monitors, durable workflow replay, contracts and output governance all have established counterparts. Related work credits those overlaps. Different vocabulary is not a technical advantage. No finite source review proves worldwide uniqueness.
Three separate achievements
| Achievement | Evidence needed | Current scope |
|---|---|---|
| Clear positioning | Coherent explanation and reachable exercise | These pages and Quickstart. |
| Demonstrated behavior | Named source, faults, tests and actual traces | Seven-predicate release challenge; separate local closure tests and cold-process trials. |
| Comparative differentiation | Same contract, targets, faults, budgets and competent alternative configuration | NOT_ASSESSED. No competitor was run. |
The larger question is how much avoidable reconstruction a human must provide after handoff. Zero intervention with no progress fails that question. Harness assistance cannot disappear from the denominator. The burden specification makes those rules explicit.
A comparison that can defeat the claim
Configure Temporal, Restate or DBOS using its recommended durable patterns, with application authority, target reconciliation and return rules. Give both applications the same authorized obligations, local effect semantics, failures, budgets, stop conditions and evidence. Separately count setup code/configuration, errors, useful progress, assistance, human reconstruction and auditability. Do not use Camden terminology as a required interface.
If that application meets the same contract with comparable burden, withdraw exclusivity claims. A smaller packaged policy model or clearer evidence could remain useful, but needs its own evidence. The deliberately naive fresh-identity retry is a teaching control, never that comparison.
Public, private and proposed
The released package has no model calls, remote effect adapter or background service. The private Camden installation is a different system whose asserted capabilities are not public-package proof. The larger gauntlet is a specification with explicit unsupported rows, not a hidden list of completed capabilities.