TASIP-008: Org-level policy templates

[ryw]

Status: Draft — open for input · Category: Enhancement

Summary

Define governance policy once at the org level (e.g. "high-audit" vs "light-touch") and have workspaces inherit it — tightening but not loosening. Enterprises get consistent guardrails across many teams without micromanaging each workspace.

Why

At one team, per-workspace settings are fine. Across dozens of teams, you need a way to set a floor centrally and let teams go stricter, not looser — and to see when someone overrides it.

Sketch

• Org admins define named policy templates.
• Workspaces inherit; they can tighten but not loosen.
• Template version diffs and override events (with justification) land in the audit log.
  (Provisional — the shape changes based on the discussion.)

Open questions

• What's in a policy template (review rules, retention, connection allowlists)?
• How do template updates roll out to inheriting workspaces?
• What overrides require justification vs are simply blocked?

How to help

React 👍 if you want this, and comment with your use case, constraints, or pushback. This is a draft Tembo Agent Studio Improvement Proposal (TASIP); your input shapes it before it becomes scheduled work.