Case · DiggingBeagle record

KedgeFlow ties agent actions to exact permissions with single-use claims

A prototype enforced exact-action grants under concurrency, with one successful claim per allowance in 6,560 ledger attempts, but it did not prove end-to-end correctness against real targets.

Scope

Prototype with three etcd members and mock target, not deployed production authorization infrastructure.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
not established
Evidence
Grade B
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

The controller and mock-target evaluation concerns proposed enforcement and concurrency, not exploitation of a deployed service. Exactly-once downstream effects and policy intent remain outside its demonstrated boundary. Assessment uses the pinned Claims and source identities; public primary pages were not independently retrievable during this run. Impact remains unrated because field consequence or a comparable scoring rubric is not established.

Assessed Oct 15, 2026 using diggingbeagle.assessment/1.

At a glance

Claims & evidence

CLM-CP7-KEDGE-MOCKIts controlled 32-call gateway race produced one committed mock effect, while the study identified limitations for production crash recovery and distributed targets.supported

Basis: reported finding

Link to claim
CLM-CP7-KEDGE-LEDGERThe paper reports 6,560 concurrent ledger claims against 82 allowances with exactly one successful claim per allowance.supported

Basis: reported finding

Link to claim

Unknowns and contradictions

  • End-to-end exactly-once effects across real services are not established.
  • Unregistered action routes and incorrect policies remain possible.

Sources and citation

Material revision history

  1. Oct 15, 2026 · Canonical change recorded · new in release · revision 150