Orgs must not see another org's configuration or data. Chat sessions, control-plane resources and model usage are scoped by org. Not yet checked: tasks and their steps, logs and events, captured webhook events, EDA sources and playbooks, memory, schedules, presence and health detail, and dashboard listings built from any of these. For each surface, either scope it by the caller's org or document why it is instance-only and admin-gated. Done when each surface is scoped or gated, with one table-driven test per store showing that a second org cannot list or read the first org's rows.
Close reason
Audit done; /api/setup and /api/skills were the leaks and are now instance-only.
Imported from beads archie-core-mt9xo · GitHub #1580 · type task · priority P1 · created 2026-10-10 · closed 2026-10-10
Orgs must not see another org's configuration or data. Chat sessions, control-plane resources and model usage are scoped by org. Not yet checked: tasks and their steps, logs and events, captured webhook events, EDA sources and playbooks, memory, schedules, presence and health detail, and dashboard listings built from any of these. For each surface, either scope it by the caller's org or document why it is instance-only and admin-gated. Done when each surface is scoped or gated, with one table-driven test per store showing that a second org cannot list or read the first org's rows.
### Close reason
Audit done; /api/setup and /api/skills were the leaks and are now instance-only.
---
_Imported from beads `archie-core-mt9xo` · GitHub #1580 · type task · priority P1 · created 2026-10-10 · closed 2026-10-10_
sam
added the hightask labels 2026-10-27 13:40:27 +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.
Orgs must not see another org's configuration or data. Chat sessions, control-plane resources and model usage are scoped by org. Not yet checked: tasks and their steps, logs and events, captured webhook events, EDA sources and playbooks, memory, schedules, presence and health detail, and dashboard listings built from any of these. For each surface, either scope it by the caller's org or document why it is instance-only and admin-gated. Done when each surface is scoped or gated, with one table-driven test per store showing that a second org cannot list or read the first org's rows.
Close reason
Audit done; /api/setup and /api/skills were the leaks and are now instance-only.
Imported from beads
archie-core-mt9xo· GitHub #1580 · type task · priority P1 · created 2026-10-10 · closed 2026-10-10