Design vendor-neutral architecture layers, deployment patterns, assurance points, and decision records.
Learning outcomes
Curriculum
The chapters are individually addressable documentation pages. You can link directly to a concept from another program, architecture decision, or implementation guide.
Connect system purpose and sovereignty dimensions to explicit architecture requirements.
Translate system purpose, sovereignty requirements, threats, and operating constraints into a vendor-neutral architecture method.
Evaluate data, model, infrastructure, operational, and evidence control as separate but connected dimensions.
Set the intended purpose, actors, assets, dependencies, lifecycle, and system boundary before selecting controls.
Separate responsibilities and describe the system consistently across logical, deployment, trust, lifecycle, and evidence views.
Separate experience, workload, knowledge, model, gateway, platform, supply-chain, operations, and evidence responsibilities.
Use context, logical, deployment, trust, lifecycle, operational, and evidence views with consistent identifiers and contracts.
Map where trust changes and where data, artifacts, requests, identities, tools, and evidence cross a boundary.
Inventory the data, models, prompts, artifacts, identities, tools, interfaces, infrastructure, and evidence that require protection.
Select deployment patterns, record trade-offs, and preserve the practical ability to change direction.
Compare public cloud, private cloud, on-premises, hybrid, edge, restricted-network, and air-gapped patterns without treating one as automatically sovereign.
Record context, options, control consequences, evidence, dependencies, limitations, and reversal triggers for material decisions.
Design and test the ability to change models, runtimes, data stores, infrastructure, providers, and operating arrangements.
Place control objectives and evidence at the architecture points where material decisions are enforced.
Translate sovereignty goals into testable statements of what must be allowed, prevented, approved, observed, retained, and recovered.
Design evidence alongside controls so important decisions, releases, configurations, and operating events can be verified.
Produce a defensible reference architecture and test its completeness and traceability.
Create and defend a multi-view sovereign AI architecture, decision set, control map, evidence map, and readiness backlog.
Verify architecture completeness, traceability, boundary control, decision quality, portability, operability, and evidence coverage.
Produce and defend a multi-view reference architecture and decision set.
Design exercise; executable implementation pending
This public curriculum provides a vendor-neutral architecture method and review structure. It is not a production design approval, vendor certification, or substitute for workload-specific engineering, security, legal, and operational review.