Backed by: state/lib/sweep.ts + state/lib/knowledge.ts

catchup

One-screen brief before a meeting. Pulls:

• git log --since=$since in ~/projects/snappy-client-<slug>
• Sweep items filtered to client participants
• Krisp action items owned-by-Robert for the client
• Xano invoice state

Steps

1. Resolve since from ~/.claude/cache/krisp/meetings.json (last

meeting with this client) if not passed.

1. Collect the four signals.
2. Dispatch gemini to condense into a one-screen markdown brief.
3. voice.checkTone() gate (internal drafts are §4a-exempt for

frontmatter but still must pass em-dash check).

1. Write to state/log/catchup/<client>-<date>.md.

Eval

score("catchup", run_id, {
  score:
    shape_ok && tone_ok && has_all_four_signals ? 1.0 :
    shape_ok && tone_ok ? 0.5 :
    0.0,
  signals_present: {
    commits: commits.length > 0,
    messages: msgs.length > 0,
    commitments: commits_k.length > 0,
    invoice_state: !!invoice,
  },
  primary_issue: !tone_ok ? "voice-gate-failed" : null,
});

0.5 acceptable if a signal genuinely has no data (new client, no commits yet). 1.0 when all four populate. 0.0 on tone fail - even internal drafts go through the gate because they get pasted into client comms.

Gotchas

• since resolution from Krisp can be wrong if the last meeting was

mislabeled. Allow explicit override.

• Client repo path convention: ~/projects/snappy-client-<slug>.

Rubric

criteria:
  - name: all_four_signals_present
    kind: deterministic
    check: "The 'signals_present' field in the evaluation JSON reports 'true' for 'commits', 'messages', 'commitments', and 'invoice_state'."
  - name: brief_tone_passes_gate
    kind: deterministic
    check: "The 'primary_issue' field in the evaluation JSON is 'null' or does not contain 'voice-gate-failed'."
  - name: output_file_created
    kind: deterministic
    check: "A markdown file named 'catchup-<client>-<date>.md' exists in 'state/log/catchup/'."
  - name: brief_content_relevance
    kind: judge
    check: "The generated brief accurately condenses and presents information from the four source signals (git log, sweep items, Krisp items, Xano invoice state) for the specified client."

catchup - loader

Per-turn rules for the catchup skill. Full reference: state/skills/catchup/SKILL.md. Do not skip these.

Critical Rules

• ALWAYS run voice.checkTone() on the dispatched draft - internal briefs get pasted into client comms, so em-dash check still applies (score 0.0 on tone fail)
• ALWAYS resolve since from ~/.claude/cache/krisp/meetings.json last-meeting timestamp UNLESS explicitly overridden - Krisp can mislabel meetings, so allow override
• Client repo path convention is hard-coded: ~/projects/snappy-client-<slug> - don't guess slugs
• All four signals (commits, messages, commitments, invoice_state) populated → 1.0; some genuinely empty → 0.5; tone fail → 0.0

Commands

| ui dashboard | state/skills/catchup/resources/ui.openui | |invoke: client is required input; collects 4 signals in parallel, dispatches gemini to condense, gates on voice.checkTone(), writes state/log/catchup/<client>-<date>.md |verify: shape_ok && tone_ok && has_all_four_signals |eval log: state/log/evals.ndjson (skill: "catchup")

OpenUI Resource

• Skill-owned OpenUI Lang resource: state/skills/catchup/resources/ui.openui. Read it before rendering or editing this skill's generated component surface.
• Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
• System resources compose OpenUI primitives and inherit SnappyChat tokens. Use ui_contract: branded in SKILL.md only for deliberate platform or client visuals.

Known Pitfalls

• since resolution can be wrong if the last Krisp meeting was mislabeled - allow explicit override via the since input
• New clients legitimately empty in commits/commitments - that's a 0.5, not a 0.0
• Frontmatter is §4a-exempt for image-prompt fields, but body prose is not (memory: feedback_image_prompts_not_4a)

Self-Test

An agent reading this should correctly:

1. [ ] Reject a draft that fails checkTone() even though it's an internal brief
2. [ ] Use ~/projects/snappy-client-<slug> for repo path
3. [ ] Score 0.5 (not 0.0) when a new client has no commits yet

Self-report

If this loader fell short, append a line:

echo "[$(date -u +%FT%TZ)] catchup: <what was missing>" >> state/log/loader-feedback.log

<!-- kernel-ok: historical attribution for the PID-loader pattern. -->

Self-correcting loader (PID feedback)

This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.

Before you finish, do two things:

1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.

• Default action: edit this file. Surgical. Add the missing line, table

row, or code example where it belongs. No restructuring.

• Only LOGGED is allowed when: the fix needs >10 lines, spans multiple

files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.

• "I didn't have time" / "it's minor" / "the next agent will figure it out"

are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.

• Concrete example of a valid P-fix: discover agent-browser screenshot

takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.

• The goal: the next agent never has to leave the loader.

2. Log the result.

echo "[$(date -u +%FT%TZ)] catchup: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log

• FIXED = you patched this loader inline (P-fix).
• LOGGED = too large for inline; the PostToolUse enqueue + Stop-hook drain

will rewrite the loader from scratch on next session-end.

Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.