Role, namespace, and credential isolation #807

New Issue

2026-07-22T05:33:11-05:00

jcwalker3 commented

2026-07-22 05:33:11 -05:00

Objective

Enforce role, namespace, and credential isolation for multi-LLM workers.

Acceptance criteria

Enforce author, reviewer, merger, reconciler, cleanup, and intake boundaries.
Derive permitted namespace/profile from the selected role.
Author workers require an existing open routed issue.
Issue creation remains a separate intake workflow.
Wrong-role and ambiguous-ownership operations fail closed.
Credentials never enter prompts, browser responses, logs, command lines, or LLM subprocess environments.
Includes adversarial security tests.

Parent Epic

Parent: #797

Issue-First & Safety Requirements

Implementation may begin only from an existing open issue.
Author implementation requires canonical routing, a durable issue lock, and a validated author worktree.
Read-after-write verification is required for all mutations.
Wrong-role and ambiguous-ownership operations fail closed.

## Objective Enforce role, namespace, and credential isolation for multi-LLM workers. ## Acceptance criteria - Enforce author, reviewer, merger, reconciler, cleanup, and intake boundaries. - Derive permitted namespace/profile from the selected role. - Author workers require an existing open routed issue. - Issue creation remains a separate intake workflow. - Wrong-role and ambiguous-ownership operations fail closed. - Credentials never enter prompts, browser responses, logs, command lines, or LLM subprocess environments. - Includes adversarial security tests. ## Parent Epic Parent: #797 ## Issue-First & Safety Requirements - Implementation may begin only from an existing open issue. - Author implementation requires canonical routing, a durable issue lock, and a validated author worktree. - Read-after-write verification is required for all mutations. - Wrong-role and ambiguous-ownership operations fail closed.

jcwalker3 referenced this issue

2026-07-22 06:11:34 -05:00

feat(webui): worker registry and configuration schema (Closes #798) #810

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#807