Feature Store · View 06 of 21 · Structure
Decisions
- Definition sits below materialisation deliberately. If materialisation read the registry live, a definition edit would silently change values mid-run.
- Observability is a layer, not a sidecar: freshness SLOs, skew replay and drift attribution are how the platform proves its central claim.
- The client SDK may cache immutable metadata and never feature values. A cached value is an undetectable staleness bug.
Assumptions
- Compiled plans are cached locally by the serving tier, which is what lets serving survive 60 minutes of registry unavailability.
Deliberately omitted
- Six of the fourteen inter-layer edges are drawn; the rest would restate what the layer order already says.
