Guiding Principles

⚠️🚧 Work in Progress

This document is a work in progress. Content may change, and some sections may be incomplete.

Understanding-oriented content about design decisions and architecture

This section explores the "why" behind the ATT&CK Data Model - the design decisions, architectural choices, and trade-offs that shape the library. These explanations provide context and rationale rather than instructions, helping you understand the deeper principles that guide the project.

Dive Deeper

Foundational Context

• Why the ATT&CK Data Model Exists - The problem context, solution approach, and value proposition
• Why TypeScript Instead of X - Why we chose TypeScript
• Why Zod Instead of X - Why we chose Zod over other options
• STIX 2.1 as the Foundation - Why STIX was chosen and how it shapes the architecture

ATT&CK Specification Understanding

• ATT&CK Specification Overview - Understanding the structure and purpose of the ATT&CK specification
• Versioning Philosophy - Understanding ATT&CK's multi-dimensional versioning approach

Technical Architecture

• Schema Design Principles - Validation philosophy, refinement patterns, and extensibility choices

Miscellaneous

• Compatibility - Compatibility matrix of versions of ATT&CK, the data model, and the library
• Architecture & Design Trade-offs - Reasons why architecture decisions were made

---