Feature Store · View 18 of 21 · Operations
Decisions
- The loop only closes because every served value carries the definition version that produced it. Without that field, Observe produces a number and Attribute produces an argument.
- Attribute is a decision node, not a step: separating a changed world from a changed pipeline is the judgement the whole loop exists to support.
- Revision creates a new version and notifies pinned consumers. Retirement is refused while a production consumer remains.
Assumptions
- Nightly skew replay per onboarded model; skew tolerance ≤ 0.1% of sampled requests per feature.
- Lifecycle states: experimental → production → deprecated → retired.
Risks
- Nightly replay dates a regression to a day, not an hour. For a fast-moving regression at peak, the loop is too slow and the per-consumer health view is the only live signal.
