37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Sprint 69 Plan: Multi-Team Policy Federation and Tenant Isolation
|
|
|
|
## Context
|
|
|
|
Different teams require different risk tolerances and policies. Sprint 69 adds
|
|
federated policy support with strict tenant isolation.
|
|
|
|
---
|
|
|
|
## Goals
|
|
|
|
1. Support organization/team-scoped transpilation policies
|
|
2. Isolate metrics, decisions, and waivers by tenant
|
|
3. Allow shared adapters with tenant-specific gate policies
|
|
4. Preserve reproducibility under federated configurations
|
|
|
|
---
|
|
|
|
## Steps
|
|
|
|
### Step 919: Tenant-scoped policy model (12 tests)
|
|
### Step 920: Policy inheritance/override resolution engine (10 tests)
|
|
### Step 921: Tenant isolation guardrails for logs/artifacts (10 tests)
|
|
### Step 922: Tenant-scoped waiver/approval ledger (10 tests)
|
|
### Step 923: Cross-tenant adapter sharing contract (10 tests)
|
|
### Step 924: Federated reproducibility validator (8 tests)
|
|
### Step 925: `whetstone_set_tenant_policy` MCP tool (8 tests)
|
|
### Step 926: `whetstone_get_tenant_support_matrix` MCP tool (8 tests)
|
|
### Step 927: Federated governance report generator (8 tests)
|
|
### Step 928: Sprint 69 integration summary + regression (8 tests)
|
|
|
|
---
|
|
|
|
## Isolation Rule
|
|
|
|
- Tenant data/artifacts must never leak across policy scopes.
|