Architecture / AIGIS resources
AIGIS treats model choice as a routing decision after governance, not as the foundation of the permission model.
Executive read
Governance should not depend on one model vendor.
Customers can bring model keys where deployment supports that path.
Model routing should be recorded as part of provenance.
Cost control improves when not every request needs a premium model.
Analysis
The same permission path should apply whether the answer is generated by Claude, GPT, Gemini, Bedrock, or a private model.
AIGIS separates the governance path from the model path so model changes do not require rethinking the permission boundary.
The audit record should show which model route was used after context was governed.
That gives buyers a clear story about quality, cost, and risk without turning model choice into a black box.
Resource packet
Evidence packet
Capture user context, system of record, enforcement tier, stripped fields, model route, response, hash marker, and fallback notes.
Salesforce is the production proof path. ServiceNow and SAP are design-partner co-development paths with asymmetric enforcement that must be disclosed in diligence.
Keep reading
Architecture
How a governed runtime shapes identity, permissions, context, model routing, and evidence before AI answers.
Architecture
How AIGIS governs requests across chat surfaces, API-accessible systems, execution paths, and model-agnostic LLM deployments.