Why PraxisForge
More intention
in everyday work.
PraxisForge is an independently built exploration of a practical question: what makes an AI-assisted business outcome understandable enough to trust?
HERMES-POWERED · SELF-HOSTEDThe gap between an answer and an outcome.
A fluent response can make work feel complete before anything has been verified. A useful operational system needs a more concrete trail: the request, the evidence it was allowed to use, the person who approved the proposed action and a record of the result.
PraxisForge begins there. It brings specialist roles into a workspace designed around deliberate handoffs, visible boundaries and human judgment. The first bounded workflow focuses on agency follow-up drafts and internal commitments, where both the context and the decision can be inspected.
The principles behind the interface.
Context before confidence
A recommendation should point back to its permitted sources. Missing evidence deserves a clear blocked outcome, not a more persuasive sentence.
Judgment before execution
The reviewer should see the actual proposal. Approval should mean a specific decision about a specific action, with a defined account, recipient and evidence boundary.
Evidence after action
An outcome needs a record. Internal changes and external provider acceptance are different claims; the product should make that distinction legible.
Calm throughout
Clear typography, considered pacing and restrained motion help people inspect work. The interface should give attention back to the decision that matters.
A platform direction with a concrete starting point.
Hermes-powered roles
The bounded core integrates Nous Research’s Hermes Agent through a constrained specialist workflow. PraxisForge is independently built; it is not presented as an official Nous Research product.
Self-hosted direction
The implementation is designed around an owner-operated environment and configured local inference. That choice does not remove the need for authentication, validation, recovery and careful operations.
An honest roadmap
The public preview, bounded core and planned connectors have different readiness levels. We describe them separately so the ambition does not obscure what has actually been built.
Read the changelogA considered next step
Meet the product through the work.
Start with a brief, inspect its sources and see where the next decision belongs.