Problem
New users start from a blank ruleset. There are no curated policy packs, so every team must author rules from scratch before Room provides any value.
Proposal
Ship a library of starter ruleset templates covering common guardrail scenarios, for example:
- Secrets prevention — block diffs that introduce API keys, tokens, private keys
- Unsafe code patterns — language-specific signals (e.g., Rust
unsafe without safety contract, Python eval/exec, SQL string concatenation)
- Dependency guardrails — flag known-vulnerable package versions in lockfile changes
- Filesystem/path safety — detect path traversal patterns in new code
- Minimal / permissive — a low-friction starter pack that only blocks the highest-severity signals
Each template should be:
- Publishable via
roomctl publish with minimal customization
- Documented with the signals it covers and its enforcement posture
- Versioned alongside Room releases
Why
Reducing time-to-first-value is critical for adoption. Curated packs let teams get enforcement running immediately and then customize, rather than starting from zero.
Problem
New users start from a blank ruleset. There are no curated policy packs, so every team must author rules from scratch before Room provides any value.
Proposal
Ship a library of starter ruleset templates covering common guardrail scenarios, for example:
unsafewithout safety contract, Pythoneval/exec, SQL string concatenation)Each template should be:
roomctl publishwith minimal customizationWhy
Reducing time-to-first-value is critical for adoption. Curated packs let teams get enforcement running immediately and then customize, rather than starting from zero.