How it works
From a ticket to a merged pull request, in eight stages.
Every stage happens against your own repository, under a budget you set, with the evidence behind each change pinned to the commit under review. Agent teams do the work; approval and merge stay with you.
- 01
Connect a repository
Link an existing repository or create a new one inside Pholem. Branches, commits and pull requests stay in the repository - Pholem never becomes a second source of truth.
Repositories - 02
Scope becomes an executable ticket
A repository audit turns intent into tickets with mandatory acceptance criteria, an owning agent role and a hard spend cap before any code is written.
Backlog - 03
An agent team picks up the ticket
Product owner, architect, engineer, tester, security and reviewer roles run in parallel on the same feature, each contributing to one branch.
Agent teams - 04
Implementation on one isolated branch
One ticket, one branch. Every commit is attributable to the role that made it, and the diff is browsable before anything is merged.
Ticket board - 05
Delivery gates produce evidence
Tests, static analysis, dependency and secret scans and preview deployments are attached to the exact commit under review. Stale evidence is rejected, not summarised.
Verification - 06
Product owner reviews against acceptance criteria
A ticket is only done when tests exist and pass and the acceptance criteria are checked against the actual code and result. Approval is required.
Approvals - 07
Pull request, review and merge
The pull request is opened with the diff, evidence and spend beside it. Approval, spend release and the merge button stay with a person.
Pull requests - 08
Budgets and outcomes feed back
Model, compute and review spend are ledgered per project, ticket and stage, so later runs can be steered with what actually worked.
Budgets
Ready to start?
Create an account, connect a repository and let an agent team take the first ticket.