37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
# Sprint 74 Plan: Financial and Compliance Semantics Pack
|
|
|
|
## Context
|
|
|
|
Regulated domains require traceability, deterministic behavior, and policy-aware
|
|
compliance reporting. Sprint 74 adds financial/compliance semantics.
|
|
|
|
---
|
|
|
|
## Goals
|
|
|
|
1. Model financial precision and ledger consistency semantics
|
|
2. Add compliance policy hooks and audit trails
|
|
3. Preserve deterministic rounding and transaction intent
|
|
4. Produce regulator-ready migration evidence bundles
|
|
|
|
---
|
|
|
|
## Steps
|
|
|
|
### Step 969: Financial precision/rounding canonical model (12 tests)
|
|
### Step 970: Ledger invariants packet schema (10 tests)
|
|
### Step 971: Compliance policy binding engine (10 tests)
|
|
### Step 972: Deterministic transaction replay verifier (10 tests)
|
|
### Step 973: Audit trail completeness checker (10 tests)
|
|
### Step 974: Compliance gate integration with support tiers (8 tests)
|
|
### Step 975: `whetstone_verify_financial_migration` MCP tool (8 tests)
|
|
### Step 976: `whetstone_get_compliance_evidence` MCP tool (8 tests)
|
|
### Step 977: Regulated-domain migration report template (8 tests)
|
|
### Step 978: Sprint 74 integration summary + regression (8 tests)
|
|
|
|
---
|
|
|
|
## Compliance Rule
|
|
|
|
- Missing audit evidence downgrades pair to non-stable status.
|