Tighten documentation drift guardrail

This commit is contained in:
Meta Vens 2026-05-01 19:23:24 +01:00
commit ed971842ca
2 changed files with 8 additions and 6 deletions

View file

@ -112,4 +112,8 @@ When the user says to prepare for imminent compaction:
- Before handoff, compaction, or phase boundaries, sync `state/map.yaml`, add
distilled evidence when the lesson changes future belief, refresh
`notes/fresh-workspace-handoff.md`, and make the next action explicit.
- In documentation, describe the live system and current rule directly. Do not
write victory laps, scar tours, or clever autopsies about what the project no
longer does. If rejected history matters, keep it short, explicit, and
decision-relevant; otherwise cut it. The docs are not a trophy case for
yesterday's wrong machine.

View file

@ -35,11 +35,9 @@ This means the agent is not generally high in the variable, the baseline is not
very easy to change, but the variable is strongly activated right now.
Translation: this is a situation, not a personality transplant.
Canonical character state does not include `certainty`. If Ghostlight is
defining a character, uncertainty about that definition is not part of the
character. It belongs in workflow provenance, drafts, imported-source notes, or
review status. Otherwise the schema confuses the person with our confidence in
our paperwork, which is how bureaucracies get haunted.
Canonical character state does not include `certainty`. If a generated or
imported profile is provisional, track that in workflow provenance, draft
status, imported-source notes, or review status.
Perceived or inferred state can use `confidence`, because that is explicitly
about an observer's or classifier's read: