feat: add generated scene skill platform hardening
This commit is contained in:
@@ -0,0 +1,74 @@
|
||||
# Promotion And Board Reconciliation Policy Report
|
||||
|
||||
Date: 2026-04-19
|
||||
|
||||
Parent framework: `2026-04-19-scene-skill-102-full-coverage-framework-plan`
|
||||
|
||||
Parent route: `Route 6 / promotion and board reconciliation`
|
||||
|
||||
Plan: `2026-04-19-promotion-and-board-reconciliation-policy-plan.md`
|
||||
|
||||
## Scope
|
||||
|
||||
This is a policy-only route. It defines how later reconciliation may update official scene-state assets.
|
||||
|
||||
This route did not:
|
||||
|
||||
- modify `src/generated_scene/analyzer.rs`
|
||||
- modify `src/generated_scene/generator.rs`
|
||||
- update `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
||||
- promote any scene
|
||||
|
||||
## Policy Inputs
|
||||
|
||||
The policy covers these status inputs:
|
||||
|
||||
- `auto-pass`
|
||||
- `fail-closed-known`
|
||||
- `adjudicated-valid-host-bridge`
|
||||
- `timeout-as-pass-candidate`
|
||||
- `timeout-as-fail-closed-candidate`
|
||||
- `timeout-still-unreadable`
|
||||
- `timeout-rerun-error`
|
||||
|
||||
## Promotion Thresholds
|
||||
|
||||
| Input status | Candidate board status | Auto-update board |
|
||||
| --- | --- | --- |
|
||||
| `auto-pass` | `framework-auto-pass-candidate` | no |
|
||||
| `fail-closed-known` | `framework-structured-fail-closed` | no |
|
||||
| `adjudicated-valid-host-bridge` | `framework-valid-host-bridge` | no |
|
||||
| `timeout-as-pass-candidate` | `hygiene-pass-candidate` | no |
|
||||
| `timeout-as-fail-closed-candidate` | `hygiene-fail-closed-candidate` | no |
|
||||
|
||||
## Board Update Rules
|
||||
|
||||
1. Diagnostic reruns, hygiene interpretations, and route-local follow-ups cannot directly update the official execution board.
|
||||
2. Board changes require a dedicated reconciliation plan that names source assets and target statuses.
|
||||
3. Pass-like promotion requires complete generation evidence under the agreed sweep or validation budget.
|
||||
4. Structured fail-closed is framework-supported coverage, not execution pass.
|
||||
5. Adjudicated host-bridge scenes remain host-bridge classified unless a later implementation closes their original expected contract.
|
||||
|
||||
## Timeout Hygiene Representation
|
||||
|
||||
Raw `source-unreadable` status must be preserved. A hygiene-aware status can be published alongside it:
|
||||
|
||||
- `timeout-as-pass-candidate`
|
||||
- `timeout-as-fail-closed-candidate`
|
||||
- `timeout-still-unreadable`
|
||||
- `timeout-rerun-error`
|
||||
|
||||
## Structured Fail-Closed Representation
|
||||
|
||||
Structured fail-closed is recognized framework coverage when:
|
||||
|
||||
- a generation report exists
|
||||
- the blocker is named
|
||||
- missing pieces or failed gates are recorded
|
||||
- a diagnostic payload such as `contractSnapshot` is available
|
||||
|
||||
It is not an execution pass.
|
||||
|
||||
## Stop Statement
|
||||
|
||||
Route 6 policy is published. Do not update the execution board under this plan.
|
||||
Reference in New Issue
Block a user