Stack

bijux-atlas-ops/stack explains the operational environment in which bijux-atlas runs, including the service itself, its supporting dependencies, profile shapes, cluster substrates, overlays, and pinned toolchain inputs.

flowchart TD
    Stack[Stack operations slice] --> Topology[Service topology]
    Stack --> Components[Stack components]
    Stack --> Profiles[Profiles and deployment shapes]
    Stack --> Clusters[Kind clusters]
    Stack --> Overlays[Environment overlays]
    Stack --> Offline[Offline assets]
    Stack --> Pins[Toolchain pins]
    Topology --> Model[Whole operational system model]
    Components --> Model
    Profiles --> Model
    Clusters --> Model
    Overlays --> Model
    Offline --> Model
    Pins --> Model

This section is the operator’s system map. It explains what runs alongside the Atlas runtime, which profiles are supported, how different local or CI environments are assembled, and which dependencies are required to make the stack predictable and reviewable.

Purpose

Use this section when you need to reason about the complete runtime system rather than a single release, observability, or Kubernetes artifact.

Source of Truth

• ops/stack/*
• ops/env/*
• ops/docker/*
• ops/inventory/toolchain.json

Main Takeaway

The stack is not a backdrop. It is part of the contract. Operators need to know which components are required, how profiles assemble them, how overlays and clusters change the shape, and how that whole system is validated.

Pages

• Cache and Store Operations
• Dependency Graph
• Deployment Models
• Environment Overlays
• Kind Clusters
• Local Stack Profiles
• Offline Assets
• Service Topology
• Stack Components
• Toolchain Pins