Pilot intake
Pilot Intake
The intake exists to prevent a vague pilot. Raven needs an operational owner, a decision owner, a security boundary and a narrow incident class before work starts.
Audience pilot sponsor
Duration usually 30 days
Mode scoped before data
What Raven Asks For
SponsorThe person who can define why the pilot matters and what decision problem should be measured.
Decision ownerThe person who can approve or reject a recommendation inside the pilot boundary.
Security ownerThe person who approves transfer method, data class, retention, deletion and support access.
Incident classA narrow operational class, such as waiting cost, degradation, dispatch uncertainty, escalation delay or evidence quality.
Controlled Data Intake
Allowed evidenceCSV, XLSX, JSON, LOG or TXT exports for incident history, dispatch, ticketing, monitoring exports or billing summaries.
Required metadataTenant, file id, data class, transfer mode, retention category, DPA reference, audit reference, file hash and malware scan state.
Personal dataCustomer personal data requires a separate approved customer-data gate before Raven can process it.
No live accessVPN access, production credentials, private keys, provider write permission and raw customer databases are not requested by the public pilot intake.
Pilot Package Boundary
Manifest firstA pilot package can be prepared only when scope, evidence register, model register, limitation statement, audit reference, export gate and owner approval are present.
Customer evidenceCustomer-data modes also require upload gate, workspace readiness and retention policy before packaging.
Personal dataDPA and redaction gates are required before personal-data-relevant evidence can enter a pilot package.
Public siteThis page does not register a manifest, generate packages, write files, create exports, notify anyone or deliver reports.
Pilot In 30 Days
Week 1Boundary, data mode, decision owner, success criteria and operational vocabulary are confirmed.
Week 2Historical or synthetic evidence is reviewed and candidate decision packets are prepared.
Week 3Raven and Mira outputs are validated with operators, managers and security stakeholders.
Week 4Pilot review separates observed evidence, estimates, open questions and production-readiness gaps.
Expected Output
Evidence packetWhat was known, estimated, assumed and unknown when a decision could have been prepared.
Decision packetProblem, evidence, options, recommendation, boundary, approval owner and follow-up review.
Pilot reportFindings, limitations, KPI hypotheses, confidence level and next-step recommendation after manifest and owner review.
No outcome assertionThe pilot validates whether decision delay is measurable. It does not state savings, ROI or incident prevention.