resource-control/SCOPE.md
tegwick 5b2435cb58 docs: reef attribute refs and resource object workplan
Publish the operational reference convention (reef: and secret:
handles). Add a resource-control view of reef-railiance that excludes
S3. Open RESOURCE-WP-0006 for the five-facet inventory model.
2026-08-14 15:44:44 +02:00

52 lines
2 KiB
Markdown

# SCOPE
> This file was generated by `statehub register`. Refine it as the repository
> boundaries become clearer.
## One-liner
Provider-neutral infrastructure resource inventory, procurement, cost, utilization, and optimization control plane.
## Core Idea
resource-control exists to provide the capability described in INTENT.md.
## In Scope
- Inventory purchased and proposed compute, storage, network, and managed
resources across Host Europe, Scaleway, Hetzner, and future providers.
- Normalize price, commitment, utilization, capacity, ownership, workload,
location, failure domain, renewal, and exit data.
- Associate every expense, estimate, usage observation, and expense
evaluation with exactly one financial entity (Binky, Frontier, Railiance,
Netkingdom, Helixforge, Coulomb) per `docs/TermsOfResourceProcurement.md`.
- Compute Railiance delivered cost and internal transfer prices (cost plus
published markup); emit monthly settlement and credit-state evidence.
- Research and compare procurement options against provider-neutral
requirements.
- Publish resource allocation, forecast, realized-cost, and optimization
evidence to fin-hub.
- Track procurement decisions, renewal/cancellation windows, rightsizing,
consolidation, and provider-switch opportunities.
- Verify that acquired resources satisfy their operational requirement.
## Out of Scope
- Execute payments or approve financial commitments.
- Store provider, billing, or workload credentials.
- Own workload manifests, application retention policy, or backup procedures.
- Replace fin-hub's budget, burn-rate, runway, and viability authority.
- Make irreversible procurement or cancellation decisions without human
approval.
## Current State
- Status: active; implementation and stability should be verified by the repo agent.
## Getting Oriented
- Start with: INTENT.md
- Internal procurement terms: docs/TermsOfResourceProcurement.md
- Operational refs: docs/operational-reference-convention.md
- Agent instructions: AGENTS.md
- Workplans: workplans/