How the work is specified
BramForgeLabs products are written from a working architecture. This page shows the patterns that architecture uses — so a buyer can see the difference between a template and a system. It does not publish the private fleet, model names, or infrastructure.
BramForgeLabs is not a consultancy, a SaaS platform, or an implementation partner. It publishes structured reference products — playbooks, radars, and synthesis — that practitioners use themselves.
Every buildable spec in the catalogue uses the same four-role loop. Fluency is not a role. Citation, refusal, and handoff are.
The verifier does not trust the synthesizer. Same-model self-check is not verification. Low confidence, ungrounded claims, or anything that would become an automated decision goes to a human with a reason code and an immutable trace.
That pattern is what “regulation-aware” means here: the audit trail is the product, not a slide at the end.
A use case is not a paragraph. It is a contract a team can hand to engineering. Every detailed cell in the IT playbook and the Insurance Radar uses the same skeleton:
| # | Section | What it forces |
|---|---|---|
| 1 | Problem & context | Whose backlog, not whose keynote |
| 2 | Success metrics | A number that would kill the project if it failed |
| 3 | Solution architecture | A diagram, not a vendor name |
| 4 | Agent roles | Inputs, outputs, success criteria per agent |
| 5 | Orchestration | Who runs, who may not decide |
| 6 | Data requirements | Purpose limitation; what must not enter the window |
| 7 | Implementation guidance | Schema first, prompt second |
| 8 | Failure modes | Hallucination, purpose creep, injection |
| 9 | POC scope | Two weeks; the demo that counts |
| 10 | Path to production | Inventory, override, drift |
| 11 | How to build | Step-by-step + one concrete multi-agent path |
No role both implements and verifies the same change. Design, implement, verify, audit. That is the whole governance claim, stated as an operating rule rather than an org chart.
Agent names, model providers, ports, cron, or the private operating system. Those are the factory. This is the method the factory uses. If a page needs a roster to look serious, it is not yet a product.
The original house-pattern example: retrieval, synthesis, verification, escalation on an ITSM knowledge base.
Playbook sample →The same four agents on a life-underwriting file. Prohibited fields: rating, decline, issue. The packet cites or it does not ship.
Radar sample →