Write the provider blueprint

docs/providers.md collects the provider contract that was spread across
comments, callers and per-provider docs: MUST/SHOULD/MAY rules per method,
each tied to the reconciler or GC behaviour it protects, the error taxonomy,
a feature matrix for kubernetes/gcp/kvm with file:line notes, a checklist for
adding a provider, and the known gaps. Linked from architecture.md and
CLAUDE.md.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-09-16 08:54:40 +00:00
co-authored by Claude Opus 5
parent cacd9583a3
commit d96e56f1a0
4 changed files with 595 additions and 4 deletions
+4 -3
View File
@@ -27,9 +27,10 @@ entrypoint yet, so there's nothing to run locally.
Documented in [docs/architecture.md](docs/architecture.md). It holds the component
table, the reconcile flow, and one section per runnable: health engine, discovery and
lease API, orphan GC, metrics, tracing, and provider health checks. Provider-specific
detail is in `docs/kvm-provider.md` and the GCP docs; the test layout is in
`docs/testing.md`.
lease API, orphan GC, metrics, tracing, and provider health checks. The provider
contract (MUST/SHOULD rules, feature matrix, checklist for adding a provider, known
gaps) is in [docs/providers.md](docs/providers.md). Provider-specific detail is in
`docs/kvm-provider.md` and the GCP docs; the test layout is in `docs/testing.md`.
## Conventions