Security
Built so an agent can't go rogue.
What Fixroom refuses to do is enforced in code, not left to a prompt. Here are the guardrails, the architecture behind them, and an honest list of what isn't built yet.
Guardrails
What it refuses to do, enforced in code.
A prompt is not a guarantee, and neither is a comment. These limits live in the code. Several are checked in tests that read the source.
Architecture
Everything runs on a server you control.
Your team works in the browser. The work that has to keep going runs on your server, even when nobody has the page open, and the browser only watches it. Two things leave: the model calls you configure, and a branch and pull request on GitHub, where a person merges.
People decideThe agent proposesYour server runs it
Fixroom · Sheet A-2 · Where everything stays · Business view, not to scale
Three ordering rules carry the guarantees
Roles are enforced on the server, and a route without a rule is refused, even for an owner. The roles are owner, admin, developer and reviewer. People join by single-use invite links that expire after seven days.
Project status