The maintainer's ruling (2026-09-29): personas were a misinterpretation of a requirement he raised -- an agent misunderstood what he meant. What he actually wanted was the identity feature, which landed later: an identity for every action, with an agent tied to a Workflow, Org, Kind and Agent so everything is auditable. SOUL is meant to be the chat personality.
Personas are therefore superseded twice over: SOUL replaces them as the chat personality, and identity-per-action replaces them as the agent-identity mechanism. There is nothing to reconcile. The supersession rests on that axis difference, not on any claim that the persona work is stale or unfinished: the shipped set has six working entries.
WHAT ACTUALLY EXISTS (verified; correct the earlier description if you read it): agent.ShippedPersonas in internal/domain/agent/persona.go ships SIX entries -- "archie" as the baseline identity, then "helpful", "concise", "technical", "creative", "teacher" as communication styles. There is ONE source, not two: gateway.DefaultPersonas in internal/gateway/persona.go is a thin adapter over agent.ShippedPersonas, production wiring calls gateway.NewPersonaRegistry(nil) in internal/app/archied/gateway_runtime.go, and the live set arrives from the control-plane resource seeded by agent.ShippedPersonas in internal/app/controlplane/personas.go.
THE ONE REAL LOSS, to state rather than hide: PersonaRegistry.GetActive COMPOSES -- the baseline prompt is prepended to a selected style. SOUL replaces the baseline only, so per-session style switching disappears with the rest.
SEQUENCING -- this must NOT land before the SOUL personality exists.
SOUL has no loader in the tree today; the prompt side does exist. internal/gateway/templates/archie.md.tpl already renders a block, XML-escaped through the shared xml helper, placed before <instruction_precedence>, and guarded by TestBuildSystemPromptSoulCannotOverrideInvariants (internal/gateway/prompt_test.go). That block is currently fed by the Persona field of SystemPromptConfig (internal/gateway/prompt.go). Deleting personas before the loader exists would render that block empty and leave the chat prompt with no identity at all.
Prerequisites: the SOUL loader with per-turn reload and default fallback, plus the seed-a-default-SOUL bead. The design of record for the boundary is docs/architecture/identity.md, "Three-layer identity model". Honour that SOUL cannot override the prompt invariants.
internal/app/controlplane/personas.go -- PersonasKind = "personas", its document, validation and seed
internal/app/controlplane/client.go -- the Personas query and watch
internal/gateway/persona.go -- PersonaRegistry (its per-session active map, Replace, GetActive composition rule), DefaultPersonas, and the handlePersonality command; the Persona field and PersonaPromptSource in internal/gateway/turn.go and internal/gateway/prompt.go
internal/channels/telegram/personality.go and the personality callback branch in telegram.go
the chat wire: proto/gateway/v1/chat.proto fields personas = 7, active_personas = 8, personas_available = 11 -- regenerate the contracts
the dashboard: ui/src/settings/PersonasPage.vue, ui/src/settings/personas.ts, the /settings/personas route and its nav entry in ui/src/router/index.ts (the Settings root currently REDIRECTS to /settings/personas), ChatSettings.vue, ui/src/chat/state.ts, ui/src/stores/control-plane.ts, ui/src/lib/api.ts, ui/src/lib/nav.ts
regenerate ui/dist (LAW) and any schema or control-plane descriptors that name the kind
Read docs/development/frontend-ui.md and docs/development/control-plane.md before touching the webui and control-plane halves; AGENTS.md requires the area's dev-docs page to travel with the work.
Also decide, and state the choice: a live "personas" resource may exist in an operator's control plane. Prefer tolerating an orphaned resource over writing a migration for a kind nothing reads.
Tracker: the superseded persona beads and GitHub issues are being closed by the backlog sweep. This bead is only the code removal.
Close reason
Personas removed; SOUL is the only chat identity text.
Imported from beads archie-core-7ftt · GitHub #1343 · type task · priority P2 · created 2026-09-29 · closed 2026-10-15
The maintainer's ruling (2026-09-29): personas were a misinterpretation of a requirement he raised -- an agent misunderstood what he meant. What he actually wanted was the identity feature, which landed later: an identity for every action, with an agent tied to a Workflow, Org, Kind and Agent so everything is auditable. SOUL is meant to be the chat personality.
Personas are therefore superseded twice over: SOUL replaces them as the chat personality, and identity-per-action replaces them as the agent-identity mechanism. There is nothing to reconcile. The supersession rests on that axis difference, not on any claim that the persona work is stale or unfinished: the shipped set has six working entries.
WHAT ACTUALLY EXISTS (verified; correct the earlier description if you read it): agent.ShippedPersonas in internal/domain/agent/persona.go ships SIX entries -- "archie" as the baseline identity, then "helpful", "concise", "technical", "creative", "teacher" as communication styles. There is ONE source, not two: gateway.DefaultPersonas in internal/gateway/persona.go is a thin adapter over agent.ShippedPersonas, production wiring calls gateway.NewPersonaRegistry(nil) in internal/app/archied/gateway_runtime.go, and the live set arrives from the control-plane resource seeded by agent.ShippedPersonas in internal/app/controlplane/personas.go.
THE ONE REAL LOSS, to state rather than hide: PersonaRegistry.GetActive COMPOSES -- the baseline prompt is prepended to a selected style. SOUL replaces the baseline only, so per-session style switching disappears with the rest.
SEQUENCING -- this must NOT land before the SOUL personality exists.
SOUL has no loader in the tree today; the prompt side does exist. internal/gateway/templates/archie.md.tpl already renders a <soul purpose="identity_and_style" trust="data"> block, XML-escaped through the shared xml helper, placed before <instruction_precedence>, and guarded by TestBuildSystemPromptSoulCannotOverrideInvariants (internal/gateway/prompt_test.go). That block is currently fed by the Persona field of SystemPromptConfig (internal/gateway/prompt.go). Deleting personas before the loader exists would render that block empty and leave the chat prompt with no identity at all.
Prerequisites: the SOUL loader with per-turn reload and default fallback, plus the seed-a-default-SOUL bead. The design of record for the boundary is docs/architecture/identity.md, "Three-layer identity model". Honour that SOUL cannot override the prompt invariants.
SURFACE TO REMOVE (verified touchpoints):
- internal/domain/agent/persona.go -- Persona, PersonaCollection, Validate, ShippedPersonas (six entries), normalizePersonaName
- internal/app/controlplane/personas.go -- PersonasKind = "personas", its document, validation and seed
- internal/app/controlplane/client.go -- the Personas query and watch
- internal/gateway/persona.go -- PersonaRegistry (its per-session active map, Replace, GetActive composition rule), DefaultPersonas, and the handlePersonality command; the Persona field and PersonaPromptSource in internal/gateway/turn.go and internal/gateway/prompt.go
- internal/channels/telegram/personality.go and the personality callback branch in telegram.go
- the chat wire: proto/gateway/v1/chat.proto fields personas = 7, active_personas = 8, personas_available = 11 -- regenerate the contracts
- the dashboard: ui/src/settings/PersonasPage.vue, ui/src/settings/personas.ts, the /settings/personas route and its nav entry in ui/src/router/index.ts (the Settings root currently REDIRECTS to /settings/personas), ChatSettings.vue, ui/src/chat/state.ts, ui/src/stores/control-plane.ts, ui/src/lib/api.ts, ui/src/lib/nav.ts
- regenerate ui/dist (LAW) and any schema or control-plane descriptors that name the kind
Read docs/development/frontend-ui.md and docs/development/control-plane.md before touching the webui and control-plane halves; AGENTS.md requires the area's dev-docs page to travel with the work.
Also decide, and state the choice: a live "personas" resource may exist in an operator's control plane. Prefer tolerating an orphaned resource over writing a migration for a kind nothing reads.
Tracker: the superseded persona beads and GitHub issues are being closed by the backlog sweep. This bead is only the code removal.
### Close reason
Personas removed; SOUL is the only chat identity text.
---
_Imported from beads `archie-core-7ftt` · GitHub #1343 · type task · priority P2 · created 2026-09-29 · closed 2026-10-15_
sam
added the mediumtask labels 2026-10-27 13:39:06 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The maintainer's ruling (2026-09-29): personas were a misinterpretation of a requirement he raised -- an agent misunderstood what he meant. What he actually wanted was the identity feature, which landed later: an identity for every action, with an agent tied to a Workflow, Org, Kind and Agent so everything is auditable. SOUL is meant to be the chat personality.
Personas are therefore superseded twice over: SOUL replaces them as the chat personality, and identity-per-action replaces them as the agent-identity mechanism. There is nothing to reconcile. The supersession rests on that axis difference, not on any claim that the persona work is stale or unfinished: the shipped set has six working entries.
WHAT ACTUALLY EXISTS (verified; correct the earlier description if you read it): agent.ShippedPersonas in internal/domain/agent/persona.go ships SIX entries -- "archie" as the baseline identity, then "helpful", "concise", "technical", "creative", "teacher" as communication styles. There is ONE source, not two: gateway.DefaultPersonas in internal/gateway/persona.go is a thin adapter over agent.ShippedPersonas, production wiring calls gateway.NewPersonaRegistry(nil) in internal/app/archied/gateway_runtime.go, and the live set arrives from the control-plane resource seeded by agent.ShippedPersonas in internal/app/controlplane/personas.go.
THE ONE REAL LOSS, to state rather than hide: PersonaRegistry.GetActive COMPOSES -- the baseline prompt is prepended to a selected style. SOUL replaces the baseline only, so per-session style switching disappears with the rest.
SEQUENCING -- this must NOT land before the SOUL personality exists.
SOUL has no loader in the tree today; the prompt side does exist. internal/gateway/templates/archie.md.tpl already renders a block, XML-escaped through the shared xml helper, placed before <instruction_precedence>, and guarded by TestBuildSystemPromptSoulCannotOverrideInvariants (internal/gateway/prompt_test.go). That block is currently fed by the Persona field of SystemPromptConfig (internal/gateway/prompt.go). Deleting personas before the loader exists would render that block empty and leave the chat prompt with no identity at all.
Prerequisites: the SOUL loader with per-turn reload and default fallback, plus the seed-a-default-SOUL bead. The design of record for the boundary is docs/architecture/identity.md, "Three-layer identity model". Honour that SOUL cannot override the prompt invariants.
SURFACE TO REMOVE (verified touchpoints):
Read docs/development/frontend-ui.md and docs/development/control-plane.md before touching the webui and control-plane halves; AGENTS.md requires the area's dev-docs page to travel with the work.
Also decide, and state the choice: a live "personas" resource may exist in an operator's control plane. Prefer tolerating an orphaned resource over writing a migration for a kind nothing reads.
Tracker: the superseded persona beads and GitHub issues are being closed by the backlog sweep. This bead is only the code removal.
Close reason
Personas removed; SOUL is the only chat identity text.
Imported from beads
archie-core-7ftt· GitHub #1343 · type task · priority P2 · created 2026-09-29 · closed 2026-10-15