Source boundaries
Evidence workflows preserve provenance, versioned outputs, immutable revision history, and reproducibility references.
R/IV / SECURITY + DATA
R/IV separates public research surfaces, customer workspaces, and private operator controls. Paid work is tied to verified commerce and server-side entitlements; private customer objects require authorization at the trusted server boundary.
PUBLIC-SAFE TRUST CENTER · PRODUCTION TRUTH ONLY[ TRUST BOUNDARIES ]
Customer material is used to deliver the requested service and is not designated for training a public or general model by default. Provider-specific handling must be verified before private data is admitted.
Evidence workflows preserve provenance, versioned outputs, immutable revision history, and reproducibility references.
Enterprise contracts require organization membership, role, scope, object permission, entitlement, policy, and approval where applicable. Production enterprise binding remains in canary.
Machine capabilities activate individually only after payment, authorization, execution, security, receipt, recovery, and economics tests pass.
[ ENTERPRISE ASSURANCE / CANARY ]
Organization policy, approvals, separation of duties, audit events, assurance packs, and governed data requests are defined and published as protected contracts. Their production identity, tenant store, approval, audit, export, deletion, and hold bindings remain limited availability until verified.
[ NO FALSE CLAIMS ]
R/IV does not claim SOC 2, ISO 27001, HIPAA, FedRAMP, GDPR compliance, an uptime SLA, data residency, SSO, SAML, SCIM, customer-managed encryption keys, penetration-test results, or third-party attestations unless they are actually in force and documented.
Enterprise customers may request the current security overview, applicable provider disclosures, retention/export/deletion process, and reproducibility information.