Skip to content

fix(fabricator): require an architect or admin role to request fabrication - #170

Merged
gibbsie merged 1 commit into
mainfrom
fix/fabricator-request-role-gate
Sep 18, 2026
Merged

gibbsie merged 1 commit into
mainfrom
fix/fabricator-request-role-gate

Conversation

@gibbsie

@gibbsie gibbsie commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • requestAgentCreation / requestToolCreation require the architect or admin role (after the required-organisation check, before any SQS send), matching agent-code and import mutations.
  • Replaces the in-code "tenancy-only, no role gate" note with the re-ratified decision.

Follow-up to finding fac16c02 (#167).

Behaviour change

  • Org members without architect/admin can no longer start fabrication from the Create Agent / Create Tool / Integration Tool / DataStore Tool / Data Pipeline wizards. The wizards have no client-side role check yet, so they will surface the resolver's error text.

Verification

  • backend jest: 8095 passed, tsc clean; 5 new tests (reject non-architect before SQS, architect passes, admin passes, missing org still rejected first)

…ation

requestAgentCreation and requestToolCreation now refuse callers that hold
neither the architect nor the admin role, after the existing required
organisation check and before anything is sent to the fabricator queue.
Triggering fabrication drives model spend and creates agent records, so
it is gated like the agent-code and import mutations. Supersedes the
earlier in-code tenancy-only decision.
@gibbsie
gibbsie merged commit 1bc4597 into main Sep 18, 2026
15 checks passed
@gibbsie
gibbsie deleted the fix/fabricator-request-role-gate branch September 18, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant