60 lines
2.7 KiB
Markdown
60 lines
2.7 KiB
Markdown
# Scene Skill 102 Deterministic Invocation Readiness Design
|
|
|
|
> Date: 2026-04-20
|
|
> Parent Asset: `examples/scene_skill_102_final_materialization_2026-04-19`
|
|
|
|
## Intent
|
|
|
|
Prepare the final materialized scene skills for deterministic natural-language invocation through sgClaw.
|
|
|
|
This design addresses the gap between a generated skill package and a deterministic callable scene skill. The sgClaw runtime already has a registry-backed deterministic dispatch path for instructions ending with `。。。`, but the final materialized `scene.toml` files are not yet normalized for that convention.
|
|
|
|
## Current Findings
|
|
|
|
1. `101 / 102` scenes have complete skill packages and `scene.toml`.
|
|
2. `1 / 102` scene, `sweep-012-scene / 业扩报装管理制度`, is still a materialization failure.
|
|
3. `0 / 101` complete generated scene manifests currently use the deterministic suffix `。。。`.
|
|
4. `101 / 101` complete generated scene manifests currently use exactly one include keyword, usually the full scene name.
|
|
5. `10 / 101` complete generated scene manifests currently define runtime-supported params.
|
|
|
|
## Scope
|
|
|
|
Allowed:
|
|
|
|
1. Analyze deterministic invocation readiness for the complete final skill set.
|
|
2. Normalize `scene.toml` deterministic metadata for complete packages.
|
|
3. Generate invocation samples and dispatch dry-run evidence.
|
|
4. Publish readiness assets and reports.
|
|
|
|
Forbidden:
|
|
|
|
1. Do not execute browser scripts.
|
|
2. Do not change generated JavaScript scripts.
|
|
3. Do not modify sgClaw runtime dispatch code unless a later dedicated implementation plan is created.
|
|
4. Do not repair `sweep-012-scene`.
|
|
5. Do not start static, mock, or production validation.
|
|
6. Do not rename skill directories.
|
|
|
|
## Readiness Model
|
|
|
|
A skill is deterministic-invocation-ready when:
|
|
|
|
1. it has a valid `scene.toml`;
|
|
2. `[deterministic].suffix = "。。。"`;
|
|
3. `include_keywords` can match at least the readable scene name;
|
|
4. the scene can be uniquely selected by dispatch dry-run using an expected invocation sample;
|
|
5. required params either resolve or produce a structured prompt.
|
|
|
|
## Expected Outputs
|
|
|
|
1. `tests/fixtures/generated_scene/scene_skill_102_deterministic_invocation_readiness_2026-04-20.json`
|
|
2. `tests/fixtures/generated_scene/scene_skill_102_deterministic_invocation_samples_2026-04-20.json`
|
|
3. `docs/superpowers/reports/2026-04-20-scene-skill-102-deterministic-invocation-readiness-report.md`
|
|
|
|
## Completion Criteria
|
|
|
|
1. All 101 complete packages have deterministic suffix normalized to `。。。`.
|
|
2. Dispatch dry-run results are available for all complete packages.
|
|
3. The failed `sweep-012-scene` remains explicitly excluded and listed as not ready.
|
|
4. No browser execution or production validation is performed.
|