Data handling

Overview

SupraOS is designed to coordinate work across existing systems without requiring unnecessary duplication of sensitive source data.

What may remain in customer systems

• Operational records
• Tickets and communications
• Underlying documents and files
• Log and telemetry systems
• Approval artifacts already stored elsewhere

What SupraOS may store

• Structured workflow / work-object state
• Approvals and workflow status
• Evidence references and selected artifacts
• Receipt / proof objects
• Policy and execution metadata
• User-entered workflow context and generated outputs as required by the workflow

Design goal

The goal is to keep sensitive data movement and duplication to the minimum necessary to run the workflow and produce the required proof.

Data categories

Website and pre-sales data

• Contact form submissions
• Updates signups
• Business contact information
• Communications regarding access requests

Product/workflow data

• Workflow state
• Tasks and approvals
• Evidence references
• Receipts / proof objects
• Generated operational or executive outputs

Sensitive information

Sensitive source artifacts can remain in customer-controlled systems while SupraOS stores only the structured state and proof required for governed execution and verification.