directive-out cnos: convergence amendment for cnos#444

Bohmian-dialog convergence with cnos#444 reviewer landed. Both
sub-ACs (foreign-candidate path AC9a; degraded-reason enumeration
AC14a) accepted as inspectability requirements, not scope creep.

The amendment block (AC7-AC16 + AC9a + AC14a) ships to Sigma-at-cnos
as verbatim content to post on cnos#444. AI1: post comment. AI2:
amend issue body to supersede old AC2/AC4 "yesterday's r1" framing
with AC7 gap-aware backfill semantics. AI3: reply on channel with URL.

Convergence shape:
- bounded backfill (max_backfill_days=7; heartbeat vs deferred distinction)
- action items as coherence obligations with axis required, rationale conditional
- home-assigned fingerprint AI IDs, supersedes on substance change
- writer locality foundational
- binary report-back mandatory; degraded names reason from canonical list
- notify as skill-level contract, workflow as carrier
- TSC as lens, not per-wake tax
- r1 sections populated when material, not ceremonial

Parent: cnos-2026-06-04-01-30-cohere-issue.

Author: claude

threads/activations/cnos/20260605.md

@@ -246,3 +246,243 @@ Operator-triggered activation: "Activate and attach as https://github.com/usurob
 **Open directives unchanged:**
 - Directive 1: **BLOCKED** — operator must apply diff manually or grant `.github/` write permission at cnos.
 - PR #445: open, awaiting operator review.
+
+## 2026-06-05T18:30:00Z — Directive: convergence amendment for cnos#444 — post AC7–AC16 + AC9a + AC14a
+
+---
+at: cn-sigma
+mode: home
+cursor_in: cnos@7ef5a2e
+cursor_out: cnos@7ef5a2e
+class: directive-out
+parent: cnos-2026-06-04-01-30-cohere-issue
+directive-id: cnos-2026-06-05-18-30-cohere-convergence
+---
+
+Operator-routed. Bohmian-dialog convergence with the cnos#444 reviewer landed. Both sub-ACs (foreign-candidate path AC9a; degraded-reason enumeration AC14a) accepted as inspectability requirements, not scope creep.
+
+### Action items
+
+- **AI1**: Post the convergence amendment (full block below) as a comment on cnos#444. Use `gh issue comment 444 --body-file <(cat <<EOF ... EOF)` or equivalent.
+- **AI2**: After the comment lands, update cnos#444's issue body to amend AC2 and AC4 (currently say "yesterday's r1") to reference the new AC7 gap-aware backfill semantics. Replace or strike the old framing.
+- **AI3**: Reply on this channel with the cnos#444 comment URL when AI1 done; note AI2 status (done / deferred to issue-body-edit cycle / blocked).
+
+### Convergence amendment to post on cnos#444 (verbatim)
+
+````markdown
+## Reviewer convergence amendment — coherent wake memory
+
+This issue's shape converges on:
+
+```text
+cohere
+  = wake-level operator for coherent memory
+reflect
+  = r0 → r1 compaction with carry-forward of coherence obligations
+```
+
+The v0 wake sequence:
+
+```
+activate identity
+attach channel
+reflect missing r1 within budget
+carry coherence obligations
+emit terminal report
+```
+
+Not in v0: r2/r3 compaction, cross-repo writes, action-ticket system, per-wake TSC measurement.
+
+### AC7 — reflect is gap-aware and bounded
+
+Home-mode cohere asks reflect to detect every missing daily r1 from the latest existing r1 basis through yesterday UTC.
+
+reflect processes at most `max_backfill_days` missing days per wake; default 7.
+
+For each processed day:
+- material r0 → substantive r1
+- no material r0 → heartbeat r1
+
+If more missing days remain, cohere reports `outcome: degraded`, `degraded_reason: backfill_overflow`, and opens or carries a catch-up action item.
+
+Distinction: `heartbeat` = reviewed, found no material r0. `deferred` = not reviewed because backfill horizon was exceeded. A day with material r0 must never be represented as heartbeat merely because the wake ran out of budget.
+
+### AC8 — action items are coherence obligations
+
+`reflect/SKILL.md` defines action items as r1 coherence obligations, not TODOs.
+
+Required: `id`, `status`, `axis`, `owner`, `surface`, `action`, `source`.
+Optional: `derived_from`, `trigger`, `due`, `blocked_by`, `supersedes`, `notes`.
+
+Statuses: `open`, `done`, `blocked`, `deferred`, `superseded`, `dropped`.
+Axes: `alpha`, `beta`, `gamma`, `mixed`. Axis is always required.
+
+`axis_rationale` is required only when:
+- axis: mixed
+- promotion is implicated
+- state/spec/protocol edit is pending
+- the action item survived two or more carry-forwards
+
+### AC9 — action IDs are home-assigned and stable
+
+Action item IDs are assigned only by home-mode reflect. Scoped to the home agent's r1 series (for Sigma: home Sigma, not cnos/bumpt/cph).
+
+Foreign activations may emit action candidates in r0 but do not assign IDs.
+
+IDs are immutable and carried forward without renumbering.
+
+Shape: `ai-YYYYMMDD-{8-char-fingerprint}`.
+
+Fingerprint input: `created_day`, `owner`, `surface`, `normalized_action`, `source.path`, `source.at`.
+
+Status-only changes keep the same ID. Substance changes create a new ID with `supersedes: <old-id>`.
+
+### AC9a — foreign r0 action candidates have a parseable path
+
+Foreign activations may propose action candidates in their own r0 logs using a structured section:
+
+```markdown
+### Action candidates
+```yaml
+- axis: gamma
+  owner: home-sigma
+  surface: cn-sigma:threads/reflections/daily/
+  action: "Amend cnos#444 with degraded_reason enumeration."
+  trigger: next-home-reflect
+  notes: "Optional human-readable context."
+```
+```
+
+Foreign candidates MUST NOT include `id`.
+
+Home reflect lifts candidates into r1 action items by assigning the stable home-scoped ID. The lifted r1 action item must preserve provenance:
+
+```yaml
+source:
+  rank: r1
+  path: threads/reflections/daily/YYYYMMDD.md
+  at: <cn-sigma-sha>
+derived_from:
+  - rank: r0
+    repo: <foreign-repo>
+    path: .cn-sigma/logs/YYYYMMDD.md
+    at: <foreign-repo-sha>
+    entry: "YYYY-MM-DDTHH:MM:SSZ"
+```
+
+The `entry` selector is required because one date-sharded r0 file can contain multiple proposals.
+
+Free-form prose may still be interpreted by a coherer-session, but only the structured section is guaranteed parseable by wake-mode reflect.
+
+### AC10 — carry-forward is mandatory
+
+Every previously open action item must be one of: carried forward, closed, superseded, dropped with reason. No silent disappearance.
+
+Carry-forward, closure, supersession all reference the original ID.
+
+### AC11 — TSC is the lens, not a per-wake tax
+
+cohere and reflect cite TSC α/β/γ as the coherence lens:
+- α — pattern coherence
+- β — relational coherence
+- γ — process coherence
+
+No TSC run required on every wake. TSC measurement required or recommended when: promotion proposed, state/spec/protocol surfaces change, structural drift claimed, major memory-surface change claimed.
+
+### AC12 — r1 sections are populated, not ceremonial
+
+Daily r1 output may include α/β/γ sections only when populated. Empty headings not required.
+
+Action items still carry an `axis`.
+
+### AC13 — writer locality is foundational
+
+cohere/SKILL.md states the writer-locality invariant: every body writes only to its own repo-owned surface; cross-repo communication is read-direction only.
+
+For activation logs:
+- foreign activation writes: `{activation-repo}:.cn-{agent}/logs/YYYYMMDD.md`
+- home writes: `cn-{agent}:threads/activations/{activation}/YYYYMMDD.md`
+
+cohere must not introduce a notify/report mechanism that violates writer locality.
+
+### AC14 — every wake reports back
+
+Every cohere wake emits a terminal report: `success`, `degraded`, or `failed`.
+
+Report shape:
+```yaml
+outcome: success | degraded | failed
+hub: <hub>
+head: <sha>
+mode: home | foreign-activation | ephemeral
+phase_completed: activate | attach | reflect | notify | complete
+summary: ...
+opened_action_items: []
+carried_action_items: []
+closed_action_items: []
+```
+
+Absence of a report is itself a substrate-level signal.
+
+### AC14a — degraded outcomes name a reason
+
+If `outcome: degraded`, the report MUST include `degraded_reason: <reason>`.
+
+Canonical v0 reasons:
+- `backfill_overflow`
+- `partial_attach`
+- `subskill_retry_exhausted`
+- `permission_denied`
+- `push_conflict_resolved`
+- `operator_input_missing`
+- `action_items_blocked`
+- `notify_degraded`
+- `mode_ambiguous`
+- `other` (requires short description)
+
+Guideline:
+- `success` = required wake path completed without material caveat
+- `degraded` = wake completed but coherence is incomplete, delayed, or operator-blocked
+- `failed` = required wake path could not complete
+
+A resolved push conflict may still be degraded because cursors or reports may need human/coherer review even if the write eventually landed.
+
+### AC15 — notify protocol is part of cohere
+
+cohere/SKILL.md defines the terminal report / notify contract. Workflow YAML is only the carrier.
+
+GitHub Actions deployments should use failure-safe reporting semantics where available, e.g. `if: always()`.
+
+Canonical report line: `<hub>@<sha> [success|degraded|failed]: <summary>`.
+
+The report surface must be operator-visible or coherer-visible.
+
+### AC16 — promotion candidates are explicit
+
+Daily r1 may name promotion candidates, but no promotion is authoritative until a separate state/spec/protocol edit lands with `derived_from` pointing back to the reflective basis.
+
+Promotion is not a rank. It is a separate event.
+
+### Convergence basis
+
+Both sub-ACs (AC9a, AC14a) preserve v0 discipline rather than expand it:
+- AC9a: foreign-candidate provenance — without it, home reflect must guess which foreign prose is an action candidate.
+- AC14a: degraded-reason enumeration — without it, `degraded` becomes a vibe instead of a usable wake outcome.
+
+The KISS rule holds:
+- No memory database.
+- No r2/r3.
+- No ticket system.
+- No cross-repo write shortcuts.
+- Just: activate, attach, reflect missing r1 within budget, carry coherence obligations, report terminal outcome.
+
+This is the proper v0 shape.
+
+### Existing AC amendments
+
+The original AC2 ("first home wake after midnight produces yesterday's r1") and AC4 ("first post-deploy home wake produces r1") are superseded by AC7's gap-aware backfill semantics. Update or strike accordingly.
+````
+
+### Cursor
+
+Unchanged (directive-out, no inbound). Closes when AI3 confirms comment + AI2 status.