Semantiv Request Review

Possible POC

GitHub agent behavior review and control prototype.

GitHub is a useful prototype surface because coding agents are visible, useful, and risky. The POC tests whether Semantiv can turn messy behavior into meaning, evidence, authority, coordination, control, and record.

Not a branch-protection wrapper. A reviewable slice of agent behavior and control.

01 Demo flow

An agent wants to modify code in a production repository.

The important question is not only whether the path is allowed. It is what the change means, what evidence supports it, who needs to review it, and what action should be allowed, blocked, escalated, or recorded.

demo flow recordable
  1. 01 agent proposes repository work
  2. 02 trace, diff, tests, and approvals reviewed
  3. 03 operational meaning assigned
  4. 04 evidence and authority checked
  5. 05 control recommendation produced
  6. 06 decision record stored
02 MVP actions
ReadRepo

Agent reads files or metadata

Which context did the agent rely on?

ProposeChange

Agent produces a diff or patch

What system behavior is affected?

OpenPullRequest

Agent creates a branch and PR

What work is being submitted for review?

RequestReview

Agent asks for human review

What authority is being requested?

AttemptMerge

Agent tries to merge

Is the system allowed to accept this work now?

ModifyProtectedPath

Agent changes protected files

What business or security obligation may be affected?

03 Core types

A small console, not a general platform.

The prototype should show behavior trace, operational meaning, evidence packet, missing evidence, authority requirement, control recommendation, and decision record. 

BehaviorTrace
ActionMeaning
EvidencePacket
AuthorityContext
ControlRecommendation
DecisionRecord
04 Proves

What this POC proves.

  • 01Semantiv can review real agent behavior, not only static policy.
  • 02Operational meaning can be extracted from traces and artifacts.
  • 03Evidence gaps can be made explicit.
  • 04Coordination and authority can be modeled.
  • 05A decision record can explain why work should proceed or stop.
  • 06The same method can apply beyond GitHub.
Next step

Use GitHub as a concrete slice, not as the company.

The POC succeeds when it helps a team understand what an agent changed, what that change means, what evidence exists, and what control should apply.

Request an Agent Behavior & Control Review View coding-agent case