Ada is your interface
Ada is your Executive Assistant - the primary way you interact with 2bd. Rather than managing templates, archives, and workflows manually, you simply talk to Ada. She coordinates everything behind the scenes. When you say “Ada, run my morning ritual” or invoke/ada plan daily, Ada orchestrates a team of specialized assistants to prepare your day, fetch calendar context, and compose your working notes.
The ritual loop
2bd operates on a simple cycle: plan - work - reflect - archive. This loop is powered by the GPS methodology - Goal, Plan, System - which cascades from yearly vision down to daily execution.
Metabolic states
2bd organizes notes by metabolic state - how active and volatile they are - rather than by topic.
Metabolic states solve the “where does this go?” problem by organizing around information lifecycle. Fresh notes go to Captive. Active work lives in Synthetic. Completed work archives to Periodic. The system moves information naturally without you deciding where things belong.
Ada’s assistant team
Ada manages a team of domain-specific assistants:
Each assistant specializes in one domain and knows how to handle that domain across all timescales.
How rituals run
The orchestration process
- Parse the action (plan/reflect) and timescale
- Run each assistant’s action for that timescale
- Each assistant writes to
Synthetic/Assistants/{name}/ - Compose outputs into Captive (plan) or Periodic (reflect)
- Learn patterns from observations
Parallel Execution
As of v1.2, Ada runs assistants in parallel for 70-80% faster rituals. The parallel flow:- Draft generation - All assistants run as background agents simultaneously
- Context analysis - Each agent reads vault, generates template section with placeholders
- Draft collection - Ada gathers all drafts and extracts questions
- Intelligent ordering - Ada orders questions for natural conversation flow
- User interaction - Ada asks questions, collects answers
- Placeholder filling - Ada fills all placeholders with answers
- Composition - Ada assembles final note from filled sections
- Other assistants continue normally
- Failed sections noted in final output
- Partial results still usable
vault/00_Brain/Systemic/Config/ada.yaml:
false to use legacy sequential mode.
Template architecture
Templates are split between Ada and assistants:
Ada composes Captive notes by:
- Loading the base template for the timescale
- Reading section order from
vault/00_Brain/Systemic/Ada/section-order.md - Inserting assistant sections in the defined order
- Each assistant owns specific H2 sections in the final document
Reflect flow
During reflection, each assistant:- Loads its template from vault
- Compares plan output to actual capture note section
- Returns findings (variance, coaching questions, entity learnings) to Ada
- Ada aggregates findings into a coaching conversation
- Confirmed entity learnings persist to vault (People, Projects)
Quick reference
Planning rituals
Run in the morning (or start of period):- Loads context from higher timescales
- Runs interactive conversation with you
- Writes structured output to Synthetic
Reflection rituals
Run in the evening (or end of period):- Reviews planned vs actual
- Captures insights and patterns
- Records observations for learning
Time scales
The loop runs at four scales, each nesting into the next:Information flow
Self-learning
Ada’s learn assistant analyzes patterns across all assistants:- Observe - Each assistant records observations
- Cluster - Similar patterns are grouped
- Graduate - High-confidence clusters move to Semantic
- Remember - Graduated insights inform future sessions