Pilot data boundary
Data Requirements
Raven can begin with limited, approved exports. The goal is to understand decision exposure without asking for unnecessary production access, sensitive credentials or customer personal data.
Audience CTO / security / data owner
Mode minimum necessary
Boundary no credentials here
Useful Inputs
Incident historyTicket exports, incident timestamps, status changes, escalation points and resolution notes help identify candidate decision windows.
Service contextService groups, regions, asset classes, customer-impact classes and support hours help Raven place signals in an operational context.
Event exportsCSV, XLSX, JSON or sanitized log exports can be reviewed when the client approves source, period and retention.
Cost assumptionsKnown downtime cost, SLA impact, dispatch cost or internal priority models can improve business interpretation.
Do Not Send
sensitive credentialsNo passwords, API keys, VPN credentials, private certificates, admin accounts or privileged tokens.
Unapproved personal dataNo unnecessary customer personal data, employee personal data or raw subscriber data.
Production write accessNo production mutation, no uncontrolled collector and no live action path for an initial review.
Undefined retentionNo customer data should be transferred before retention and deletion expectations are agreed.
Pilot Data Modes
SyntheticSynthetic or public-safe examples can validate the decision surface before client data is used.
HistoricalHistorical exports can be used to test evidence packets and lead-time hypotheses.
Read-onlyA read-only pilot can observe and prepare recommendations without executing actions.
ProductionProduction integration requires a separate security, legal, support and rollback gate.
Persistence Boundary
Initial reviewOffline review can begin from approved exports without customer database access or production credentials.
Customer persistenceDurable tenant data storage requires DPA path, retention rule, deletion/export path, backup/restore proof and audit owner.
Migration readinessSchema drafts are not applied. A migration must be promoted, reviewed, versioned, reversible and tested with synthetic data.