The product
From a request
to a record.
PraxisForge brings evidence, specialist agents and human review into one place. Follow the work from its first brief to an inspectable outcome.
HERMES-POWERED · SELF-HOSTEDOne continuous thread.
A useful outcome needs more than a fluent answer. It needs context, a deliberate decision and a record of what actually happened.
01 / Intention
Give the work a clear brief
Describe the client, the deliverable and the evidence the team may use. A request begins as a durable task, with its own history and an explicit outcome.
- A bounded request
- Selected workspace evidence
- An owner for the decision
02 / Evidence
Bring the right context
Versioned text sources give the specialists something concrete to work from. Source references travel with the proposed draft so the reviewer can inspect its basis.
- Text knowledge with provenance
- Workspace-scoped selection
- Missing context stays visible
03 / Judgment
Review the exact proposal
Read the message, intended recipient, account and commitments together. Approval belongs to that specific action and its evidence; a changed proposal needs a new decision.
- Inspect before approving
- Reject or cancel deliberately
- No implied permission to send
04 / Outcome
Keep an inspectable result
The bounded core records an approved draft and internal commitments together, then produces a receipt. Download the resulting JSON artifact for your own review or handoff.
- Internal draft artifact
- Recorded commitments
- Exportable receipt
Distinct responsibilities. Shared context.
The Orchestrator
Turns the request into a bounded plan. It identifies the deliverable, the missing information and the work each specialist needs to do.
The Researcher
Checks the selected evidence for supported commitments and unresolved details. It brings source references into the handoff instead of treating confidence as evidence.
The Operator
Prepares the proposed draft and commitments for review. In this bounded core, it has no tools for sending email, browsing accounts or administering systems.
Choose how to explore.
A public design preview
The interactive workspace uses synthetic client records. Filters, task details and approval interactions demonstrate the experience; its actions are simulated.
Open the synthetic workspaceAn authenticated operations core
The owner-operated core implements text knowledge, durable tasks, exact approvals and internal receipts. It is a bounded implementation under verification, with no public registration.
Open operations sign-inExternal tools, deliberately later
Email delivery, connected drives, messaging and third-party CRM writes are planned connector work. Familiar tool names describe the direction, not an active account connection.
See capability boundariesBuilt for work you can inspect.
PraxisForge starts with one concrete agency workflow: turn meeting and procedure evidence into a thoughtful follow-up draft and a clear set of commitments. That focus makes it possible to test the handoffs, review the proposed changes and distinguish a completed internal action from a failed or blocked attempt.
The larger platform direction includes more connectors, richer retrieval and measured improvements to specialist behavior. Those capabilities belong on the roadmap until their permissions, failure handling and verification are implemented.
A considered next step
See the operating principle at work.
Explore a synthetic client request, its supporting context and the decision it asks you to make.