Idea 01
IR, the source of truth.
One intermediate representation, tool-neutral, that code, tests, and proofs are generated from. Change the IR, regenerate the outputs; nothing drifts.
One IR in. Ten kinds out: code, tests, proofs.
Strevian Forge
Idea to ship, with a person at every gate.
Forge is the AI-powered development platform we build Strevian with. Six phases, fourteen flows, sixty-two modules, one loop.
6 phases, 14 flows, 62 modules.
In internal use today. Greenfield only in v1. Public when mature.
What Forge is
A portfolio, a loop, and a wall.
Forge takes a product from idea to ship and keeps it running afterward. Everything happens in the context of a portfolio node: an organization, a team, a product, a feature. What a parent decides, a child inherits, and Forge shows you the cascade before you change it.
Four phases move forward: Define, Create, Build, Grow. Two run continuously once anything is live: Learn and Operate. What they learn feeds the next definition, which is why the mark is a loop.
Agents do the routine work behind a wall that every commit has to pass. A person makes the decisions and reads every diff.
Portfolio Canvas
- Node
- Hollis & Co / Product / Ledger
- Permissions
- 4 resolved, 3 inherited
- Tokens
- 3 resolved, 2 inherited
- Environments
- preview
- Cascades to
- 2 nodes
Interface fragment.
The Loop Explorer
The taxonomy as a place you can walk through.
Every phase, flow, and module below is the real taxonomy Forge is built from. Open a phase to see its flows, open a flow to see its modules, and find any module by name.
6 phases14 flows62 modules
DefineCreateBuildGrowLearnOperate
Forge is used internally today. Public release when mature.
Four ideas
What makes Forge different.
Idea 02
Impact preview before commit.
Before a node moves, a permission changes, or anything is deleted, Forge shows what it would touch. Then it asks.
Node Manager
- Organization Hollis & Co1 actor assigned3 tokens declared
- Team Product1 actor assigned
- Product Ledger1 actor assigned1 token declared
- Feature Invoices1 actor assigned
- Feature Reminders2 actors assigned1 token declared
- Team Ops0 actors assigned1 token declared
- Product Console1 actor assigned
- Feature Audit log2 actors assigned1 token declared
Impact preview
Choose a control to see what it touches
Sample data. Nothing you do here is saved.
Idea 03
MCP surfaces.
Forge exposes its services to agents and tools through MCP Studio, so the same mechanism serves a person in the UI and an agent in a pipeline.
Idea 04
The loop.
Insights and Feedback feed Vision and the Prioritizer. Learning goes back to the beginning.
Learn feeds Define
The wall
Ten stages on every commit. Nothing merges past them.
Every stage runs on every commit, in order. CI blocks any merge that fails one. Then, and only then, a person reviews it.
Every file formatted the same way, or the commit stops here.
format:check
The tenet rules as lint: compose on primitives, preview before commit.
lint
TypeScript at its strictest. No implicit anything.
typecheck
Packages import only what the layering allows. Cycles are failures.
fitness
The wall proves its own checks still catch a planted violation.
proof
The suite runs. Every test is meaningful or it is deleted.
test
A ratchet that only tightens. Coverage never goes down.
coverage
Real browser flows, recorded as proofs a human can watch.
test:e2e
Copied code is flagged. One mechanism, many uses.
duplication
Secrets, known vulnerabilities, and license risks. Blocked, not warned.
security
HUMAN REVIEW. THE FINAL GATE, NOT A STAGE.
Past the tenth stage, a person reads the change. Nothing merges on green alone.
Commite41b7c0
10Security
MERGE BLOCKED. NOTHING DOWNSTREAM RUNS.
Interface fragment.
FIRST EXECUTION OF THE WORKFLOW GUARD: 5 REAL SECURITY DEFECTS CAUGHT.
Who decides
Different models for different jobs. One person for the decisions.
Forge allocates models by task: some are good at generation, some at review, some at classification. Humans rule on every checkpoint. Every action is logged, so accountability never blurs. One mechanism serves many uses, and adding a new one requires written justification.
HumansAI
Decide the architectureGenerate the code and tests
Set what mattersFlag what breaks
Approve every mergeSelf-review first
Rule on checkpointsRun the routine work
Own the outcomeLog every action
Changelog
Building in the open.
Dated, true, and one line each: the decisions, checks, and modules as they land.
- Standard
Quality model Q1 to Q12 added: the ladder from impossible to detected to tested to reviewed to production.
- Standard
Agent-operations standard A1 to A12: how an agent-operated development ecosystem is stood up and run.
- Decision record
ADR-0030 addendum: Forge v1 is greenfield-only. Brownfield import is a deliberate v2 decision, not a silent absence.
- Decision record
ADR-0030: architecture batch-apply. Two-tier platform census locked, Notification Hub and Integration Hub added.
- Decision record
ADR-0027 to 0029: UI stack re-chartered on the Tactile design system, build commit type, tighten-only coverage ratchet.
- Wall check
Delivery wiring merged to main. All four required checks green on the first protected merge.
- Design system
Self-describing repo: architecture snapshot and MAP.md so an agent with only the repo can read the specs.
- Design system
Tactile accepted as the Strevian design system from nine rendered directions. Warm paper, squash physics, the glow is truth.
- Wall check
Workflow guard CHK-28 live. It caught five real security defects on its first execution.
- Standard
Engineering standard locked: R1 to R20, the check catalog, security baseline, git conventions, model allocation.
- Forge module
Portfolio Canvas: all seven cluster decisions locked.
- Forge module
Flow architecture: 14 flows across 6 phases documented as the parent reference for every spec.
Status and waitlist
Used internally to build Strevian. Public when it is mature.
Forge is in internal use today and greenfield-only in v1. Join the waitlist and you will hear from Wesley when it is ready for more hands, and not before.
Questions
Four short answers.
01When will Forge be public?
When it is mature. It builds Strevian today; that is the test it has to pass first.
02Who is it for?
Solo developers and small teams building a product from scratch. Forge v1 is greenfield-only.
03What will it cost?
Not decided yet. When it is, it will be on this page, in the open, like the services.
04Do I need Forge to work with Strevian?
No. Every project uses the same standard and pipeline, and everything it produces is ordinary code in a repository you own.