Agentic software engineering
Ship agent work the way you ship engineering work
Pholem runs an AI software team inside your repository: isolated branches per ticket, evidence pinned to the reviewed commit, and a spend ceiling you set before anything runs.
- Spend cap
- per project, feature and stage
- Cost split
- Model API · compute · UI
- Merge gate
- human approval, exact head
- Runtimes
- any agent, model or CI provider
How one ticket travels
Full workflow- 01
Scope becomes an executable ticket
Product Owner · Architect
A repository audit turns intent into tickets with acceptance criteria, an owning agent role and a hard spend limit before any code is written.
- 02
One ticket, one isolated branch
Engineer · Tester
Implementation happens on a feature branch in your GitHub or GitLab. The repository stays the canonical source of truth - Pholem never becomes a second one.
- 03
Evidence pinned to the exact commit
Security · DevOps
CI, tests, security scans, audit output and preview deployments are attached to the commit SHA a human is about to read. Stale evidence is rejected, not summarised.
- 04
Humans hold budget and merge
Reviewer · Evaluator
Agents can plan, implement and argue for a change. Approval, spend release and the merge button stay with a person.
Cost control
Autonomy is only safe when the invoice is bounded.
Pholem audits a repository, proposes migrations, estimates lean, balanced and ambitious budget scenarios and generates tickets automatically. Migration execution stays off until you approve it, and work stops at the cap instead of quietly exceeding it.