Architecture Decisions

This section records the implementation decisions that shape AuroraSOC's flagship architecture.

These pages are intentionally normative. If code or documentation disagrees with a decision record, the mismatch must be resolved in the same pull request.

Active Decision Set

Frontend and Analyst UX

AuroraSOC is allowed to fully redesign the dashboard and analyst workflows when the current UI does not meet enterprise SOC expectations.

The current frontend stack remains valid as a foundation, but the user experience is not treated as fixed.

See Frontend UI Strategy.

Runtime Modes and Demo Data

dummy mode is the only mode that may serve showcase data.

dry_run and real mode must use live backend state for read flows and must fail clearly when required services are unavailable.

See Runtime Modes and Data Fallbacks.

Rust Fast Path

rust_core is not part of the default AuroraSOC runtime profile.

It may remain as an optional accelerator only if it is explicitly benchmarked, supported, tested, and documented as such. Otherwise its responsibilities should be absorbed into the Python backend.

See Rust Core Decision.

Repository Runtime Surfaces

The infrastructure/ directory is a first-class runtime and operations surface, not a dump of incidental configs.

The scripts/ directory is a first-class bootstrap, validation, and operator automation surface, not an unowned collection of helper scripts.

These directories must evolve with the same discipline as application code and documentation.

Review Rule

Any pull request that changes runtime topology, frontend foundations, operation modes, or rust_core expectations must update the relevant decision page in this section.