30 lines
1004 B
Markdown
30 lines
1004 B
Markdown
# Sprint 208 Plan: Projection Constraint Enforcement II
|
|
|
|
## Context
|
|
Projection constraints need enforcement in generation and validation paths.
|
|
|
|
## Goals
|
|
1. Enforce forbidden API/runtime policies per target projection
|
|
2. Enforce resource budget declarations and threshold checks
|
|
3. Emit target-specific blocked reasons
|
|
|
|
## Steps
|
|
|
|
### Step 2079: Forbidden API policy checker (10 tests)
|
|
Block plans violating per-target forbidden API rules.
|
|
|
|
### Step 2080: Resource budget threshold checker (10 tests)
|
|
Validate target budgets (latency/memory/binary) against declared constraints.
|
|
|
|
### Step 2081: Target projection blocker taxonomy (8 tests)
|
|
Emit deterministic blocker classes for projection violations.
|
|
|
|
### Step 2082: Per-target projection validation report (8 tests)
|
|
Add target-level pass/fail breakdown into reports.
|
|
|
|
### Step 2083: Sprint 208 Integration Summary (8 tests)
|
|
Add `editor/src/Sprint208IntegrationSummary.h`.
|
|
|
|
## Architecture Gate
|
|
- Projection-violating plans cannot pass strict readiness.
|