Before (failing example)

After (passing example)

Before (failing example)

Introduction

Expanded diagram

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Skip to content

ForgeSDLC

Governed human + agent delivery

Shape intent, delegate safely, and release with evidence—not ad hoc prompts.

Start quickstart See how it works

Full documentation · Trust model

Three outcomes teams need

Clear intent before agent work starts.

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

How governed delivery flows

Intent to release

After (passing example)

How governed delivery flows

Intent to release

Linear gate chain: Intent → Human review → Agent execution → Release

Before (failing example)

How it works

Delivery gate chain

Work moves through intent, human review, agent execution, and release checkpoints.

Custom flow for this landing page only.

After (passing example)

How it works

Delivery gate chain

Work moves through intent, human review, agent execution, and release checkpoints.

Registered template under Ksv / Zxd — catalog key gate matches gallery and visual registry.

Before (failing example)

Diagram label coverage

Catalog keys without on-surface names

Modal legend lists Step A–D, but the SVG surface only shows [subtitle] placeholders.

Catalog legend requires Gate 1 and Gate 2; diamonds only show G.

After (passing example)

Diagram label coverage

Legend keys visible on the tile

Step A, Step B, Step C, Step D (matches catalog nodes)

Surface text includes Stage 1, Gate 1, Stage 2, Gate 2, Stage 3 per catalog.

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Featured guide

Static copy — motion reserved for essential status only.

Path

Quickstart

24

Syncing rules

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

job=forge-lenses-docs-health status=RUNNING queue=3 worker=node-7

last_event=2026-05-19T18:01:02Z detail=container argv drift

After (passing example)

detail=container argv drift

Before (failing example)

After (passing example)

Before (failing example)

Forge Platform

Governed delivery spine for human-owned agent execution

Intent, structure, delegation, review, and evidence in one workspace.

Not a docs tree—a product control plane you can inspect.

Lenses shows workspace state; LCDL governs LLM tasks; Fleet runs bounded jobs.

For platform engineers, operators, and methodology leads.

Start quickstart Read docs

Trust · Schemas · Operate

• Local-first workspace visibility
• Governed LLM task layer
• Token-protected job plane

Methodology

ForgeSDLC

Intent to evidence

Control plane

Lenses

Workspace visibility

Reasoning

LCDL

Governed LLM tasks

After (passing example)

Forge Platform

Governed delivery spine

Human-owned intent, agent execution, and reviewable evidence—without opening the full handbook first.

Start quickstart Read docs

One governed-flow snapshot—not the full architecture map.

Outcomes

Three layers, one story

Methodology

ForgeSDLC

Shape intent and release with evidence

Control plane

Lenses

See workspace state and next safe action

Reasoning

LCDL

Versioned, schema-aware LLM tasks

How it works

Platform topology

Full subsystem map for readers who already understand the promise.

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

How it works

Human review before agent execution

Work moves in one direction: shape intent, pass a human review gate, then let the agent execute inside bounded scope, then release with evidence.

After (passing example)

How it works

Human review before agent execution

Work moves in one direction: shape intent, pass a human review gate, then let the agent execute inside bounded scope, then release with evidence.

Linear gate chain: Intent → Human review → Agent execution → Release (matches left-to-right arrows and diamond gates in the SVG).

Before (failing example)

Architecture overview

Use the diagram to explain the flow.

Handbook content—no nav button on narrow viewports.

After (passing example)

Architecture overview

Select the diagram to open a larger view with step-by-step notes.

Menu

Handbook

Theme

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

PLATFORM · AI · GOVERNANCE · DOCS

Everything you need!!!

Agents, automation, compliance, analytics, dashboards, and more in one place.

Get started Learn more Book demo Watch video

Fast

Ship instantly

Secure

Enterprise grade

Smart AI

Why teams choose us

Feature

Feature

Feature

Feature

After (passing example)

Forge Platform

Governed delivery you can inspect

Structure intent, delegate safely, and keep human review points—presented with calm, deliberate spacing.

Start with Quickstart See how it works

Outcomes

What changes for your team

Control

Human-owned gates

Review points stay visible—copy and card treatment match the rest of the page.

Evidence

Inspectable artifacts

Logs and contracts linked with the same elevation and typography rhythm as adjacent tiles.

Depth

Mechanism on demand

Technical detail deferred to docs—this band stays spacious and scannable.

Operating model at a glance

Intent

Shape

Clear problem statement before delegation

Execution

Delegate

Bounded jobs and governed LLM tasks

Assurance

Review

Evidence you can trace—not decorative KPI noise

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Forge Platform

Governed delivery you can inspect

Calm dark surfaces, amber primary actions, and cyan structure labels—accents that guide reading instead of decorating every line.

Start with Quickstart See how it works

Outcomes

One temperament across the page

Control

Human-owned gates

Amber accent marks the primary story tile—same role on every card.

Evidence

Inspectable artifacts

Headlines stay solid display type; gradient reserved for the hero.

Depth

Neutral glass for supporting copy—cyan label, no third accent hue.

Before (failing example)

After (passing example)

Before (failing example)

After (passing example)

Forge Platform

Governed delivery you can inspect

One headline carries the fold; tagline and CTAs stay visibly subordinate.

Start with Quickstart See how it works

Read architecture docs

Outcomes

What changes for your team

Primary outcome

Human-owned gates

One accented tile marks the hero proof point; siblings stay quieter.

Supporting

Evidence trail

Default elevation and body scale—readable, not competing.

Supporting

Bounded automation

Depth links appear after the eye learns the focal path.

How it works

Mechanism at lower weight

Mechanism and reference bands use section labels and body copy—not a second display headline in the fold.

Before (failing example)

Forge Platform

Governed human and agent delivery

See how intent, review gates, and evidence connect across your workspace.

Why teams choose us

Everything you need

Secure

Enterprise-grade protection

Fast

Move at AI speed

Smart

Powered by agents

After (passing example)

Forge Platform

Governed human and agent delivery

Structure intent, keep human review gates, and ship with evidence—not ambient decoration alone.

The diagram shows the same spine the product implements: intent → review → bounded agent work → release artifact.

Outcomes

What each layer gives you

Human control

Review before agent work

Gates in the diagram match operator-owned approval points—not a generic lock icon.

Evidence

Artifacts you can inspect

Release node ties to logs and contracts linked from this handbook.

Mechanism

Full gate-chain detail

Expand the registered diagram below for labels and catalog legend keys.

How it works

Gate chain matches the hero visual

Follow left-to-right: intent is shaped, humans approve, agents execute inside scope, then release carries evidence.

Same topology as the hero: captions name actors and order so the visual teaches structure, not mood.

Before (failing example)

Forge Platform

Governed delivery spine

Structure intent and keep review points visible.

Quickstart Docs

Outcomes

What changes

Control

Human gates

Review stays visible.

Evidence

Logs linked inline.

Depth

How it works

Step 1

Shape intent.

Step 2

Delegate with bounds.

12 modules

48 endpoints

∞ agents

After (passing example)

Forge Platform

Governed delivery you can inspect

Structure intent, delegate safely, and keep human review points—presented with deliberate vertical cadence.

Start with Quickstart See how it works

Outcomes

What changes for your team

Control

Human-owned gates

Review points stay visible in every band.

Evidence

Inspectable artifacts

Logs and contracts use the same card rhythm as neighbors.

Depth

Mechanism on demand

Technical detail deferred—this row stays aligned and even.

How it works

From intent to evidence

Step 1

Shape intent

Capture goals and boundaries before delegation.

Step 2

Delegate with bounds

Agents execute inside review gates you define.

4 layers

1 governance spine

0 mystery gaps