Handbook
Forge Lenses — see your Forge workspace locally
Forge Lenses is a local Python server and browser dashboard for Forge SDLC–aligned repos: inspect plans, sibling projects, documentation health, and workshop flows entirely on machines you control.
Updated
This site (lenses.forgesdlc.com) is the canonical product documentation home for Lenses—install guides, tutorials, enterprise posture, and builder-facing API/schema notes. Forge SDLC carries adoption and methodology narrative; Blueprints holds methodology guides and Wizard background; Kitchen Sink documents the diagram and layout primitives used here.
Hero path from install
|
v
workspace root selection to Classic or StudioStart here — primary actions
| Goal | Start |
|---|---|
| Install and run | Install and run |
| First Studio session | Studio 101 |
| First Wizard session (experimental) | Wizard 101 |
| Enterprise / security posture | Security and local-first → Enterprise hub |
| HTTP API, schemas, examples | Builders overview → Schemas and API (builders) |
Choose your role
Pick a path curated for how you evaluate or operate Lenses.
| Role | Start | Typical next steps |
|---|---|---|
| Evaluator | Lenses overview | Install and run, Security and local-first |
| Solo developer | Workspace setup | Studio 101, Docs Health |
| Team lead | Tutorials — 201 | Wizard 201, Examples hub |
| Platform operator | Enterprise hub | Network binding, Backup and upgrades, Configuration reference |
| Security reviewer | Security and local-first | OIDC sessions, Action allowlists, LLM boundaries |
| Builder / integrator | Builders overview | Route families, HTTP API route catalog, JSON examples |
Detailed journey tables live on Pick your path—including topics not to start from on day one.
Time horizons
| Horizon | Goal |
|---|---|
| First 10 minutes | Understand products and trust posture → install → choose a workspace root. |
| First hour | Complete a Studio 101 or Wizard 101 exercise; optional Docs Health scan. |
| First day | Establish day-two flows (Studio 201, Wizard 201), optional LLM/offline stance (LLM and AI setup). |
| First week | Enterprise rollout inputs (binding, backups, Fleet if used), Tutorials — 301, Builders integration sketches. |
Product map — what sits on one server
| Area | Plain language |
|---|---|
| Classic Lenses | Server-rendered workspace dashboard at / — projects, Forge plan lenses, rooted in your clones. |
| Forge Studio | React UX at /studio/ — newer flows and dashboards on the same /api surface as Classic. |
| Blueprints Wizard | Experimental guided workshop/session flow inside Studio (/studio/blueprints/wizard/): exports and facilitation; no automatic Blueprints submodule commits. |
| Docs Health | Analysis/reporting surfaces for handbook and doc quality (Docs Health). |
| Fleet / LLM settings | Optional: remote Fleet hooks and model usage when you deliberately enable them in settings or environment. |
One server hosting Classic dashboard, Forge Studio, shared API, Docs Health signalsEnterprise trust posture (summary)
| Property | Meaning |
|---|---|
| Local-first | Repos and Wizard session data stay on volumes you manage unless you integrate outbound services. |
| Loopback by default | Bind to 127.0.0.1 until you knowingly expose the server for LAN/testing. |
| Optional outbound | Fleet and LLMs are opt-in configurations — read enterprise pages before enabling. |
| Explicit write scope | High-impact actions honor operator allowlists and settings; failures should be surfaced in UI/API. |
For the full reviewer-oriented narrative, Security and local-first and the Enterprise hub.
Ecosystem map — where each site helps
| Site | Responsibility |
|---|---|
| forgesdlc.com | Forge SDLC methodology, adoption narratives, encyclopedia pointers. |
| blueprints.forgesdlc.com | Blueprints practice library; methodology depth that supports Wizard and planning work. |
| lenses.forgesdlc.com (this handbook) | Product usage, installation, tutorials, ops, schemas, APIs. |
| ks.forgesdlc.com | Kitchen Sink design system — components, diagrams, generator patterns mirrored in handbook builds. |
See Cross-site map for deeper linking.
Next steps and support
| Need | Doc |
|---|---|
| Troubleshooting | Troubleshooting |
| Release notes / versions | Release notes, Docs versioning |
| Terms | Glossary, Support |
Maintainer & contributor handbook
Publishing workflow, deeper ADRs, and raw route inventories remain in docs/maintainer/ in the forge-lenses repo on GitHub. They intentionally omit from the lean public handbook build—you will not navigate there from primary reader journeys on this site.
Local handbook build
With Kitchen Sink at kitchensink/:
python3 generator/build-lenses-docs.py
# Mirror production page set:
# LENSES_DOCS_BUILD_PROFILE=public python3 generator/build-lenses-docs.py
Output: lenses-docs/. The Firebase-hosted shell consumes the same subtree via forge-lenses-website.