Request
Typed intent in Account context.
Security + trust
Clear boundaries. Reviewable controls. Evidence for diligence.
Raindex keeps private work inside an explicit Account boundary and routes material actions through product-owned authority. Security and legal commitments are stated only where supporting evidence exists.
Account isolation
Private work has an owner; actions have an actor.
Each private artifact belongs to an Account. A user’s identity records who acted; it does not grant access outside that Account. Backend checks enforce scope, with data policies as a backstop.
Explicit Account request → authorization check → in-scope object or not found.
Material action
A request is not yet a result.
Supported mutations require validated intent, Preview where required, current authority, confirmation, the owning product workflow, and evidence of the durable effect.
Review
Validation and Preview where required.
Authorize
Current authority and confirmation.
Prove
Owner action, receipt, and resulting state.
Interface boundaries
One authority model across the interfaces.
UI, Agent, API, MCP, and governed authoring interfaces enter product-owned workflows. They do not become independent sources of options, policy, or authority.
Diligence material
Go directly to the maintained source.
Bring specific hosting, access, recovery, retention, AI, or contract questions to a scoped review.
Have a specific diligence question? Bring it directly to the evidence.
We’ll review the applicable current controls, documentation, and agreement language with your team.