Rhiz docs
Start with the product model, then go deeper into Context, permissions, approvals, outcomes, integrations, and current proof.
Documentation map
These are current product boundaries, not promises about future features or autonomous action.
Rhiz helps a person or team understand the situation, choose a useful Move, coordinate with the right people, and learn from what actually happened.
Rhiz can help prepare a Move. Sending, publishing, paying, routing, or using sensitive information stays behind the appropriate human approval and policy boundary.
Receipts, observed results, corrections, and permissioned memory help the next decision start with better context instead of starting over.
Review the interface, authority, data lifecycle, operating responsibilities, and evidence required for your workflow.
Engineering evaluation
Start with one workflow, its accountable owner, and the result that would make the work worthwhile. Agree on permitted data and actions before connecting private systems.
General developer access and the supported API reference remain closed. An evaluation does not grant access, certify a control, or establish a service level.
Current paths