SentarynSENTARYN
Documentation

Getting teams ready for Sentaryn.

This page describes pilot prerequisites, product concepts, and the intended design-partner workflow. Hosted GitHub enforcement is not presented here as an already-live capability.

Pilot requirements

Who the first pilots are for

  • AI-heavy software teams using GitHub pull requests
  • Teams using Codex, Claude Code, Cursor, Copilot, or similar tools
  • Willingness to start in Shadow Mode
  • Willingness to review findings and help tune policy fit
What Sentaryn evaluates

Core checks

  • Expected vs actual repository scope
  • Sensitive-path and protected-file detection
  • Required evidence for governed changes
  • Explainable allow / approval / block outcomes
Suggested pilot flow

Start with proof, not friction

  1. Begin with the planned Shadow Mode pilot workflow
  2. Evaluate real AI-generated repository changes
  3. Measure useful catches and false positives
  4. Tune policy and evidence requirements
  5. Decide whether a future required-check integration is justified
Outcome

What a good pilot should produce

  • Real repository scope examples
  • Evidence requirements that match team reality
  • Clear useful catches
  • A trustworthy developer experience