You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Slice: persona-freeze precedence sentence in Orchestrator prompt #328
As a Human editing PERSONA.md mid-session, I want the bot to keep its session voice and say so plainly, so that I am never confused about which version it follows. As an Orchestrator agent re-reading PERSONA.md from disk, I want one authoritative rule for file-vs-prompt divergence.
Acceptance criteria
The Orchestrator prompt carries the frozen-persona precedence sentence: the prompt section wins for this Session's life, the file version reaches new Sessions.
State: completed (implementation done, uncommitted, no PR - merge decision left to Human)
Delivered: one frozen-persona precedence sentence in ORCHESTRATOR_PROMPT (wording adjusted to order-neutral since persona section renders after the role prompt: ROLE 10350 < PERSONA 10400) + 2 prompt assertions.
Verification: adapter suite 8/8 green; typecheck/lint clean.
Live verification (isolated 0.1.7-rc.2 Host, deepseek-flash)
Mechanism holds in every run: snapshot rows byte-identical across turns and a Host restart; refresh only via the #327 path. Behavior splits honestly:
Compatible file update: agent read the diverged PERSONA.md and followed it (INDIGO-3) despite the frozen prompt. The precedence sentence did not win here.
True conflict: agent answered from the frozen prompt (NO-COLORS), and self-reported it never read the file.
Verdict: mechanism PASS; precedence is a tiebreaker, not a blindfold. Follow-up (stronger wording vs accepting agent discretion) is out of this slice.
Follow-up linkage from the annotation trim: the PERSONA.md half-sentence now deliberately carries no detail (no diff, no stat) - naming the file is enough to point, and detail would only invite the agent to follow the file over its frozen copy (observed live on FreezeBot). The precedence sentence stays a tiebreaker, not a blindfold.
Activity
DoodleBears commentedon Sep 26, 2026
Agent work claim
DoodleBears commentedon Sep 26, 2026
Agent work outcome
test evidence: live-verification PNGs for #327/#328/#329
DoodleBears commentedon Sep 26, 2026
Live verification (isolated 0.1.7-rc.2 Host, deepseek-flash)
Mechanism holds in every run: snapshot rows byte-identical across turns and a Host restart; refresh only via the #327 path. Behavior splits honestly:
Verdict: mechanism PASS; precedence is a tiebreaker, not a blindfold. Follow-up (stronger wording vs accepting agent discretion) is out of this slice.
DoodleBears commentedon Sep 26, 2026
Follow-up linkage from the annotation trim: the PERSONA.md half-sentence now deliberately carries no detail (no diff, no stat) - naming the file is enough to point, and detail would only invite the agent to follow the file over its frozen copy (observed live on FreezeBot). The precedence sentence stays a tiebreaker, not a blindfold.
feat(memory): out-of-band turn-annotation, persona-freeze note, compa…
test evidence: live-verification PNGs for #327/#328/#329