oikos phase 0: ontology + inventory + policy seeds, OpenAPI contract, ADRs

- seeds/ontology.yaml: 59 entity types (5 abstract, is-a hierarchy), 46
  relationship types with cardinality, 6 lifecycles with terminal states
  and named precondition checks
- seeds/inventory.yaml: 110 entities / 142 relationships translated from
  legacy inventory.yaml (fleet, services, ingress, storage, governance,
  archaeology); thin spots marked for backfill
- seeds/policy.yaml: 4 risk classes, 27 approval rules (hierarchy-aware,
  per-entity overrides), autonomy kill-switch off (cold start)
- api/openapi.yaml: full v1 REST contract (40 paths), RFC 9457 errors,
  cursor pagination, idempotency, ETag/If-Match, scopes; redocly-clean
- docs/adr/0001-0010: initial architecture decision records
- scripts/validate-seeds.py: Phase 0 gate — hierarchy, lifecycles,
  endpoints, cardinality, policy cross-refs (0 errors)
- plan: layer CHECK gains 'meta' (root type), cardinality gains
  'many-to-one'

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/adr/0010-infisical-with-sops-fallback.md

@@ -0,0 +1,20 @@
+# ADR 0010 — Infisical secrets with SOPS DR fallback
+
+Status: accepted (2026-07-07) · Plan: rev 3, Phase 5 (resolves audit S9)
+
+## Context
+SOPS+age is file-based: no runtime API, no machine identities, no
+rotation tracking, and every consumer needs the age key.
+
+## Decision
+Infisical in the Docker stack; services fetch via machine identities;
+secrets never in env files or plain config (config hierarchy: defaults →
+file → env → Infisical, secrets only). Bootstrap root of trust: Infisical
+master key in the mac-mini Keychain, backed up offline. One age key is
+retained and all secrets are exported to a SOPS-encrypted fallback file
+until an Infisical restore drill has passed; the fallback is refreshed on
+rotation.
+
+## Consequences
+- Chicken-and-egg is explicit: the Keychain + offline copy are the root.
+- SOPS retirement is gated on a passed restore drill, not on the calendar.