Skip to content

Slice: persona-freeze precedence sentence in Orchestrator prompt #328

Closed

Description

@DoodleBears

Parent

#324

What to build

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.
  • Existing prompt-section tests cover the addition.
  • No other prompt bytes change.

Blocked by

None (can start immediately).

Activity

  1. added
    ready-for-agentFully specified, ready for an AFK agent
    area:backendHost-side implementation
    feature:memoryPersonaBot Memory Repository and Memory Service
    scope:tracerHuman-testable implementation slice
    on Sep 26, 2026
  2. DoodleBears commented on Sep 26, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: opencode (interactive session, not a DSH Session)
    • Task: opencode/local/2026-09-26-memory-slices
    • Issue scope: persona-freeze precedence sentence in Orchestrator prompt
    • Worktree: current checkout, uncommitted, no PR yet
    • Started: 2026-09-26
    • State: active
  3. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 26, 2026
  4. DoodleBears commented on Sep 26, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome

    • Agent: opencode (interactive session) · Task: opencode/local/2026-09-26-memory-slices
    • 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.
    • Remaining: review, PR.
  5. removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Sep 26, 2026
  6. DoodleBears commented on Sep 26, 2026

    @DoodleBears
    ContributorAuthor

    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:

    freeze evidence

    • 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.

  7. DoodleBears commented on Sep 26, 2026

    @DoodleBears
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:backendHost-side implementationfeature:memoryPersonaBot Memory Repository and Memory Serviceready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions