Evidence · checked 1 November 2026
Know what supports each claim.
Provider documentation supports candidate functionality. The proposed method, architecture and benefits remain our interpretation until their application is agreed and evaluated.
Source and claim verification table
| Claim | Source | Verification and limit |
|---|---|---|
| CAE is a proposed architectural framework, not an industry standard. | Existing CAE website and repository editorial terminology policy. | Existing public positioning inspected in the browser. No independent industry acceptance or certification is claimed. |
| The discovery offer is human-led and its commercial details are to be agreed. | User brief and existing CA consultancy positioning note, 29 October 2026. | Proposed offer; availability, delivery capacity, seller identity, terms and price remain unverified. |
| The Contextual Discovery Lens and engagement model describe this initiative’s approach. | Original method, diagrams and schema prepared for this release. | Working product language and proposed design. Not a claim of patent, trademark clearance, canonical CAE ontology or a deployed engine. |
| Reusable enterprise context may make later transformation easier and less costly. | Product hypothesis stated by the owner; no customer study supplied. | Hypothesis only. Requires baseline and post-change measurement of reuse effort, delivery lead time, quality and full cost. No savings claim. |
| AWS supplies model access and agent building blocks. | Bedrock, AgentCore, Knowledge Bases. | Official overview pages opened. Service functionality is documented, but this release has no AWS integration or target-region verification. |
| AWS supports API, workflow and mediated tool policy components. | API Gateway, Step Functions, human approval example, AgentCore Policy. | Documentation opened or official search result checked. Gateway policy covers its mediated path; human decision and backend controls require implementation. |
| AWS data governance and architecture review are available categories. | Lake Formation, Well-Architected. | Official pages opened. Not a verified business ontology, audit or customer configuration. |
| Google’s current agent documentation uses Gemini Enterprise Agent Platform. | Platform overview, runtime / scale, Agent Builder index. | Official pages opened; earlier Agent Engine URL redirects to the platform scale page. Exact feature, API, release stage and region remain implementation checks. |
| Google documents API, workflow, identity and catalogue capabilities. | Apigee, Workflows, callbacks, IAM, Knowledge Catalog, Well-Architected. | Official pages opened. Knowledge Catalog naming checked; no tested integration, business authority or regional suitability inferred. |
| Microsoft documents Foundry agents and supporting architecture. | Foundry Agent Service, landing-zone reference. | Official pages opened. Overview names a preview optimiser; it is not required by the proposed map. No customer configuration or equivalence to another provider asserted. |
| Microsoft documents API management, integration and data governance. | API Management, Logic Apps, Purview. | Official pages opened. Exact tier, licences, region and feature suitability remain open. |
| The contact address is an existing recorded route. | CAE contact material and Worker CONTACT_TO / EMAIL_REPLY_TO configuration. | Address corroborated in source and on the inspected live homepage. Recipient delivery and operator response were not tested. |
| The enterprise model and worked example describe a real customer or connected service. | No source: intentionally fictional examples. | This claim is not made. Fixed synthetic data, scripted transitions and proposed architecture only. |
| Cloud selection automatically supplies compliance, authority or business results. | No supporting evidence. | This claim is explicitly rejected. Customer-owned controls and decisions remain necessary. |
Keep source evidence separate from interpretation
The cross-cloud comparison links each candidate capability directly to supporting documentation. Its customer-owned column is a CAE architectural interpretation. Documentation checked today can change; recheck before procurement or implementation. No independent provider performance benchmark, current price quotation or customer result is supplied.
Original content, diagrams and scripted animation were prepared for this release. No supplied vendor image, vendor logo, book figure or unpublished manuscript passage was reused. The stylesheet and brand mark derive from the existing CAE repository; dependency and asset review is recorded in the handoff.
Discovery, trust and measurement references
The proposed Studio, trust review views, scope index and KPI definitions are original product designs, not certified implementations of a standard. Useful reference foundations include W3C DCAT 3 for dataset and service descriptions with provenance, the NIST AI RMF core for Govern, Map, Measure and Manage, and FinOps unit economics for connecting attributed costs to useful business units. These references do not validate the proposed index or establish CAE product certification.
YOUR ENTERPRISE. YOUR NEXT CHAPTER.
Turn complexity into
a clear next move.
Bring a business question. We can discuss a discovery scope and the decisions it should support.
Start a discovery conversation