refactor: Enhance architecture documentation with detailed sections on purpose, constraints, runtime view, deployment, and key concepts; add implementation plan and update quickstart reference

docs/architecture/08_concepts.md

@@ -1,8 +1,46 @@
+---
+title: "08 — Concepts"
+description: "Document key concepts, domain models, and terminology used throughout the architecture documentation."
+status: draft
+---
+
 # 08 — Concepts
 
-Status: skeleton
+## Key Concepts
 
-Document key concepts, domain models, and terminology used throughout the architecture documentation.
+### Scenario
+
+A `scenario` represents a distinct mining project configuration, encapsulating all relevant parameters, costs, consumption, production outputs, equipment, maintenance logs, and simulation results. Each scenario is independent, allowing users to model and analyze different mining strategies.
+
+### Parameterization
+
+Parameters are defined for each scenario to capture inputs such as resource consumption rates, production targets, cost factors, and equipment specifications. Parameters can have fixed values or be linked to probability distributions for stochastic simulations.
+
+### Monte Carlo Simulation
+
+The Monte Carlo simulation engine allows users to perform risk analysis by running multiple iterations of a scenario with varying input parameters based on defined probability distributions. This helps in understanding the range of possible outcomes and their associated probabilities.
+
+## Domain Model
+
+The domain model consists of the following key entities:
+
+- `Scenario`: Represents a mining project configuration.
+- `Parameter`: Input values for scenarios, which can be fixed or probabilistic.
+- `Cost`: Tracks capital and operational expenditures.
+- `Consumption`: Records resource usage.
+- `ProductionOutput`: Captures production metrics.
+- `Equipment`: Represents mining equipment associated with a scenario.
+- `Maintenance`: Logs maintenance events for equipment.
+- `SimulationResult`: Stores results from Monte Carlo simulations.
+- `Distribution`: Defines probability distributions for stochastic parameters.
+- `User`: Represents application users and their roles.
+- `Report`: Generated reports summarizing scenario analyses.
+- `Dashboard`: Visual representation of key performance indicators and metrics.
+- `AuditLog`: Tracks changes and actions performed within the application.
+- `Notification`: Alerts and messages related to scenario events and updates.
+- `Tag`: Labels for categorizing scenarios and other entities.
+- `Attachment`: Files associated with scenarios, such as documents or images.
+- `Version`: Tracks different versions of scenarios and their configurations.
 
 ## Data Model Highlights