Improve scene-aware combat gating
This commit is contained in:
@@ -611,12 +611,13 @@ references:
|
||||
lane: scene-descriptions
|
||||
```
|
||||
|
||||
When bound, the combat extractor and normalizer receive the generated registry
|
||||
at operation time. Framework provenance and checkpoint dependencies contain its
|
||||
kind, schema identity, media type, canonical digest, size, and bounded producer
|
||||
identity; names, content, and paths are not recorded there. When
|
||||
absent, the combat prompt receives the exact empty registry value
|
||||
`{"npcs":[]}` with its projection digest and no registry provenance.
|
||||
When `npcs` is bound, the combat extractor and normalizer receive the generated
|
||||
NPC registry at operation time. Framework provenance and checkpoint dependencies
|
||||
contain its kind, schema identity, media type, canonical digest, size, and
|
||||
bounded producer identity; names, content, and paths are not recorded there.
|
||||
When absent, the combat prompt receives the exact empty NPC registry value
|
||||
`{"npcs":[]}` with its projection digest and no registry provenance. The
|
||||
generated `scene_descriptions` artifact is supplied only to combat extraction.
|
||||
The complete example uses the same explicit scene binding; an external approved
|
||||
scene-description artifact may be used instead when the workflow crosses a
|
||||
process or session boundary.
|
||||
|
||||
Reference in New Issue
Block a user