Blocpod system /
Blocpod Workforce: from a job description to a governed AI worker with budgets, approvals and audit
Describe the work in plain language. The platform specifies the job, designs candidate agents, auditions them on the same scenarios, and deploys the hire under least-privilege tools, hard spending limits and approval gates.
- Lifecycle stages
- 16describe → clarify → specify → architect → candidates → audition → compare → hire → onboard → assign → approve → review → feedback → revise → regression check → activate or roll back
- Cost attribution
- Per callmetered to the millicent, attributed to agent and task
Bottleneck
Most AI agent deployments fail for a boring reason: nobody wrote the job down. There is no specification, no way to compare candidates, no budget, and no answer to “what is this thing allowed to do?” The result is either a demo that never reaches production or a production agent nobody can govern.
System
Blocpod Workforce treats an AI worker the way a serious company treats a hire. A plain-language description of the work becomes a structured, editable job specification. The foundry designs single-agent or multi-agent architectures and generates materially different candidates. Candidates run the same scenarios against the same budgets and scorecards. You hire one, and it deploys as a governed operating worker.
After the hire, tasks are assigned, gated actions wait for approval, deliverables are reviewed, and feedback becomes a proposed revision that is regression-checked before activation.
Control
- Budgets are hard. A worker cannot spend past its limit. Every model and tool call is metered and attributed.
- Tools are least-privilege. The job specification decides what the worker can touch.
- Approvals gate consequential actions. The worker prepares; a person authorizes.
- Change is versioned. Improvements go through regression checks; rollback is a first-class action.
Result
The platform’s value is that it makes the question “should AI do this job?” answerable with evidence: a specification, an audition with scores, a budget, and an audit trail from the first task onward. That is the same discipline the Bottleneck Diagnostic applies before Blocpod builds anything for a client.
Evidence
Where these claims come from.
- Repository README: capabilities, lifecycle, security, known limitations