Delegate pack · One page
The probe, for the person who approves it.
Someone on your team asked us to run a readiness probe. This page says exactly what that grants, what leaves, and how to turn it off. It is written to be forwarded.
- What it is
- A 20-minute readiness read against the codebase. It produces a score out of 100, the blockers by name, and priced first mandates. No call attached.
- What leaves
- The report artifact only. We store a fingerprint and the report, never the source. Nothing is written to your systems at any level.
- How to revoke
- The read-only GitHub App uninstalls in one click from your org settings, and access ends the moment you do. CI runs live on your runners and stop when you remove the job.
- Who approves
- A person on our side approves every run before anything executes. No probe starts unattended.
The three access levels
Your requester picked one. Any of the three can be downgraded before approval; the probe runs at the level you are comfortable with.
| Level | What we see | What never leaves you |
|---|---|---|
| Outside-in | Public surface only: your app, docs, status history, job posts, public repos. No access granted at all. | Everything. We never touch your systems; the sketch is built from what the internet already shows. |
| Read-only app | Repository structure, tests, dependencies and CI signals, through a read-only GitHub App installed at org level. | Your code. We store a fingerprint and the report, never the source. Revoke the app in one click. |
| In your CI | Whatever your CI shows the container. The probe runs inside your walls on your runners. | Everything including network access. Only the report artifact leaves, and you can read it first. |