Rhiz docs

Understand how Rhiz governs context, action, proof, and memory.

Start with the product model, then go deeper into Context, permissions, approvals, outcomes, integrations, and current proof.

Documentation map

Read the part of the system that changes your next decision.

These are current product boundaries, not promises about future features or autonomous action.

  1. 01 · Product model

    Start with the outcome, then see the path that can move it.

    Rhiz helps a person or team understand the situation, choose a useful Move, coordinate with the right people, and learn from what actually happened.

    Read the product model
  2. 02 · Context and authority

    Identity says who you are. Context says what you may do.

    Rhiz keeps people, participation, governed Context, and permission distinct so access does not become a vague role label or a hidden assumption.

    See how authority works
  3. 03 · Actions and approvals

    A useful proposal is not an action taken on your behalf.

    Rhiz can help prepare a Move. Sending, publishing, paying, routing, or using sensitive information stays behind the appropriate human approval and policy boundary.

    Read the safeguards
  4. 04 · Proof and memory

    A response is not an Outcome until the evidence supports it.

    Receipts, observed results, corrections, and permissioned memory help the next decision start with better context instead of starting over.

    See the governed loop
  5. 05 · Engineering evaluation

    Evaluate one integration before committing to it.

    Review the interface, authority, data lifecycle, operating responsibilities, and evidence required for your workflow.

    Review the integration

Engineering evaluation

A clear boundary for the first integration.

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.

Interface and authority
Rhiz provides an MCP connection for compatible assistants. A partner integration needs its own agreed interface and delegated authority. A member login or token does not establish authority to act for an organization.
Data and withdrawal
Agree on fields, purposes, providers, retention, and withdrawal behavior. Data export and account deletion are handled by request today; the privacy policy explains how to request them. Review completion evidence for the agreed data scope.
Reliability and operation
Define retry and reconciliation behavior, workload and cost limits, incident ownership, recovery, and how to disconnect. Agree on support and service commitments for the selected scope.
Acceptance evidence
Require the tested revision and environment, allowed and refused operations, persisted results, revocation, and failure recovery. An illustrative workflow, source test, or system activity count alone does not establish a completed customer outcome or production readiness.

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

Choose the next path that is real today.