Handbook
Blueprint consumers
Some workspace repos consume Blueprints and/or Kitchen Sink but are not Forge Platform instruments. They illustrate adoption patterns — not control-plane or execution strata.
Updated
Listed consumers
| Repo | Purpose | Platform relation |
|---|---|---|
Situ8 (Situ8/) |
Android app — case workflows, BYOK LLMs; blueprints submodule | Process consumer example |
Situ8-web (Situ8-web/) |
Marketing site for situ8.app; KS generator | Design-system consumer; separate Firebase |
Capablio (capablio-website/) |
Private handbook / forge360 shell | Adjacent SKU |
What they do not do
- Do not write ForgeRun state to Lenses
- Do not ship platform schemas or ADRs
- Do not appear in the core spine topology as instruments
Deploy tooling
forge-composer can deploy reviewed manifests into consumer repos:
cd forge-composer
python -m forge_composer deploy --manifest targets/situ8.yaml --workspace-root .. --apply
See forge-composer.
Related
- Product boundaries — Out of platform spine
- Ecosystem reference
- Blueprints — canonical policy and Forge setup