Handbook
Product boundaries
Integrators placing Forge Intelligence alongside LCDL, Platform, Lenses, and Fleet.
Updated
Who is this for?
Integrators placing Forge Intelligence alongside LCDL, Platform, Lenses, and Fleet.
What problem does it solve?
Clear ownership prevents duplicate runtimes, conflicting sources of truth, and scope creep. Forge Intelligence owns problem-class policy and session telemetry shapes — not execution planes, UI, or doc hydration.
What Forge Intelligence owns
- Problem-class catalog and pack policies
- Per-domain intelligence libraries
- Session dual-wiki (machine + generated human report)
- Attach schemas for route trace, token ledger, ambiguity
What Forge Intelligence does not own
| Product | Owns instead |
|---|---|
| LCDL | Governed LLM tasks, operators, flow execution |
| Lenses | ForgeRun system of record, approvals, evidence review UI |
| Platform | Ecosystem ADRs, cross-product contracts, doc hydration |
| Fleet | Containerized job execution plane |
Critical rules (operator view)
- FI is not a second LCDL runtime — packs compose existing tasks.
- FI is not the ForgeRun system of record — sessions attach evidence; Lenses is authoritative.
- FI is not doc hydration — claim registries stay in Platform design.
- Break-in actions are closed sets defined in pack policy — no open-ended agent loops.
Limitations
Ecosystem placement evolves with Platform ADRs. When in doubt, check the paired system page and PRODUCT-BOUNDARIES.md.
Next steps
- Platform overview
- Sessions and audit
- System depth: paired system page