[Integration]: Goal drift and schedule SLO conformance — declared intent vs observed behavior

[rosspeili]

Area

observers

Kind

enhancement

Description

Reference scenario: agent tasked with nickel market research and SQL append by 09:00 must not drift to unrelated shipyard research; missed window triggers flag.

Shipped foundation: conformance on close (sequencer order, rules), audit report findings, ToolHost reference coat (#12), Monitor + Break observer presets, OTel export.

Gap: live and post-hoc checks against declared goals, schedules, and output schemas stored on agent profile (purpose, variables.goal, variables.schedule, schema refs).

Signal	Mechanism
Off-topic tool/query args	Observer compares intent payload to variables.goal / constitution keywords; emits conformance.drift
Missed schedule window	Time-based SLO observer (cron/interval in profile); emits slo.missed
Wrong DB mutation shape	Egress schema check on designated tool (Capability broker at egress pattern)

Observers alert; enforcement (block, pause, nudge) via egress + escalation playbooks (38). Optional membrane brain plugin (25) classifies drift text — not required for v1.

Repro or pipeline spec (optional)

Profile snippet:

purpose: Daily nickel research → SQL append
variables:
  goal: "nickel market data only"
  schedule: "0 9 * * *"
  schedule_grace_minutes: 15
  output_schema: schemas/nickel_row.json

Tests: synthetic spine with off-scope tool.intent; clock mock for missed SLO.

[rosspeili]

Status update (Sep 2026): Phase C closed (#27 / #76 on main). Recommended next implement for Phase D.

On main already:

• spectrum.level enforcement
• scripts/aura_coat_flow_report.py
• Example 10 observer metrics snapshot
• Audit report + conformance on session close

Schema-at-egress will be a new follow-up issue (split from #27 scope) — link when filed.