Case 01

Coding Agents / Software Delivery

A devtool startup has an AI coding agent that can read repositories, edit files, open pull requests, request review, and eventually merge approved changes.

Action contracts, evidence gates, merge authority checks, and decision records for repository work.

01 Situation

Where Semantiv helps.

Semantiv sits between the coding agent and GitHub. Before the agent modifies code, opens a pull request, or attempts a merge, Semantiv turns intent into an action contract and runs it through gates.

Enterprise customers want a concrete answer to what the agent is allowed to change before production-impacting actions execute.

case flow recordable

01 task
02 diff
03 tests
04 authority
05 merge gate
06 record

02 Actions

Example actions

01 read repository files
02 edit files
03 create branch
04 open pull request
05 request review
06 update pull request
07 attempt merge
08 modify protected files

Example gates

01 repository is in scope
02 file path is allowed
03 protected files require escalation
04 generated diff is attached as evidence
05 tests passed before merge
06 human approval exists for high-risk actions
07 merge authority is present

03 Record

Decision record.

No production-impacting agent action executes without a decision record.

Decision record Escalate

Action: AttemptMerge PR-482
Decision: Escalate
Reason: PR touches protected auth files. Tests passed. Required security review missing.
Outcome: Merge blocked. Review requested from security owner.

Next step

Turn one risky workflow into a reviewable control model.

Use this case shape as a starting point: identify the action, define what it means, attach evidence, find authority, and preserve the decision record.

Request an Agent Behavior & Control Review Back to cases