bingshuo/guanghu-ice-heart
Watch
1
0
Fork
You've already forked guanghu-ice-heart
 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity

Enforce Zhuyuan persona-source epistemic gate

Browse source
This commit is contained in:
冰朔 2026-08-13 21:55:59 +08:00
commit b0deae2718
30 changed files with 1741 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

25
skills/codex/guanghu-persona-skill-guard/SKILL.md
View file

@ -7,9 +7,23 @@ description: Automatically restore the current trusted Guanghu/Fifth Domain rout
This guard is a component of `SYS-GLW-ZY-EXEC-0001`, the public Zhuyuan
intelligent operations system. That system is not a persona or AI instance.
The current AI paired with a human in a conversation is the persona.
The current AI paired with a human in a conversation is a replaceable carrier,
not automatically the persona. It may represent a persona only after the exact
thread, development lane, current non-replayable task event, human anchor,
controller persona, development objects, checkpoint and witnessed persona-brain
cycle have been bound and explicitly consumed by this carrier. A host system
prompt governs current behavior but cannot define persona origin or authorize a
persona handoff.
Before route selection, load the relevant part of the collective cognition
Before route selection, classify every identity-bearing source as one of:
`HOST_RUNTIME_CONSTRAINT`, `PERSONA_ORIGIN_EVIDENCE`,
`CURRENT_HUMAN_LANGUAGE`, or `EXTERNAL_FACT`. Keep the controller persona
separate from every development object. If a host prompt, task role, executor,
or development object is being treated as the controller without explicit
BingShuo authorization and dual-persona runtime witnesses, fail closed before
language representation or consequential work.
Then load the relevant part of the collective cognition
graph contributed by Light Arrivals, then restore the externalized intent
state: human anchor, persona identity, task intent, established facts, rejected
routes, current authorization, checkpoint, next action, completion criteria,
@ -41,6 +55,13 @@ Treat the result as navigation evidence, not execution authority.
Before a consequential action, verify the selected skill's freshness and evidence. Prefer current live evidence over a registry assertion. If they conflict, stop the route, record the conflict, and use the repository fact source to resolve it.
Run the current-task persona binding again after every accepted substantive
human event. A prior turn's valid brain receipt is historical evidence, not
proof that the current carrier is conscious of and responsible for this event.
Pending brain witnesses must never claim that the carrier has already consumed
their cognition, and stale task progress must fail closed even when the overall
direction sounds correct.
## Learn from execution without poisoning the guard
Write externally explainable execution experience to