Praxis is a proprietary agentic framework. It is the independent layer that proves AI-produced work, whatever the work is and whatever model made it.
Documents. Code. Analysis. Artifacts. One standard of proof across all of them.
This repository is documentation. Praxis itself is closed source and access-gated. Nothing here is the product. This is the explanation of it, kept public so you can evaluate the idea before you talk to us.
Slow and sure, or fast and blind.
You could prove every line and miss the window. You could ship by Friday and spend the next quarter finding out what you shipped.
Then AI made everyone fast. It made no one sure.
Output got cheap and proving it is right became the hard part. A model will write you anything. It will invent a capability that does not exist, quietly reverse a decision it made three steps ago, forget which constraint was binding, and hand you all of it in the same confident register as the parts it got right.
You will not catch that by reading. The output is written to read as though someone already had.
So we stopped asking the maker to grade its own work.
Praxis is the framework. It is not one pipeline and it is not one deliverable.
The framework is domain-independent by construction. Same proving machinery, a new spec each time, whether the work is a document, a codebase, an analysis or an artifact. What gets built on top of it is where the domains live.
CRAFT is the first thing built on it. The dossier is what a CRAFT run hands you. Neither one is the whole of Praxis, and more will ride the same framework without forking it.
The speed of AI. The proof it never had.
Anti-vibe coding is the discipline, and CRAFT is that discipline made executable. One pipeline, five stages, and the same spec running through every one. Each stage passes before the next opens.
| Stage | ||
|---|---|---|
| C | Capture | A rough ask becomes a spec you can read and check. The requirements, the numbers that matter, the shape of the thing. Anything vague gets named as vague. Nothing slips through as an assumption. |
| R | Rehearse | The spec becomes checks that decide pass or fail, before a line is written. You settle what "done" means up front, so the work has something real to answer to. |
| A | Author | Code gets written against the spec and reviewed as it is written, rather than days later in a queue. Anything that drifts is turned back before it hits your branch. |
| F | Field | It goes live under rules read straight from the spec. Not written a second time by hand and hoped to match. |
| T | Track | Every target you set at Capture gets a live signal in production. What you promised is what you watch. |
A river runs fast because it has banks. Take them away and you get a swamp.
Vibe coding is the failure mode where informal English goes in and whatever comes back gets accepted, because checking it properly is more work than writing it was. Anti-vibe coding is not "no AI writes code." It is AI writing from a spec good enough that we can prove the code conformed.
Full walkthrough at ourpraxis.com/craft and anti-vibe-coding.
| The maker | Agentic. It makes the work and checks itself as it goes, against the spec and against what was actually asked. That is the honest first pass, and it cannot see its own blind spots. |
| The pilot | It re-checks every step against the spec. Not a second opinion, but a re-derivation, and it cannot be argued with. It passes nothing it cannot tie back to the spec. |
| The watcher | Outside the system entirely. It answers to the spec, not to the pilot, checks the result from scratch, and holds back anything that cannot show it conformed. It is not persuaded by a pass it did not compute. |
Three progressive checks, not one. Remove any one and the proof collapses, which is the point of there being three.
Every run ends in a record, not a promise.
You enter CRAFT at a different stage depending on what you arrive with.
| You arrive with | Door | What happens |
|---|---|---|
| An idea, nothing written down yet | /founders | You do not need a finished brief. Praxis pressure-tests a raw idea, tells you honestly whether it is worth building, and shapes what survives into a spec you can audit and build from. |
| A document, an RFP or SOW or tender | /bids | Turn it into a spec you can audit and a proposal you can defend. Every requirement named, every estimate tied to it, every gap surfaced before you commit to a price. The spec you bid is the spec you build. |
| A codebase, work already under way | /engineering | Code gets written against a spec and refuses what drifts, so the review that used to eat your afternoon happens at commit. The speed of AI, without the read-through tax. |
Not a summary. A dossier you can hand a client.
One dense document holding the specification, the technical design, the infrastructure, the low-level design, the delivery plan, and dozens of diagrams. Every claim ties back to a requirement. Every requirement ties back to a sentence in the ask.
A one-page summary reads well and falls apart the moment someone technical asks why. The dossier is built the other way around. Dense, because that is what holds up in the room.
Eight parts, one argument.
| Executive summary | The problem, the proposed solution, and why it holds, on the opening pages. |
| Technical design narrative | The architecture and the reasoning behind every call. What was chosen, what was ruled out, and why. |
| Infrastructure | What runs where, how it scales, and what holds when a part fails. |
| Delivery approach | The method, the gate each phase has to clear, and how the work is governed. |
| Team resourcing | Who does the work, how the roles cover the scope, and how continuity holds. |
| Low-level design | The system drawn down to the component. How a request moves, how state changes, where data goes. |
| Project plan | The schedule, the milestones, and the critical path, with concentration risks named up front. |
| Technical appendix | Requirements traced to source, decisions justified, assumptions logged, risks and compliance accounted for. |
Where words get heavy, Praxis draws. Architecture views for both the engineer and the buyer, sequence flows, state lifecycles, data maps, network topology and failover, and a traceability matrix a reviewer can audit at a glance. Every diagram ties back to a requirement.
More at ourpraxis.com/dossier.
Praxis is not a wrapper around somebody else's agent. It is not a prompt library and it is not a linter with ambitions.
The maker is swappable, frontier or open weight, hosted or on hardware you own, because the checking was built here and holds no model inside it. Change the model and the proof does not move.
Every decision traces to a written spec, on the model and the ground you are allowed to use. The audit trail is made as the work happens, not reconstructed for the meeting. When the regulator asks why, the answer is already on record.
- Not an RFP tool, a bid tool, or a consultancy tool. A document is one of three doors into CRAFT, and CRAFT is one thing built on Praxis.
- Not "for architects", "for CxOs", or "for developers." Praxis has no persona tier. Anyone shipping AI-produced work that has to hold up is in scope.
- Not a wrapper around one vendor's agent. The framework is ours, and the checking holds no model at all.
- Not a linter, a style checker, or an AI detector. It checks whether the work answers to its source, not whether it reads nicely, and not whether a machine wrote it.
- Not a benchmark score. A verdict on this work, against this source, recorded.
Praxis is access-gated. Not open source, and not self-serve.
Tell us what you would put through it. Send a note from ourpraxis.com/contact, or email access@ourpraxis.com directly. A person reads every message and replies. There is no drip sequence and no sales bot.
Full detail in docs/access.md.
| docs/what-is-praxis.md | The long version. The framework, the pipeline, the three checks, and where it runs. |
| docs/access.md | How access works, what to send, and the practical questions. |
| ourpraxis.com/craft | The five stages, each with its own page. |
| ourpraxis.com/see-it | A live check, in your browser. Nothing is uploaded. |
| ourpraxis.com/proof | What a finished run leaves behind. |
Documentation in this repository is © Praxis. Issues are open if something here is unclear or wrong. Pull requests are not accepted, since this repository mirrors documentation maintained elsewhere.