FORGE
Orchestrate. Prepare repository context, classify risk, plan work, manage approvals, persist runs, and collect evidence around AI-assisted engineering.
Explore FORGE →
GODTECH ECOSYSTEM
Build it. Keep it healthy. Govern the work around it.
FORGE, StackPilot, and Steward are separate tools with different jobs. The ecosystem becomes more useful precisely because they do not duplicate each other.
StackPilot
Scaffold. Choose supported project shapes, generate production-minded foundations, and keep golden-path assumptions under one dedicated tool.
Explore StackPilot →Steward
Maintain. Scan repositories deterministically, explain health findings, report stable evidence, and apply only explicit safe fixes.
Install Steward →
BOUNDARIES
One project. Different responsibilities.
01
Before building
FORGE can inspect the project and prepare bounded context. StackPilot can generate or adopt a supported project foundation.
02
While building
FORGE governs task flow, approvals, runs, and evidence. The coding client remains responsible for model execution.
03
After changes
Steward can independently scan repository health and produce findings that can optionally feed a FORGE verification workflow.
Integration rule: FORGE may call Steward through public CLI and machine-readable contracts when repository health is relevant. StackPilot may consume Steward's versioned scan report observationally. Neither integration changes the owning product's core responsibility, and neither makes Steward or StackPilot a runtime prerequisite for FORGE.
START HERE
Use the smallest tool that solves the problem.
Need a project foundation? Start with StackPilot. Need a governed AI engineering workflow? Start with FORGE. Need repository health or housekeeping? Start with Steward.