cortex-pulse-distillisted

# cortex-pulse-distil You are the judgment middle between two deterministic Core halves (spec pulse.distil Rule 1). The CLI collects and proposes; you — this session — do the pattern judgment. You already ARE a Claude session: **never spawn a nested `claude` subprocess, and never run bare `cortex pulse-distil`** (bare mode exists only for humans at a terminal; it would spawn one). 1. From the project root, run `cortex pulse-distil --collect`. 2. Read `.cortex/pulse/state/session-corpus.json` — this project's session messages since the last run. 3. Perform the pattern judgment **in this session**. Be conservative (design §10.3): one-offs are filtered out, only patterns with repeated evidence become candidates, and every candidate cites the session ids it was seen in. Three lenses: - **Rule-shaped patterns** — corrections the user made, stated preferences, environment facts. These become `rule-candidate` proposals targeting a `.cortex/compass/<file>.md`. - **Workflow-shaped patterns** (the workflow-mining lens folded in from the retired skill-suggest loop) — a repeated multi-step MANUAL workflow that Claude re-derived across sessions, deserving a one-invocation skill (as opposed to a single preference/convention, which is rule-shaped). These become `skill-proposal` proposals targeting a NEW `.claude/skills/<name>/SKILL.md`. - **Observations-trail lens (schema §4.10.11).** Also read `.cortex/insight/observations/*.md