AAF-0 — Ambient Attractor Foundations
The pre-behavioural layer beneath Ambient Attractor Commerce and Ambient Navigation. AAF-0 defines why applications lose primacy before behaviour, interaction, or commerce begin.
1. The App Paradox (Smartphone-Era Bug)
The smartphone era assumed the world was neutral and that action began with a container.
Applications required:
- explicit intent (“what do you want to do?”)
- manual context switching
- abstract software disconnected from place, body, or situation
This made interaction cognitively expensive and thermodynamically unstable. Attention was forced to work against its environment.
2. Before Apps, There Are Fields
Ambient OS rejects the assumption of a neutral world.
In lived reality, attention always attempts to stabilise into attractor fields — patterns of relevance, limitation, and meaning that exist before any interface appears.
Behaviour does not begin with execution. It begins with thermodynamic settling.
3. Locations Are Multi-Field Systems
A location is not a single context. It is a multi-field attractor system.
A university simultaneously contains:
- Purple — infrastructure, systems
- Blue — information, clarity
- Pink — mentorship, relation
- Yellow — ignition, unresolved intent
- Green — bodily recovery
Activating a color does not select a function. It allows one aspect of reality to become dominant.
4. Field = App (The Abstraction Collapse)
In Ambient OS, the field is the application layer.
Once a field stabilises, behaviour emerges automatically:
- Blue → notes, transcripts, schedules, orientation
- Pink → group presence, mentorship cues
- Green → posture, hydration, recovery
- Purple → spatial systems, infrastructure logic
No application is opened. No interface is summoned. Software dissolves into contextual behaviour.
5. Context Is Richer Than Software
An application is a single-purpose container. A context is multidimensional.
A supermarket contains clarity, movement, health, relation, infrastructure, and self. No single application can carry this. A field can.
The world becomes the container.
The field becomes the interface.
Applications dissolve into behaviour.
6. Home, Red, and the Absence of Apps
Home is not an Attractor Entity. Home is the resting state of attention.
Red is dominant. Red does not execute behaviour. Red carries attention.
Therefore: Red has no applications.
What appeared as application usage at home was often compensation for architectures unable to carry stillness.
7. Yellow — Navigation Without Execution
Yellow is ignition and unresolved intent. Yellow never executes behaviour.
Yellow has no applications.
When behaviour begins, attention descends into a stabilised field.
8. The Foundational Stack
- Red — being · rest · no apps
- Yellow — ignition · navigation · no apps
- Stabilised Fields — behaviour emerges
- Gray — legacy fallback only
9. Illustration Layer — Attractor Entities
The principles described in AAF-0 are not theoretical. They manifest as Attractor Entities — locations where multiple fields coexist and behaviour emerges through stabilisation.
AAF-0 defines the grammar. Its lived expressions are documented separately.
AAF-0 defines the grammar.
AAC documents the language in use.
See the canonical Attractor Entity library:
AAC — Canonical Attractor-Entity Library
10. Canonical Sentence
Every location contains multiple attractor fields.
The dominant field determines which behaviour becomes available.
This document defines the pre-behavioural layer beneath Ambient Attractor Commerce and Navigation.
Commerce, interaction, and systems only emerge after field stabilisation.