Document NPC semantic normalization
This commit is contained in:
@@ -86,6 +86,22 @@ workflow intentionally crosses a process or session boundary. Those files are
|
||||
validated against the consumer slot and must be protected as sensitive
|
||||
campaign data. They are not part of the maintained ordered handoff workflow.
|
||||
|
||||
### NPC Semantic Normalization
|
||||
|
||||
Before the first step can release its accepted NPC artifact across the ordered
|
||||
generated-reference barrier, `dnd/npcs` performs one document-level semantic
|
||||
normalization call for each configured normalize attempt when eligible distinct
|
||||
names remain. The normalize binding's `retries` setting controls additional
|
||||
attempts. If an invalid or unsafe identity proposal exhausts that budget, the
|
||||
run safely accepts the deterministic and any independently safe partial
|
||||
consolidation, with a bounded warning; ordinary validation still applies before
|
||||
the artifact can cross the barrier.
|
||||
|
||||
An accepted normalized NPC checkpoint can be reused on `--resume` just like
|
||||
other accepted normalize work. A changed normalization prompt, response schema,
|
||||
or policy identity produces a cold cache miss, so the current reconciliation is
|
||||
recomputed rather than silently reusing incompatible state.
|
||||
|
||||
## Chunk-Plan Cache
|
||||
|
||||
Chunk plans are stored at:
|
||||
|
||||
Reference in New Issue
Block a user