Framework¶
The Readiness Hub measures practical control and enterprise-readiness risk across five dimensions.
1. Vendor & Cloud Dependency¶
This dimension looks at whether the business is too dependent on one cloud, vendor, API, managed service, or opaque infrastructure path.
Typical questions:
- Can the core workload be redeployed elsewhere?
- Are proprietary dependencies documented?
- Is there an exit or migration path?
- Are critical vendor risks visible to leadership?
2. Data Control & Jurisdiction¶
This dimension looks at where data originates, where it is stored, where it is processed, and which jurisdictions or processors may be involved.
Typical questions:
- Do you know where customer data, logs, backups, and AI-related data are stored?
- Do you understand cross-border data flows?
- Are retention and deletion processes documented?
- Are sensitive data flows separated from analytics, debugging, and AI workflows?
3. AI / Model / RAG Control¶
This dimension looks at how AI systems handle prompts, embeddings, inference, model routing, retrieval, and vendor dependency.
Typical questions:
- What data is sent to external AI APIs?
- Are prompts, embeddings, and inference logs governed?
- Can the workflow move between managed APIs and self-hosted inference if required?
- Are cost, latency, privacy, and reliability trade-offs understood?
4. Security, Auditability & Evidence Readiness¶
This dimension looks at whether the team can prove what it has implemented.
Typical questions:
- Are critical admin and user actions logged?
- Are CI/CD and container workflows scanned?
- Can the team produce evidence for customer security questionnaires?
- Are access control, backup, and incident processes documented?
5. Portability, Resilience & Exit Readiness¶
This dimension looks at recovery, continuity, and the cost of failure.
Typical questions:
- Are backups tested?
- Is the recovery window known?
- Is infrastructure-as-code used for critical systems?
- What breaks if a vendor, region, account, or API becomes unavailable?
Interpretation¶
This framework is designed to support technical and governance conversations. It should not be treated as legal advice, certification, or an audit opinion.