Team Review & Access Rights
Goal: Let your team (and any AI it brings) move fast on changes that matter - safely.
Not everything needs a gate. But when a change touches production, access, or a shared source of truth, OpenX gives you a confidence layer: AI proposes, the right teammate accepts per their access rights, and the decision is recorded. This is the part that lets you ship fast without breaking what matters.
How review works
- Someone - a teammate, Azi, or an external agent over MCP - proposes a change via
manage_proposals(a new query, an edit, a correction). - It waits as a proposal, tagged by origin (you or an AI), not a live change.
- The right teammate reviews it in the portal - the proposal, the reasoning, a preview.
- They accept, edit, or reject, per their access rights.
- On accept, save and deploy; either way the decision is recorded.
There is deliberately no accept tool over MCP. Building is open to any AI; what goes live is always a human call in the portal. That boundary is the point.
Correcting recorded data
Corrections are proposals too: pick the record, choose a reason, add a justification, review the before/after, submit. A second teammate confirms. The original is never modified - a linked amendment records the change, so the full chain stays traceable. A correction is good practice, not a failure. Full how-to in Corrections.
Why it compounds
Because every proposal and decision is recorded, your team's judgment accumulates - you always see who decided what, and why. That history is Ship with Confidence.
Next steps
- See how decisions are recorded -> Ship with Confidence
- Set who can accept what -> Team & Access Rights