Decide what happens to DefaultPersonas() (archie, helpful, concise, technical, creative, teacher) and the /personality command once SOUL owns identity. Options: SOUL replaces the default archie persona and the rest remain selectable style modifiers; or personas become seed templates a user copies into their SOUL; or personas are retired. Currently GetActive composes the baseline archie prompt with the selected persona, so the interaction with SOUL must be explicit rather than emergent.
Acceptance Criteria
Precedence between SOUL and a selected persona is defined and documented. /personality either keeps working with stated semantics or is removed deliberately. No path lets a persona selection blank out the user's SOUL without them asking.
Notes
Not resolved yet. docs/architecture/identity.md (Three-layer identity model, agreed 2026-07-30) documents SOUL as Layer 2 and explains why SOUL comes first, but does not state the specific precedence rule between SOUL and a /personality selection that this issue's acceptance criteria requires. /personality is still fully live and unmodified: internal/channels/telegram/personality.go, internal/gateway/gateway.go:375,472,507. DefaultPersonas() still lives in internal/gateway/persona.go with no SOUL reference. This is a real open design decision, not a documentation-only task -- read docs/architecture/identity.md's three-layer model first, then decide (and document) precedence.
Close reason
Answered by docs/prds/soul.md (Persona removal gate): SOUL replaces the PersonaRegistry baseline, per-session personality switching disappears, the style catalogue is not retained, and the persona wire/page/commands are removed under archie-core-7ftt. No residual reconciliation question remains open.
Imported from beads archie-core-1786637500130-394-584ce317 · GitHub #415 · type task · priority P2 · created 2026-08-08 · closed 2026-09-29
Decide what happens to DefaultPersonas() (archie, helpful, concise, technical, creative, teacher) and the /personality command once SOUL owns identity. Options: SOUL replaces the default archie persona and the rest remain selectable style modifiers; or personas become seed templates a user copies into their SOUL; or personas are retired. Currently GetActive composes the baseline archie prompt with the selected persona, so the interaction with SOUL must be explicit rather than emergent.
### Acceptance Criteria
Precedence between SOUL and a selected persona is defined and documented. /personality either keeps working with stated semantics or is removed deliberately. No path lets a persona selection blank out the user's SOUL without them asking.
### Notes
Not resolved yet. docs/architecture/identity.md (Three-layer identity model, agreed 2026-07-30) documents SOUL as Layer 2 and explains why SOUL comes first, but does not state the specific precedence rule between SOUL and a /personality selection that this issue's acceptance criteria requires. /personality is still fully live and unmodified: internal/channels/telegram/personality.go, internal/gateway/gateway.go:375,472,507. DefaultPersonas() still lives in internal/gateway/persona.go with no SOUL reference. This is a real open design decision, not a documentation-only task -- read docs/architecture/identity.md's three-layer model first, then decide (and document) precedence.
### Close reason
Answered by docs/prds/soul.md (Persona removal gate): SOUL replaces the PersonaRegistry baseline, per-session personality switching disappears, the style catalogue is not retained, and the persona wire/page/commands are removed under archie-core-7ftt. No residual reconciliation question remains open.
---
_Imported from beads `archie-core-1786637500130-394-584ce317` · GitHub #415 · type task · priority P2 · created 2026-08-08 · closed 2026-09-29_
sam
added the mediumtask labels 2026-10-27 13:38:18 +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.
Decide what happens to DefaultPersonas() (archie, helpful, concise, technical, creative, teacher) and the /personality command once SOUL owns identity. Options: SOUL replaces the default archie persona and the rest remain selectable style modifiers; or personas become seed templates a user copies into their SOUL; or personas are retired. Currently GetActive composes the baseline archie prompt with the selected persona, so the interaction with SOUL must be explicit rather than emergent.
Acceptance Criteria
Precedence between SOUL and a selected persona is defined and documented. /personality either keeps working with stated semantics or is removed deliberately. No path lets a persona selection blank out the user's SOUL without them asking.
Notes
Not resolved yet. docs/architecture/identity.md (Three-layer identity model, agreed 2026-07-30) documents SOUL as Layer 2 and explains why SOUL comes first, but does not state the specific precedence rule between SOUL and a /personality selection that this issue's acceptance criteria requires. /personality is still fully live and unmodified: internal/channels/telegram/personality.go, internal/gateway/gateway.go:375,472,507. DefaultPersonas() still lives in internal/gateway/persona.go with no SOUL reference. This is a real open design decision, not a documentation-only task -- read docs/architecture/identity.md's three-layer model first, then decide (and document) precedence.
Close reason
Answered by docs/prds/soul.md (Persona removal gate): SOUL replaces the PersonaRegistry baseline, per-session personality switching disappears, the style catalogue is not retained, and the persona wire/page/commands are removed under archie-core-7ftt. No residual reconciliation question remains open.
Imported from beads
archie-core-1786637500130-394-584ce317· GitHub #415 · type task · priority P2 · created 2026-08-08 · closed 2026-09-29