For Developer
Start coding with the decisions already attached.
Most AI tooling promises speed and hands you a transcript. Praxis hands you a resolved package — requirement, design, contracts, budgets — and closes on evidence a person can inspect.
01
Less hype, more checkable work
A fast patch is hard to trust when you have to reconstruct acceptance from a transcript. You need to know which work package is current, what the Architect decided, which repository is in scope and what evidence the next reviewer expects.
02
Why a faster assistant isn’t enough
The handoff may reference files in a separate product repository. Neither a ticket link nor a handoff JSON alone makes those files available. Before coding, inspect the selected package, its referenced design and the local code context. Resolve missing or stale inputs with the owner.
03
You become the product engineer
Receive Architect’s prepared WP, connect the chosen code checkout, and confirm the package identity and acceptance. Research the affected code, plan the bounded change, implement it, then record the commands and results that actually ran. Request Quality Harness review of the result. Applying that review and publishing with Git are separate decisions; publication leaves a PR or MR awaiting review and merge.
04
What you actually get
- 01
Linked input
Accepted scope, selected decisions, contracts and constraints rather than a bare ticket.
- 02
Repository choice
A source-tool path can read a separate design directory; current Runtime expects its design and manifest inputs in the selected
repo. The handoff requires explicit preparation. - 03
Conditional assistance
Use research and specialist agents when needed. No fixed six-agent launch applies to every request.
- 04
Evidence with limits
Show passed, failed and skipped checks for this operation. No universal verdict or automatic commit pin is promised.
The case
Digital Winery illustrates why product intent and implementation need a durable connection; it is not evidence that today’s Runtime operated the historical project.
05
Proof you can open
Open the WP and its referenced files, the code diff, the implementation record and the Quality findings. Confirm which approval remains before publishing or applying a result.
Install it and see
Start with the Claude Code CLI setup, or use the Developer workflow guide for the documented local path.