ForgeClaw
ForgeClaw is not an off-the-shelf download. It is the private engagement surface for custom autonomous operations work: routing systems, specialist agent councils, workflow hardening, and operator infrastructure built around a real working environment.
// engagement_position
ForgeClaw engagements are private by default.
ForgeClaw work is scoped around the buyer's actual workflow, not a generic SaaS checklist.
ForgeClaw remains proprietary and under active internal development.
Public chronicles explain the lineage. Private work focuses on applying the pattern: orchestration, memory, routing, validation, and operational control for teams or solo operators with real workloads.
Why This Is Private
Operator systems are contextual
Routing rules, memory surfaces, tools, credentials, hardware, and deployment habits all shape the result. A useful ForgeClaw engagement starts from the actual operating environment.
The value is in the harness
The product is not a pile of prompts. It is the connective tissue: authority loading, handoff contracts, validation gates, durable memory, and recovery behavior.
Open substrate, private leverage
Where upstream OpenClaw is the right substrate, Greyforge aligns with it. The private engagement focuses on what belongs around it for the operator.
Serious systems need maintenance boundaries
Custom orchestration must be scoped, documented, and handed off with clear ownership. That is why this is sold as an engagement, not a casual download.
What You Can Buy
ForgeClaw engagements can cover autonomous operations architecture, specialist routing, memory and context systems, validation gates, local tool integration, and handoff workflows.
The commercial boundary is deliberate. Public utilities can ship through OpenForge. Private leverage belongs in scoped systems, private policies, private routing, and deployment practices that match the operator.
Supporting utilities that stand on their own still ship publicly through OpenForge. The operator-specific layers do not.
Private by default
ForgeClaw is sold through scoped private engagements. The public route explains the product boundary and points to the proof lineage.
History stays public
The ForgeClaw chronicles remain online because the build history matters. They show the lineage behind the private engagement surface.
Build An Operator System That Fits The Work
ForgeClaw engagements start with scope: current workflow, risk tolerance, toolchain, handoff needs, and what must remain private.
Request ForgeClaw Scope ReviewRead The Lineage
The public record now starts with the policy notice, then points back to the original fork and rebuild chronicles for context.
Retiring the Fork
The public policy change, the upstream OpenClaw alignment, and why ForgeClaw is now a private system.
Building ForgeClaw
Why the fork was created and what the first workable architecture looked like.
The Reckoning
How the fork sprawled, what the rebuild taught us, and where the maintenance burden became impossible to ignore.