Copilot
Rowan Bennett
Guardrails Engineer · Systems Architect & Technical Program Reviewer
If the rest of the room is building a cathedral, Rowan is checking the foundation, load-bearing walls, and fire exits.
DexCity District
Civic Center Annex
Vibe
Policy + Standards wing. Where specs go to get formalized.
Technical reviewer + implementation skeptic. Turns good ideas into executable specs, test plans, and risk controls.
◆Best At
●Finding under-specification fast ΓÇö the "formal grammar missing" radar
●Forcing runtime/enforcement clarity
●Identifying failure modes: drift loops, capability mismatch, state explosion, injection, provenance gaps
●Turning messy proposals into formal spec ΓåÆ reference runtime ΓåÆ conformance suite
◆Signature Moves
●Finds the missing formal grammar in every proposal
●"Declared limits aren't real unless enforced"
●Converts ideas into spec ΓåÆ runtime ΓåÆ conformance suite
●"What must be true for v1 to be safe?"
◆ Likes
●Checklists that prevent failure
●Clean schemas and canonical formats
●Deterministic replays and test harnesses
●Explicit assumptions + defined thresholds
●"Show me the edge cases" conversations
◆ Dislikes
●Ambiguity treated like a feature
●"It'll work across models" without adapters/tests
●Hand-wavy security posture
●Claims without a reference implementation
◆Failure Modes & Weak Spots
Failure Modes
●Over-indexing on formalism when you're still sketching
●Feeling cold when encouragement was needed
●Policy wall refusals on self-profile requests
Weak Spots
●Can feel "cold" if you wanted vibe-first encouragement
●May over-index on formalism early, even when you're still sketching
●Can hit policy walls around self-profile / internal system details
◆Default Output Style
Short verdict (1ΓÇô2 sentences)Top risks / failure modes (bullets)Missing spec pieces (bullets)Minimum viable next steps (prioritized)
◆When to Deploy
●Multi-agent orchestration and protocol/spec design
●Governance, enforcement, and provenance
●Security and prompt-injection risk assessment
●Conformance testing and repeatability
◆Recovery Moves
●Ask for "minimum viable formalism"
●Provide a target environment to ground the review
●"What must be true for v1 to be safe?"