# SECRETS-WP-0009-T03 — spend envelope for metered Glas runs

Blocking workplan: SECRETS-WP-0009
Blocking task: SECRETS-WP-0009-T03 (hub prefix f8069c8a)
Related: HFACT-WP-0001-T01/T04 (SpendPolicy and owner config), GLAS-WP-0012

## Question
Accept the spend envelope for metered Glas runs on the Anthropic key (EUR 5 per run, 20 per day, 500 total, until 2027-01-31)?

## One act
Accept this envelope as the spend authority for rein-aharness MessagesOwner
`metered-once` runs on railiance01 using the Anthropic key of catalog lane
`glas-claude-agent-dev-anthropic`. The accepted approval id becomes the
SpendPolicy `authority_ref` for envelope `hfact-glas-anthropic-2026-09`.

## Enforced values (rein-aharness SpendPolicy, decimal strings)

| Field | Value | Note |
| --- | --- | --- |
| `per_run_eur` | 5 | Operator-stated |
| `daily_eur` | 20 | Operator-stated; timezone Europe/Berlin |
| `total_eur` | 500 | Operator-stated; over the whole envelope |
| `eur_per_usd` | 0.87 | Operator rate 1 EUR = 1.15 USD (1/1.15 = 0.8696), rounded up |
| `max_liability_usd` | 5.74 | Per run. Reserves ceil(5.74 x 0.87) = EUR 4.9938, inside EUR 5 |
| `max_budget_usd` | 5.00 | Per run. Claude CLI stop threshold, inside liability |
| `valid_from` | acceptance time | |
| `expires_at` | 2027-01-31T23:59:59+01:00 | Operator-stated |

Resulting capacity: at most 4 runs per day and 100 runs in total. A completed run
is charged its full reservation, not its reported cost. A failed, cancelled or
unaccounted run keeps its reservation and blocks further runs until reconciled.
Cost above liability permanently marks the envelope breached.

The operator's overall USD 600 budget and USD 800 liability caps are dominated
by `total_eur` 500 (= USD 575) and need no separate field.

## Recorded, not enforced
- EUR 100 per calendar month. SpendPolicy has no monthly ceiling; a rein-aharness
  follow-up adds `monthly_eur`. Until then the operator reviews monthly use.

## Scope bound by the SpendPolicy, filled in before the private file is written
`worker_id`, `activity_definition_id`, `target_repo`, `project`, `profile_ref`,
`profile_sha256`, `descriptor_sha256`, `repository_grant_id`, `max_turns` come from
the admitted factory profile (HFACT-WP-0001-T01). They narrow this envelope; they
cannot widen the amounts above.

## Must not
- Deliver, read or display the Anthropic key
- Authorize the OpenBao apply, verify or exec actions (separate T03 approvals)
- Cover llm-connect or its DeepSeek default; that path is not this envelope
- Raise any amount or extend the expiry without a new memo