Signals
Source path: knowledge-base/knowledge/vocabulary/beliefs/32-signals.md
# Signals that reposition the read, staged for the user to weigh in on. Every task emits **DomainProgramEvents** (the canonical projection spine — "projection" here is the rendering of events into cards, the event-rendering sense, distinct from the Projection opinion layer) that project into **Stories**. A domain projects only its own activity; a **constellation Program** is bottom-up **aggregation** — it reads member domains' events after a per-domain cursor and produces rollups/portfolio Stories, **never mutating a member artifact** (§7). The four tasks are the engine's *internal* decomposition; the reading surface organises what they produce by **Consequence** (below) — what each item means for the user — not by task. On mobile, the four Program task circles form an always-visible top bar opening a focused full-screen Story sequence; on desktop the same tasks are a divider-separated railOpen on GitHub
Raw Markdown source