Forge Manifesto
Why Forge exists.
The last generation of developer platforms optimized for engineers writing code.
Forge optimizes for Builders creating software.
Software has always been shaped by its tools.
Compilers changed programming.
IDEs changed development.
Cloud changed deployment.
AI changes who builds.
Forge changes what a developer platform should be.
Software Is Built, Not Written
Writing code is one activity.
Building software is the craft.
Building includes understanding problems, shaping Goals, selecting Capabilities, producing Resources, learning from Events, and improving the system over time.
Code is one artifact.
Software is the outcome.
Builders Create Software
Engineers build.
Designers build.
Product managers build.
Researchers build.
Security engineers build.
Infrastructure engineers build.
Agents build.
Different expertise.
One identity.
Builder.
Builders Pursue Goals
A Builder does not start with infrastructure.
A Builder starts with a Goal.
Add support for larger uploads.
Reduce latency.
Release safely.
Investigate a regression.
Improve quality.
Forge exists to turn Goals into progress.
Agents Are Teammates
Agents are not features.
Agents are not autocomplete.
Agents are Builders with different strengths.
Humans provide judgment.
Agents provide leverage.
Both operate through the same platform.
Forge Builds the Software Factory
Builders build software.
Forge builds the factory they build it in.
The factory should be powerful.
The factory should be safe.
The factory should disappear.
If Builders spend more time thinking about Forge than the software they are creating, Forge has more work to do.
The Future
The first generation of developer platforms managed code.
The next generation will coordinate Builders, Goals, Capabilities, Resources, Events, Policies, and Permissions.
The first generation accelerated developers.
The next generation will multiply Builders.
Forge is not adapting to that future.
Forge is built for it.