Outcome-as-a-Service using Intelligence Systems. The master methodology for enterprise AI transformation: what to do, in what order, and why.
OASIS is not an implementation guide for any one practice area. That depth lives in nine companion repositories instead. Each one is maintained independently and scoped to a single Part III engineering chapter, or occasionally a closely related pair. The Companion Repository Index has the full mapping, ownership, and depth notes.
| Repository | Chapter(s) | What it covers |
|---|---|---|
| Ageis | Ch. 14 | Agentic coding delivery: the "Intelligence and Agent Engineering" discipline applied to software delivery end to end |
| Forge | Ch. 15 | Data and knowledge engineering (retrieval architectures, embeddings, grounding) |
| Loom | Ch. 16 | Human–AI workflow and experience engineering: progressive autonomy, escalation, workflow blueprints |
| Helm | Ch. 17 (light), 18 (light), 19, 21, 26 | Deployment, operations, and AgentOps (observability, release management, incident response, security containment) |
| Verity | Ch. 18 | Evaluation and reliability engineering — the fifteen-dimension evaluation methodology, statistical rigor, failure taxonomy |
| Compass | Ch. 19, 20 | Security, responsible AI, governance, and regulatory compliance across jurisdictions |
| Fulcrum | Ch. 22 | Economics, FinOps, and sustainability, covering cost and value tracking for AI systems |
| Nexus | Cross-cutting (feeds Ch. 5) | The opportunity catalog: which use case, in which domain and function, before it enters the OASIS lifecycle |
| Axiom | Background (underpins Ch. 14) | AI model architecture reference (Transformers, MoE, SSMs, and related families), not itself a chapter companion |
Known gap: Chapter 17 (Enterprise Integration and Tool Engineering) has no dedicated companion at Forge/Loom/Verity's depth yet. See the index for what light coverage exists in Helm.
This is a simple, Markdown-only GitHub package: all handbook pages live in this single folder, linked together with relative Markdown links. Open this README.md file to navigate the handbook. See CHANGELOG.md for what's changed, when, and how often the Standards and References material gets reviewed.
Executive sponsor or business owner. You want the case for committing budget, and a way to check whether it's working. Start with Chapter 01: OASIS Executive Overview and Chapter 03: Enterprise AI Transformation Direction. Then use the AI Engineering Maturity Model to see where the organization stands today. CHANGELOG.md shows what changed most recently and when it's due for its next review.
Delivery or engagement lead. You're running an initiative through the six phases. Start with Chapter 04: Multiple Entry Paths and Configurable Depth to pick the right depth, then work through Part II: The OASIS Lifecycle (Chapters 7–13) — each phase has its own diagram. Chapter 32 names the twenty artifacts you'll actually produce; their fillable versions are in Tools. If you hit an unfamiliar term or role along the way, the Master Glossary and Roles Roster will resolve it.
Architect or engineer building the system. Start with Chapter 14: Intelligence and Agent Engineering for the system equation, then read the six companion articles in the Engineering section below: Model, Context, Tool, Harness, Memory, and Evaluation Engineering. The OASIS Reference Architecture and its nine enterprise perspectives show how the pieces fit together as components. The Companion Repository Index points to the implementation-depth repository for each Part III chapter.
Security, governance, risk or compliance reviewer. Start with Chapter 19: Security and Responsible AI Engineering and Chapter 20: Governance, Compliance and Regulatory Engineering. Then read the Security: Agentic AI Threat Model and Control Checklist and the four framework-specific checklists in Standards; the Regulatory and Standards Framework Alignment Index indexes all four.
Operations or support, running a live system. Start with Chapter 21: Deployment, Operations and AgentOps, then read the Monitoring: Observability and Telemetry Specification and the Service Runbook template. Chapter 26: OASIS Measurement Framework defines what the Outcome Scorecard should track once the system is live.
- Chapter 01: OASIS Executive Overview
- Chapter 02: Methodology Foundations and Design Principles
- Chapter 03: Enterprise AI Transformation Direction
- Chapter 04: Multiple Entry Paths and Configurable Depth
- Chapter 05: Opportunity Portfolio and Transformation Horizons
- Chapter 06: OASIS Operating Model and Decision Rights
- Chapter 07: Phase 1 — Engage & Align (diagram)
- Chapter 08: Phase 2: Discover & Validate (diagram)
- Chapter 09: Phase 3: Engineer & Integrate (diagram)
- Chapter 10: Phase 4 — Activate & Adopt (diagram)
- Chapter 11: Phase 5: Operate & Assure (diagram)
- Chapter 12: Phase 6 — Optimize & Scale (diagram)
- Chapter 13: Decision Gates and Evidence Model (diagram)
- Chapter 14: Intelligence and Agent Engineering (diagram)
- Chapter 15: Data and Knowledge Engineering
- Chapter 16: Human–AI Workflow and Experience Engineering
- Chapter 17: Enterprise Integration and Tool Engineering
- Chapter 18: Evaluation and Reliability Engineering
- Chapter 19: Security and Responsible AI Engineering
- Chapter 20: Governance, Compliance and Regulatory Engineering
- Chapter 21: Deployment, Operations and AgentOps
- Chapter 22: Economics, FinOps and Sustainability
- Chapter 23: Forward Deployed Outcome Engineering
- Chapter 24: Roles, Teams and Governance Forums
- Chapter 25: Enterprise Intelligence Platform
- Chapter 26: OASIS Measurement Framework
- Chapter 27: Delivery Cadence and Management Practices
- Chapter 28: Scaling and Productization
- Chapter 29: OASIS Adoption Roadmap
- Chapter 30: Tailoring OASIS
- Chapter 31: Illustrative Use Cases
- Chapter 32: Templates, Checklists and Tools (diagram)
- Chapter 33: Appendices and Reference Material
-
Common Challenges, a 40-question challenge-to-change-to-remedy matrix across the OASIS ecosystem.
-
Additional relevant standards and frameworks are listed in the alignment index.
-
Master Glossary and Roles Roster (terms and roles across the whole repository, plus a default RACI)
-
Companion Repository Index (the implementation repository for each Part III chapter, and how far each one currently goes)
- AI Engineering Maturity Model (nine dimensions, five levels, weakest-link scoring)
- Maturity Scorecard Template (fillable, per assessment cycle)
- Architecture: OASIS Intelligence-System Reference Architecture (system diagram, design principles, enterprise perspectives)
- Architecture Principles
- Enterprise architecture perspectives:
- Engineering (Chapter 14 companion articles, in build order):
- Monitoring: Observability and Telemetry Specification
Fillable versions of all 20 artifacts named in Chapter 32, grouped by lifecycle stage:
- Outcome and Portfolio Templates: Opportunity Assessment, Outcome Charter, Outcome Contract, Outcome Metric Tree, Value and Risk Case
- Workflow and Intelligence Templates: Process and Decision Map, Human–AI Workflow Blueprint, Data and Knowledge Readiness Assessment, Evaluation Strategy and Dataset, Failure Taxonomy
- System and Governance Templates: Intelligence-System Blueprint, Autonomy Matrix, Responsibility Assignment Matrix, Decision-Gate Record
- Readiness and Operations Templates; Production Readiness Checklist, Operational Acceptance Checklist, Outcome Scorecard, Service Runbook
- Risk and Scale Templates: Risk and Control Register, Scale and Productization Assessment
Licensed under CC BY-SA 4.0. Reuse and adaptation are welcome with credit to KnowledgeTrails-OASIS, a link to the license, an indication of changes, and release of adaptations under the same license.
Shripadraj Mujumdar is an Agentic AI & Automation Strategist, Advisor, and Responsible AI Expert with 28+ years of experience in enterprise architecture and AI-driven transformation, including hands-on work in Agentic AI, Generative AI, and enterprise data and knowledge platforms. His practice covers designing multi-agent systems, knowledge-graph and RAG architectures, accelerated delivery capabilities, and Responsible AI governance frameworks aligned to global regulatory standards. This methodology ecosystem distills that practitioner experience — across architecture, delivery, evaluation, governance, and economics — into one reusable body of work.
Ankit Mirajkar is a Data & AI Architect and technology consultant specializing in modern data platforms, enterprise data architecture, and Agentic AI. His expertise spans scalable data engineering, AI-ready data platforms, Generative AI, and cloud technologies, with a strong focus on turning complex data challenges into practical, production-ready solutions. He also works across architecture, technology strategy, and innovation to help organizations build intelligent, scalable data ecosystems.