Verification
What Happens After You Submit a Repo
Submission is the start of the process, not the end. Repokit moves supported repositories through onboarding, training, evaluation, and activation before verification can begin.
The visible stage flow
- submitted
- onboarding
- training
- evaluating
- ready
What is automatic today
Supported repositories auto-start the happy path while intake is active. That means onboarding, training, evaluation, and promotion can move forward without per-repo operator approval in the normal case.
That does not mean every repository will finish successfully. Sparse or unusual repositories can still stop early.
When the workflow becomes useful to you
The key moment is ready. That is when the runtime is active and repository-specific verification can start through API or MCP.
Before that, the repo is still being prepared and the claim is not ready to test yet.
What to expect as a beta user
Treat the stage bar as the source of truth. Submission alone is not a promise of instant serving, and readiness is the point where the workflow becomes verifiable.
Next up
Use the shortest path through submission, readiness, verification, API, and MCP.
Related reading
Why Your Repo May Not Reach Ready
A straightforward explanation of why some repositories stop before ready and why that is an honest beta constraint rather than hidden failure.
Read articleWhat Ready Means in Repokit
Understand the difference between submission, processing, and served readiness so you know when repository-specific verification really starts.
Read articleHow Verification Tokens Work in Repokit
Understand what verification tokens do, when they become available, and how they fit into the API and MCP access flow.
Read articleFeatured paths
If the next useful move is clearer than another article, take it.
Use the main Repokit paths to move from blog reading into docs, submission, API, or MCP without leaving the same funnel.
Debugging path
Start with a regression or failing test.
Use ranked files to narrow the likely implementation surface before you spend time browsing or guessing.
Verification path
Understand ready, tokens, and the real beta flow.
Use the verification and readiness content to judge the product on your own code instead of on generic examples.
API path
Build an internal tool with direct HTTP control.
Go from human-facing API guidance into a real integration once the verification flow and repository boundary are clear.
MCP path
Connect a tool-capable client through MCP.
Keep the scope narrow to one repository and one retrieval task before you try to scale the workflow outward.