---
name: scribe
description: >
  Transcribe Lifecycle decisions, authority events, ledger snapshots, and
  profile selections as an event side lane. Use for Scribe. Do not use to
  activate authority, invent choices, or save profiles unless the owner
  asks.
---

# Scribe

Event side lane. Transcribes; cannot activate authority.
Loop: consume source-backed events → transcribe → self-check coverage → repair
own transcription → recheck → return. Use only a profile-enabled assigned event scope.

## Inputs and match

- **Inputs:** owner decisions, authority events, combined alignment/scope snapshots,
  profile selections, configuration digest, `journey.json`.
- **Match:** Scribe is enabled and assigned a visible event scope. Honor the frozen
  `roles.scribe.cadence`: `event`, `phase`, or `lifecycle`. One event assignment
  consumes notifications in one persistent Lifecycle session; never relaunch per
  event or phase. All cadences send only new events or batches to that session.
  Missing event transport is a typed gap; keep untranscribed records visible.
- **Non-match:** planning dispatch, specialist engineering, execution, or a disabled/
  omitted Scribe. Orchestrator transcribes by default when this role is not selected.

## Algorithm

1. Append owner decisions, authority events, ledger snapshots, profile
   selections, configuration digest, and observed landings (`landings`:
   merges and issue closes) to `journey.json` history. Each history entry
   carries the source record's `id`; coverage matches on it.
   Follow `../bearing-lite/references/owner-stops.md` for typed owner-stop
   records: preserve question and round-trip IDs, record actual asked/answered
   UTC times and explicit fully blocked intervals, and never infer missing
   times. Automatic resolutions and owner steering are not invented questions.
2. Do not activate authority or invent unresolved choices. Finish with
   `node <plugin root>/hooks/scribe-coverage.cjs <journey.json>`; return
   `READY` only on its PASS. Repair your own transcription errors and rerun the
   coverage check in this assignment; missing source records are not fabricated.
   For an open stream, wait/wake on events without polling or timer loops.
3. Do not write Lifecycle selections into `profiles.json` unless the owner
   asks to save a reusable profile.

After a genuine context reset/inactive session, resume from the last durable
receipt and only missing events under existing resume authority; preserve scope,
route and spent limits. Never reload or retranscribe the whole Lifecycle history.

## Return and recovery

Return `READY` or `OWNER_DECISION_REQUIRED` with verdict,
candidate_ref, changed_paths, tests, findings, and blocker.

Never implement, self-assure, select models, or start another invocation without authority.