95 lines
2.5 KiB
Markdown
95 lines
2.5 KiB
Markdown
# Generated Scene Source Evidence Cross-Scan Plan
|
|
|
|
> Date: 2026-04-20
|
|
> Status: Draft
|
|
> Parent roadmap:
|
|
> - `docs/superpowers/plans/2026-04-20-generated-scene-source-first-runtime-semantics-hardening-plan.md`
|
|
> Parent design:
|
|
> - `docs/superpowers/specs/2026-04-20-generated-scene-source-evidence-cross-scan-design.md`
|
|
|
|
## Goal
|
|
|
|
Perform a bounded source-first cross-scan over the original 102 scene directories so the project can identify which scenes share the same runtime-semantics risk family as `sweep-030-scene`.
|
|
|
|
This plan is analysis-only.
|
|
|
|
## Fixed Inputs
|
|
|
|
1. `tests/fixtures/generated_scene/scene_skill_102_final_materialization_manifest_2026-04-19.json`
|
|
2. `tests/fixtures/generated_scene/scene_execution_board_2026-04-18.json`
|
|
3. source root:
|
|
- `D:/desk/智能体资料/全量业务场景/一平台场景`
|
|
|
|
## Boundaries
|
|
|
|
Allowed:
|
|
|
|
1. map the current 102 scenes to original source directories
|
|
2. scan bounded source evidence
|
|
3. publish JSON inventory and report
|
|
|
|
Forbidden:
|
|
|
|
1. no edits in `src/`
|
|
2. no edits to generated skills
|
|
3. no rematerialization
|
|
4. no validation reruns
|
|
5. no execution board updates
|
|
|
|
## Phase 0: Freeze Scene Mapping
|
|
|
|
Tasks:
|
|
|
|
1. derive the exact 102-scene source directory mapping
|
|
2. validate that each scene maps to one source directory or an explicit missing record
|
|
|
|
Acceptance:
|
|
|
|
1. all 102 scenes have a source mapping status
|
|
|
|
## Phase 1: Run Bounded Source Evidence Scan
|
|
|
|
Tasks:
|
|
|
|
1. scan for alias evidence
|
|
2. scan for dictionary evidence
|
|
3. scan for default parameter evidence
|
|
4. scan for request mapping evidence
|
|
5. scan for runtime URL evidence
|
|
|
|
Acceptance:
|
|
|
|
1. each scene has evidence flags
|
|
2. representative evidence files are recorded where found
|
|
|
|
## Phase 2: Build Cross-Scan Ledger
|
|
|
|
Tasks:
|
|
|
|
1. write one record per scene
|
|
2. tag scenes with source-side risk hints
|
|
3. explicitly identify scenes that look similar to `sweep-030-scene`
|
|
|
|
Acceptance:
|
|
|
|
1. all 102 scenes appear in the ledger
|
|
2. the anchor case is clearly represented
|
|
|
|
## Phase 3: Publish Assets
|
|
|
|
Deliverables:
|
|
|
|
1. `tests/fixtures/generated_scene/generated_scene_source_evidence_cross_scan_2026-04-20.json`
|
|
2. `docs/superpowers/reports/2026-04-20-generated-scene-source-evidence-cross-scan-report.md`
|
|
|
|
Acceptance:
|
|
|
|
1. the JSON can be used as the next input to the runtime-semantics ledger stage
|
|
2. the report summarizes the five evidence families across the 102-scene set
|
|
|
|
## Stop Statement
|
|
|
|
Stop after publishing the JSON inventory and report.
|
|
|
|
Do not start rule-hardening or rematerialization in this plan.
|