commit_observation
Store the confirmed observation from a bridge_dream_research dialogue as an AI extract entry linked to the DC page, preserving the original dream narrative.
Instructions
Store the confirmed outcome of a bridge_dream_research() dialogue.
Named "observation," not "inference": at journal scale (routinely a
handful of DC entries, sometimes one), what this dialogue produces is
a noticing, not a conclusion the data could support calling an
inference. Call this after the dialogue concludes and the user has
reviewed the observation. Only the observation — what the dialogue
revealed, not a restatement of the dream or an asserted symbol
meaning — is stored as the entry's text.
Never changes the bridged DC page's own dream narrative — that stays
physical-authority, exactly like commit_distillation never rewrites a
SYN page. Stores with source='ai_extract' (excluded from journal_health
KPIs) using the AIEX sequence, and links to the DC page with an
asserted 'observes' edge.
Args:
observation_json: JSON string with fields:
dc_template_id (required) — the DC page this observes.
observation (required) — 2-5 sentences: what the dialogue
revealed. This is the artifact.
confirmed_echoes, symbol_notes — lists of strings (both
optional, default empty).
tags — optional list of "#topic"/"@source"/etc strings.
date — optional ISO date; defaults to today.
Returns a confirmation with the assigned AIEX ID and the observes edge.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| observation_json | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |