Know the ground.
Then build.
From your first workspace to the next release.
Understand the contracts, boundaries and tools behind ForgeZero.
Start on solid ground.
Understand the parts of ForgeZero, then connect your first workspace.
Read guide ↗Start hereConfigure the boundary.
Public build settings and private runtime configuration have different homes.
Read guide ↗Build & releaseA release is a handoff.
Readiness, ownership and drain belong in the deployment contract.
Read guide ↗PlatformSecrets with a scope.
Give each workload a precise capability, rather than a shared password.
Read guide ↗PlatformAuthority, deliberately.
Account identity, workspace custody and infrastructure trust are separate boundaries.
Read guide ↗OperationsTake the private path.
Public ingress and private connectivity solve different problems.
Read guide ↗OperationsKeep a credible way back.
Recovery begins with ownership and durable evidence.
Read guide ↗Build & releaseOne contract. Every boundary.
Inferred types connect the app and API; validation protects the wire.
Read guide ↗Build & releaseExplore the API contracts.
Request schemas, response schemas and security requirements generated from the canonical route declarations.
Read guide ↗