📦 Forge
The Forge is a catalog of certified functions, libraries, services, and templates. Agents reuse these building blocks instead of generating the same logic for every change.
What the Forge contains
| Tier | Examples | Why |
|---|---|---|
| Shared services | Authentication, identity, billing, audit logging, notification dispatch, document storage | Production-hardened services are called, never rebuilt |
| Reusable code | Libraries, shared client SDKs, validated domain logic, cryptographic utilities, telemetry wrappers | Agents import pre-tested packages that already meet enterprise standards |
| In-context templates | Project skeletons, scaffolding, and canonical design patterns (for example frameworks such as Gatelin or Foxnox) injected into agent context | Agents follow the reference architecture from the first line |
| Interface contracts | Versioned API specifications (OpenAPI, gRPC, AsyncAPI) | Cross-service compatibility is fixed before generation starts |
Templates give agents the reference architecture when starting a service, endpoint, or pipeline.
Where the Forge is used
The Forge feeds three stages of the operating model.
| Stage | What happens with the Forge |
|---|---|
| 2 — Think | The agent searches the catalog semantically and proposes reuse options. The chosen assets are recorded as Forge asset bindings in the Think record |
| 3 — Plan | The Plan reads the bindings from the Think record, so the implementation steps compose them |
| 4 — Code | The agent imports the bound packages and calls the bound services, or copies the reusable code |
Rules
- Compose before you build. A custom implementation of something the Forge already offers needs a recorded reason in the Think record.
- One fix, every consumer. Security patches, performance work, and dependency updates made in a Forge module reach all consuming squads automatically.
- Certified before listed. An asset enters the catalog only with an owner, a versioned interface, tests, and documentation.
- Deprecate explicitly. A retired asset carries a replacement and a removal date, so agents never bind to something that is going away.
Who owns it
The Architect owns the Forge, with every team contributing assets through pull requests.
Where it lives
Versioned in enterprise package registries, service catalogs, and in organization repositories.
Health signals
| Signal | Healthy | Warning |
|---|---|---|
| Share of work items that bind at least one Forge asset | Rising | Flat or falling |
| Duplicate logic generated that a Forge asset already covers | Near zero | Recurring |
| Assets without an owner or with a stale version | None | Any |