Handbook
Handbook pair (fi ↔ fiw)
Forge Intelligence follows the workspace product repo ↔ handbook deploy shell pattern.
Updated
| Abbr | Repo | Role |
|---|---|---|
| fi | forge-intelligence/ |
Markdown SoT, packs, schemas, Python package |
| fiw | forge-intelligence-website/ |
kitchensink + fi submodule → Firebase Hosting |
Sync workflow
- Edit docs in forge-intelligence (
docs/,README.md); commit in fi. - In forge-intelligence-website: bump
forge-intelligencesubmodule pointer. - Build:
python3 generator/build-site.py→ updates trackedwebsite/. - Deploy:
./deploy-websites.sh --only forge-intelligence-websitefrom workspace root.
Firebase
| Item | Value |
|---|---|
| Firebase project | forge-intelligence-handbook |
| Hosting site | forge-intelligence-handbook |
| Custom domain | https://intelligence.forgesdlc.com |
Create the Firebase project and connect the custom domain before first live deploy.
DNS: Cloud DNS zone forgesdlc-com (project forge-sdlc) — CNAME intelligence → forge-intelligence-handbook.web.app.
Submodule init
cd forge-intelligence-website
git submodule update --init --recursive
Distinction from session dual-wiki
- Handbook pair — product documentation published as HTML.
- Session dual-wiki — per-session M/H audit trail (DUAL-WIKI.md).
Kitchensink propagation
If handbook chrome or forge-autodoc changes, propagate kitchensink first:
./sync-kitchensink-and-rebuild.sh
Then bump kitchensink submodule in fiw and rebuild.