πŸ“‹ laravel Γ— regulated

Ship regulated industry on Laravel with sensible defaults.

Laravel is a PHP workable choice for regulated industry. GreatCTO auto-detects both β€” adds the regulated archetype overlay, wires regulated-specific gates, and runs 83 specialist agents around your existing Laravel workflow.

What changes when GreatCTO joins your Laravel project

Detection β†’ overlay β†’ gates β†’ reviewers.

1 Β· DETECT

Stack + archetype

GreatCTO reads your composer.json and detects laravel + regulated archetype from signals: imports, file structure, env vars, README hints.

2 Β· OVERLAY

Archetype pack

Attaches the regulated archetype overlay: archetype-specific reviewer + compliance gates. Override if your specifics differ; the defaults are sensible for Laravel-style projects.

3 Β· GATES

Laravel-aware reviewers

qa-engineer runs phpstan / phpunit / psalm; security-officer checks SQL injection + Laravel CSRF; performance-engineer reviews query N+1 + Redis cache patterns.

4 Β· MEMORY

Cross-project lessons

Bugs you've hit before in other Laravel projects (connection-pool exhaustion, ORM N+1 queries, retry storms) β€” the agent's Step 0 includes the prior detection order. MTTR drops 94 % on second occurrence (methodology).

First 10 minutes

Concrete walkthrough.

$ cd my-laravel-app && npx great-cto init
βœ“ scanning manifests… found manifest
βœ“ stack: laravel (PHP)
βœ“ archetype: regulated
⚠ archetype + stack combo is unusual β€” review overlay manually
βœ“ 83 agents ready

$ /start "add regulated feature"
β–Έ architect drafting ARCH-regulated.md…
β–Έ pm decomposing into beads tasks…
⚐ gate:plan β€” your approval needed

Approve β†’ 3 senior-devs run in parallel worktrees β†’ 5 reviewers fan out in parallel β†’ gate:ship β†’ deploy. One real run walked stage-by-stage: /proof.

What ships

The first feature, Laravel-idiomatic.

This is the shape of what senior-dev drafts for "regulated feature" β€” auth first, schema validation, and the audit line the regulated reviewer requires before gate:ship opens.

// app/Http/Controllers/RegulatedController.php β€” reviewed by 5 agents
class RegulatedController extends Controller
{
    public function __construct() {
        $this->middleware('auth');             // security-officer: auth before handler
    }
    public function store(StoreRegulatedRequest $request) {
        $result = $this->service->handle($request->validated(), $request->user());
        AuditLog::record($request->user()->id, 'regulated feature',
                         $result->confidence);  // gate:regulated: every decision logged
        return response()->json($result);
    }
}
Where this combo lands

What teams build with Laravel + the regulated overlay.

1

SOX-scoped systems with ITGC change management.

2

DORA / NIS2-covered services with ICT risk evidence.

3

ISO 27001 environments with SoA gap tracking.

⚠ Honest caveat

Laravel (PHP) is not a typical fit for regulated industry. The archetype overlay still attaches, but you may want to override defaults more aggressively. Check the regulated archetype page for the typical stack list and decide if your case is the right tool / right archetype.

Architecture

Every step of the pipeline, transparent.

No black-box "AI does it all" loop. GreatCTO is a deterministic state machine β€” 8 stages, 22 nodes, 2 human gates. Every node maps to a real agent on GitHub. Inspect the state machine β†’

Install

Laravel + GreatCTO in one command.

$ npx great-cto init

Free, MIT, runs locally. Built as a Claude Code plugin β€” install with one command.

Related deep-dives

More from the blog

AI

How I designed the SDLC state machine for agentic coding

Eight stages, two human gates, four memory layers. Why this exact shape, and what I tried that didn't work.

AI

First real shipped feature with this stack β€” receipts

One run, one feature, from prompt to merged PR. Time, cost, and gate-by-gate breakdown β€” no marketing math.

AI

How GreatCTO chooses which compliance pack to attach

Regex vs LLM-based archetype detection, the false-positive count, and why I keep rejecting the obvious fix.

AI

Why your agent system fails: missing gates, not missing intelligence

The bottleneck in agentic SDLC isn't model quality β€” it's process governance. Here's the state machine that closes the gap.