The Laws of Forge
These are not guidelines. These are the laws that govern Forge.
The Laws are timeless. They describe what must remain true even as technology changes.
Software Is Built, Not Written
Writing code is an activity.
Building software is the craft.
Forge optimizes the craft.
If You Create Software, You Are a Builder
Humans build.
Agents build.
Services build.
Different forms.
One identity.
Builder.
Builders Pursue Goals
A Builder starts with a desired outcome.
The Goal is the source of work.
Do not confuse the Goal with the mechanism.
Capabilities Perform Behavior
A Capability is what Forge can do.
Plan.
Build.
Test.
Evaluate.
Deploy.
Observe.
Capabilities are behavior.
Resources Represent State
A Resource is what exists.
Builds.
Deployments.
Artifacts.
Evaluations.
Workspaces.
Resources are state.
Events Record Facts
Events describe what happened.
They do not ask for action.
They do not contain intent.
They are immutable facts.
Policies Govern
Policies decide what is allowed, required, blocked, or escalated.
Policies protect Builders, Resources, and the software being created.
Permissions Authorize
Permissions answer who may act.
Permissions are relationships between Builders and Capabilities or Resources.
Builders Own Outcomes
Agents increase leverage.
Automation increases speed.
Responsibility does not move.
Builders own outcomes.
Every Decision Helps Builders Build
Every feature.
Every Capability.
Every Resource.
Every Policy.
Every Permission.
Every architecture choice.
Every pull request.
Answers one question:
> Does this help Builders build?
If yes, continue.
If no, remove it.
These are not guidelines.
These are the laws that govern Forge.
Does this help Builders build?
Does this help Builders build?
If yes, continue. If no, remove it.