generated from coulomb/repo-seed
tegwick
8528005bdb
Close the dangling MVP pilots task with H1 provider-switch test, pilot validation report, and resolver tenant-override fix. Add credential routing guidance to AGENTS.md and Claude rules.
2.4 KiB
2.4 KiB
MVP Pilot Validation Report (FEATURE-WP-0003-T06)
Date: 2026-06-19
Pilot: docs/pilots/mvp_pilot.py
Tests: tests/test_registry_resolver.py, tests/test_sdk_wrapper.py (incl. UC-H1)
Scope
End-to-end validation of the WP-0003 MVP against the scored UseCaseCatalog MVP selection.
Use cases exercised
| UC | Description | Result |
|---|---|---|
| UC-G1 | Register with lifecycle | Pass — registry validates owner, temp review_date |
| UC-A1/A2 | Adopt with wrapper + local provider | Pass — thin client + LocalProvider, no backend |
| UC-C1 | Tenant enable | Pass — tenant.preview scoped to acme vs globex |
| UC-D3 | Agent capability | Pass — agent.extract evaluated with agent context |
| UC-E1 | Compute disable per tenant | Pass — compute.heavy_ocr disabled for tenant |
| UC-E4 | Emergency kill switch | Pass — kill signal overrides tenant/default at runtime |
| UC-G3 | Explain decision | Pass — client.explain() returns reason/source/scope |
| UC-H1 | Provider switch | Pass — test_h1_provider_switch_without_business_code_change |
Observations
- Adoption effort: Single-script pilot; a consuming repo can integrate in one small task using the SDK + LocalProvider pattern (aligns with UC-A1 scoring).
- Explainability: Decisions include
reason,source,scope— sufficient for MVP governance (UC-G3). - Runtime control: Kill switch and tenant overrides applied without redeploy (local values mutated in-process).
- Compute savings: Pilot demonstrates disable path; real savings measurement deferred to production adapter work.
- Canon alignment: Evaluation uses tenant/agent context dimensions consistent with
docs/canon-mapping.md(EvaluationScope).
Fit vs scored catalog
The MVP UCs selected in WP-0003 (A1, C1, D3, E1, E4, G1, G3, H1) are all demonstrated. Deferred items from the catalog remain appropriate for follow-on work:
- Full tenant self-service (higher cost/risk)
- Experimentation analytics
- Complex approval workflows
- Production backend adapters (Unleash/Flagsmith/flagd)
No catalog adjustments required for the MVP boundary.
Ready for next workplan
Pilot and automated tests satisfy T06 acceptance. Recommended follow-ons (per WP-0004 Production Hardening section):
- Real OpenFeature provider adapters
- Entitlement signal integration depth
- SDK packaging (PyPI) and multi-language examples
- Adoption validation in a real consuming repository