docs/architecture/configuration.md:160 already states the position: ChatConfig
holds "separate channel instance settings... there is no chat-wide settings
owner". The config section name has not followed, so a settings block named for
a product surface owns what the architecture calls channel state.
Two candidates, neither settled: [channel.] and [messaging.channel.]. The
second reads as a domain path, and no config section in this repo is currently
named after a domain package, so adopting it sets a precedent for every other
section rather than fixing one name.
This needs a maintainer decision, not evidence. Recorded as an OPEN entry in
docs/architecture/migration-decisions.md.
Operator-visible TOML break, so it should land with the internal/config
dissolution recorded in that same register, not on its own.
Close reason
Closed on GitHub; syncing bead state
Imported from beads archie-core-w46s · GitHub #863 · type task · priority P2 · created 2026-09-18 · closed 2026-09-26
docs/architecture/configuration.md:160 already states the position: ChatConfig
holds "separate channel instance settings... there is no chat-wide settings
owner". The config section name has not followed, so a settings block named for
a product surface owns what the architecture calls channel state.
Two candidates, neither settled: [channel.*] and [messaging.channel.*]. The
second reads as a domain path, and no config section in this repo is currently
named after a domain package, so adopting it sets a precedent for every other
section rather than fixing one name.
This needs a maintainer decision, not evidence. Recorded as an OPEN entry in
docs/architecture/migration-decisions.md.
Operator-visible TOML break, so it should land with the internal/config
dissolution recorded in that same register, not on its own.
### Close reason
Closed on GitHub; syncing bead state
---
_Imported from beads `archie-core-w46s` · GitHub #863 · type task · priority P2 · created 2026-09-18 · closed 2026-09-26_
sam
added the taskmedium labels 2026-10-27 13:41:12 +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.
docs/architecture/configuration.md:160 already states the position: ChatConfig
holds "separate channel instance settings... there is no chat-wide settings
owner". The config section name has not followed, so a settings block named for
a product surface owns what the architecture calls channel state.
Two candidates, neither settled: [channel.] and [messaging.channel.]. The
second reads as a domain path, and no config section in this repo is currently
named after a domain package, so adopting it sets a precedent for every other
section rather than fixing one name.
This needs a maintainer decision, not evidence. Recorded as an OPEN entry in
docs/architecture/migration-decisions.md.
Operator-visible TOML break, so it should land with the internal/config
dissolution recorded in that same register, not on its own.
Close reason
Closed on GitHub; syncing bead state
Imported from beads
archie-core-w46s· GitHub #863 · type task · priority P2 · created 2026-09-18 · closed 2026-09-26