---
typeId: req
recordId: benac-stor-012
fields:
  title: Storage lease requests
  statement: Benac shall support machine-readable storage lease request records created
    by authenticated or locally scoped users, agents, tools, packages where authorized,
    or other clients. A storage lease request shall describe the requested storage
    descriptor or offer where applicable, requested operations, target blob CIDs or blob
    classes where known, data classes, byte limits, recipient principals, encryption
    requirements, retention expectations, cost constraints where applicable, evidence
    expectations, requested expiry, initiating actor, authentication context where
    applicable, and supporting evidence or justification where supplied. A storage lease
    request shall not itself authorize storage effects. Storage effects require an
    active storage lease, capability grant, Local Policy allowance, or other accepted
    authorization record.
  rationale: Agents and tools need a legible way to ask for bounded storage resources,
    but the kernel does not need to define an agent's storage-planning process. Lease
    requests let agents take small reviewable steps toward availability, backup,
    staging, or sharing without receiving ambient storage authority.
  verification: An agent or tool creates a storage lease request for encrypted backup of
    selected blob CIDs. No upload, pin, publication, retrieval of sensitive blobs,
    sharing, or staging effect occurs until a matching lease or grant exists. The
    resulting request, approval/denial, lease, storage effects, receipts, and
    diagnostics are attributable and inspectable.
  testable: true
  status: draft
  area: BENAC-STOR
  sourceDocument: /home/johnb/Downloads/benac_syrs_v0_4_integrated_authentication.md
  sourceVersion: v0.4
  sourceSections:
    - 10.11 Storage discovery, remote storage, and content availability
  order: 129
---
