What hardware Aura runs on, and — the part that matters — what you're allowed to claim from a run on each one.
Those two things are usually kept apart. They shouldn't be. A benchmark on an 8 GB laptop with mocked models and a benchmark on a 64 GB machine with the resident 32B are not the same measurement, and a number carried from the first to the second is just a number. Each profile below lists its allowed claims and its disallowed ones explicitly, so a result knows what hardware produced it.
- Target Hardware: Standard laptop (e.g. Intel/M1 MacBook Air), 8GB RAM.
- Required Models: None (mocks/stubs only).
- Memory/Compute: Minimal resource requirement.
- Allowed Claims:
governed runtime(static verification only)production-sealed(static gate validation)
- Disallowed Claims: All empirical claims, including
operational volition,autonomous agency,emergent intelligence,DNU AGI,synthetic cognitive entity. - Tests That Can Run:
python -m compileallpytest --collect-only- Strict Flagship Readiness check
- Production Surface Lint check
- Static Enterprise/Readiness gates
- Tests That Are Blocked: All live capability runs, agent loop tests, longevity soak, and model-dependent tests.
- Target Hardware: Virtualized CI Runner (e.g. GitHub Actions standard runner), 2-4 vCPUs, 7-14GB RAM.
- Required Models: Light local MLX-compatible models for bounded proof runs.
- Memory/Compute: Bounded.
- Allowed Claims:
governed runtime(receipt verification on light runs)persistent memory(local persistent memory writes)operational volition(bounded Will Decision receipt logging)production-sealed
- Disallowed Claims:
emergent intelligence,external real-world validation,DNU AGI,AGI-candidate,mature RSI,synthetic cognitive entity. - Tests That Can Run:
- All unit/integration tests (
pytest) - Bounded Agency Emergence proof runs (with local/mocked LLMs)
- Bounded Longevity soak (
proof_shortprofile)
- All unit/integration tests (
- Tests That Are Blocked: Full 100-task DNU AGI suite, multi-hour longevity soak, high-capacity model-reasoning evaluations.
- Target Hardware: Mac Studio / MacBook Pro (M2/M3/M4 Max), 64GB - 128GB Unified Memory.
- Required Models: the three in-process MLX tiers — Cortex (32B, foreground), Brainstem (7B, background), and Reflex (1.5B, fast lane) — plus Qwen-2.5-Coder-7B-Instruct (local) for code work.
- Memory/Compute: High-throughput CPU/GPU memory bandwidth.
- Allowed Claims:
governed runtime,persistent memory,causal internal state,affect steering,System 2 planning/search,self-repairoperational volition,autonomous agency,entity-in-a-box behaviorexperience-adjacent functional indicators
- Disallowed Claims:
DNU AGI,AGI-candidate,external real-world validation(requires independent high-horizon evaluation),indefinite autonomy. - Tests That Can Run:
- Local model-aware agency emergence batteries
- Local sandbox/boxed entity suites
- Medium-duration longevity soak (e.g.,
local_4h)
- Tests That Are Blocked: Multi-day longevity soak (e.g.,
local_72h) and high-horizon external validation.
- Target Hardware: Dedicated Workstation / Server, 128GB+ System RAM, 2x NVIDIA RTX 4090 or A6000 GPUs.
- Required Models: Aura MLX 32B/72B lane artifacts, DeepSeek-Coder-33B (local quantized).
- Memory/Compute: Massive local GPU memory allocation.
- Allowed Claims: Same as Local Apple Silicon, plus:
emergent intelligence(locally evaluated on larger distributions)
- Disallowed Claims:
DNU AGI,AGI-candidate,indefinite autonomy. - Tests That Can Run:
- Heavy local model reasoning runs
- Local System 2 search rollouts
- Longer longevity soak (e.g.,
local_24h)
- Tests That Are Blocked: Third-party benchmark gates that exceed local compute capacity.
- Target Hardware: Dedicated robotic/embodied system or developer workstation with full system access and live web interface hooks.
- Required Models: Local Cortex, Solver, Brainstem, and Reflex lanes.
- Memory/Compute: Unconstrained host access.
- Allowed Claims: Bounded by authorization/compliance profiles.
- Disallowed Claims:
mature RSI(unless sandboxed with rollback), subjective consciousness. - Tests That Can Run:
- Live browser-use and OS-control validation
- Physical or simulation co-presence integration
- Tests That Are Blocked: Bounded by environment safety profiles and authority filters.