HomeRunHistoryBillingSettings
Sign in

Run

Step 3 of 3: choose one scoped PR for one governed-packet check.

Keep this step narrow: one repo, one PR, short optional context, and one governed packet at the end. If trusted analysis is unavailable, intake stays paused instead of inventing a fallback verdict, and the page names the missing setup before the form can submit.

Connected repo

0

Only the one connected repo can start a governed-packet check from this surface.

Listed PRs

0

Starting a governed-packet check stays PR-first and keeps the selected repo scope explicit from start to governed packet.

Saved repo notes

0 saved · 0 eligible · usage window missing

Saved repo notes need plan or repo setup before they can be reused.

Entry loop step 3 of 3

Pick one PR that matters and keep intake read-only.

This surface is where Codaegis reads one PR, keeps the scope explicit, and saves one governed packet for human decision support.

Sign in first. Intake waits until one account owns the next governed-packet check.

Return to ConnectOpen Result

Intake posture

Sign in first0 connected repo0 listed PRs

Submitting a governed-packet check stays PR-first, one repo at a time, and read-only by default. Nothing in this step silently changes access, billing, or authority.

If starting is unavailable, use the button label and setup reason to return to the next place. After a governed-packet check finishes, Result becomes the latest governed packet and History becomes the place to compare past governed packets and return for the next check.

Preflight

PR intake posture

Checks visibleGovernance pendingNo governed packet yetMissing proof: focused test evidenceHuman decision remains separate

External checks and risk cues are intake evidence only. Governance stays pending until one packet is saved from this selected PR.

Repo in use

No repo

Connect one repo before starting a governed-packet check.

Selected pull request

No PR

No selectable pull request is listed yet for the selected repo.

Saved repo notes

Needs setup

This check uses a one-time note only because saved repo notes need plan setup.

GitHub PR preflight checklist

Confirm these items before the first governed-packet check. Anything marked paused or needs you is a handoff point, not something Codaegis works around.

2/8 available for this check

Account owner

Needs you

Sign in before any real repo can be checked.

A governed packet should belong to one accountable user.

One repo

Needs you

Connect one repo before packet intake can submit.

Codaegis v1 keeps the first governed packet inside one named repo scope.

One pull request

Needs you

Choose one listed pull request.

The review needs one clear change target, not a broad repo scan.

Evidence source

Needs you

No PR evidence source is selected yet.

The packet should name whether it is using current repo evidence or local rehearsal data.

Risk cues named

Check

No risk cues are visible yet.

The governed packet should preserve the cues that made this PR worth checking.

Saved repo notes

Needs you

Select a repo before saved notes can be checked.

Repo memory should help only when it is explicitly available for this scope.

Trusted analysis

Available for this check

Trusted analysis path is in scope.

Codaegis should stop before inventing a verdict.

No repo changes

Available for this check

This check remains read-only and advisory.

The first product promise is a governed packet for review, not a repo change.

Connected repo

Sign in and connect one repo before starting a governed-packet check.

Selected PR

Choose a connected repo with at least one listed pull request to see the governed-packet preflight here.

Saved repo notes

Saved repo notes appear after a repo is selected.

Useful intake signals

  • The pull request is close enough to a human decision that evidence quality matters.
  • It touches auth, billing, schema, permissions, or release behavior.
  • AI wrote a meaningful share of it, or the CI story is mixed or failing.
  • Rollback notes or missing context still need a human decision.

This check will

  • Begin from one connected repo and one pull request that needs a careful check.
  • Keep optional context short and concrete so the governed packet stays easy to trust.
  • If a repo, pull request, or trusted analysis path is missing, stop on the blocked reason and return to the named setup step.
  • Codaegis saves one governed packet only when the trusted service returns a verified result.
  • Use the current recorded repo access for one selected repo.
  • Reduce unnecessary client-IP exposure by keeping the check bound to the selected repo and PR.
  • Read one selected PR and preserve the current repo details in the governed packet.
  • Start without saved repo notes because the current plan does not include them.
  • Save one saved-packet record only after the trusted analysis path returns a verified result.

This check will not

  • Push code, merge the PR, or change repo settings.
  • Silently request broader permissions or widen repo access on its own.
  • Ask for secrets, credentials, production access, customer data, private logs, or unrelated source code.
  • Silently invent a fallback verdict if trusted analysis is unavailable.
  • Invent missing deployment or rollback knowledge if the current inputs do not provide it.
  • Hide repo access or PR reachability problems if the selected PR can no longer be reached.

Start governed-packet check

Sign-in and plan setup are needed first. Sign in and connect one repo before starting a governed-packet check. Until then, Run stays paused.
Codaegis will use the current recorded repo access only. If more access would materially improve the governed packet, it will ask for it instead of taking action. Saved packet materials are used to support the requested check purpose.
Trusted analysis path is in scope. Codaegis will only save a packet when the trusted service returns a verified result.

Sign-in is needed first. Return to Connect so the check belongs to one account.

After a packet is saved

  • Start with the governed packet verdict, then read the reasons and risks before you act.
  • Treat the recorded next action as your checklist, not as background reading.
  • Return to Run for the next PR that needs a check in the same repo.
  • Use History to compare governed packets and notice repeat issues over time.