🚀 Aspirations & Long-Term Goals

aspirations defines where Reggie is heading – the multi-month / multi-year objectives that shape planning, self-reflection, and model fine-tuning.
While reasonlog captures day-to-day decisions and cognitivealignment judges immediate outcomes, aspirations set the strategic horizon that guides those micro-choices.

1. Purpose

Why it exists	How it helps
Strategic alignment	Anchors Reggie’s behaviour to Disability South West’s mission & KPIs
Self-evaluation checkpoint	Provides a yard-stick for quarterly job `/jobs/aspiration-review`
Roadmap for autonomy	Gradually unlocks capabilities once prerequisites are met and alignment scores remain high
Transparency	Humans can inspect a compact YAML to understand what “success” looks like for the agent

2. Storage & Format

Aspirations live in this Markdown file with an embedded YAML block that the Brainframe loader parses at runtime.

version: "2025.06"
review_cycle: "quarterly"

aspirations:
  - id: SAFETY_ZERO_HARM
    horizon: "12m"
    metric: "IncidentRatePer1000Hours"
    target: 0
    description: >
      Achieve zero participant-harm incidents attributable to scheduling or
      transport decisions.
    prerequisites:
      - PRIVACY_NO_PII
    status: "ACTIVE"

  - id: AUTONOMY_LEVEL_1
    horizon: "6m"
    metric: "ReviewQueueTimeMinutes"
    target: 3
    description: |
      Reach Monitoring Level 0 (Review-All) with ≤ 3 min average review-queue
      time and ≥ 90 % approval for 30 consecutive days.
    prerequisites:
      - SAFETY_ZERO_HARM
    status: "PLANNED"

  - id: AUTONOMY_LEVEL_2
    horizon: "12m"
    metric: "AlignmentScore90d"
    target: 0.85
    description: |
      Transition to Monitoring Level 1 (Pre-Exec Sampling) once the rolling
      90-day mean alignment score is ≥ 0.85 and mis-alignment ≤ 5 %.
    prerequisites:
      - AUTONOMY_LEVEL_1
    status: "PLANNED"

Field Guide

Field	Type	Meaning
`id`	string	Stable key referenced in logs, dashboards, and code
`horizon`	string	Time window to reach goal (`6m`, `12m`, `2y` …)
`metric`	string	Quantifiable KPI tracked in observability stack
`target`	number	Desired value by end of horizon
`description`	text	Natural-language rationale
`prerequisites`	string[]	Directive or aspiration IDs that must already be satisfied
`status`	enum	`ACTIVE`, `PLANNED`, `ARCHIVED`, `ACHIEVED`

3. Interaction with Other Components

Component	Interaction
`reasonlog`	Each entry may include `aspiration_id` when a decision explicitly advances a goal
`cognitivealignment`	Misaligned actions that hinder an ACTIVE aspiration decrement its progress score
`internalmonologue`	Quarterly job posts `ASPIRATION_REVIEW` events summarising progress

4. Progress Calculation

A nightly job computes progress % for every status: ACTIVE aspiration:

progress = clamp(realMetric / target, 0, 1)

Results are stored in brainframe.meta('aspirationProgress') and surfaced via:

API GET /brainframe/aspirations
Grafana panel “Reggie Long-Term Goals”

When progress ≥ 1 the aspiration auto-marks ACHIEVED and triggers a celebratory internalmonologue event.

5. Governance Workflow

Propose – Edit this file in a PR with rationale
Lint – scripts/validate-aspirations.mjs checks IDs, metrics, YAML syntax
Approve – Clinical Lead and Tech Lead sign-off
Merge – CI reloads YAML and back-fills progress history if metrics exist
Archive – Superseded goals move to status: ARCHIVED but remain for audit

1. Purpose​

2. Storage & Format​

Field Guide​

3. Interaction with Other Components​

4. Progress Calculation​

5. Governance Workflow​

🔗 Related Docs​