Handbook
How to read this handbook
Anyone opening the Forge Intelligence handbook for the first time — humans and agents.
Updated
Who is this for?
Anyone opening the Forge Intelligence handbook for the first time — humans and agents.
Four documentation layers
| Layer | Where | When to use |
|---|---|---|
| Operator | operator/ | User concepts, workflows, limits — start here |
| System | system/ | Architecture, contracts, catalogs, maturity |
| Concept wiki | wiki/semantic + wiki/execution | Per-intelligence semantic vs execution overlays |
| Deep maintainer docs | docs/ root pages | ADRs, node catalog, vendor packs, governance |
Four dual-wiki patterns
Forge Intelligence uses four related patterns — see DUAL-WIKI.md:
- Handbook pair — this Markdown publishes as HTML on intelligence.forgesdlc.com.
- Documentation dual-wiki — operator pages (this section) paired with system pages.
- Concept dual-wiki — semantic definitions paired with execution overlays per intelligence.
- Session dual-wiki — machine JSON paired with generated human session reports.
Finding information
| Need | Go to |
|---|---|
| Stable feature ID | feature-index |
| Plain-language term | glossary |
| Change rules | dual-wiki requirements |
| What FI is / is not | overview, boundaries |
What is not on the homepage
Node catalogs, maturity matrices, vendor prompt packs, and registry YAML files remain in maintainer docs — linked from system handbook, not the operator Start here table.