Skip to content

Harness sync: policy exclusions and employer-name redaction

  • Date: 2026-10-20
  • Status: Accepted
  • Tags: tooling | structure | process

Context

claude/harness/ mirrors ~/.claude through syncing-harness-inventory. Redaction rewrites work identifiers to placeholders and re-scans the output. The last sync ran on 2026-08-31. Two gaps showed up in the first run after that:

  • The redaction rules missed the employer's written-out name ("Healthy Together") and the manager's name, so the re-scan passed while a personal skill still carried both.
  • Personal notes (laser-focus role and programs files, resume-ledger local config) and editor backup copies (*.bak*) were copied into the mirror. Their content is work context in prose, which redaction cannot clean.

Decision

  • Redaction rules now cover the spelled-out employer name, the manager's full name, and the manager's bare first and last names.
  • scripts/exclude.txt lists paths (fnmatch, relative to claude/harness/) that are dropped before redaction. Files matching it are reported under excluded_work_related.
  • inventory.py drops every *.bak* file by policy, before redaction.

Alternatives Considered

Option Why Rejected
Exclude whole skills for any work-context file Drops the reusable pattern too. The redaction approach was kept for everything it can clean.
Hand-delete files from the mirror after each run Not repeatable; the next snapshot would copy them back.
Keep backups and let redaction handle them Backups are not authored config; mirroring them adds noise and stale copies.

Consequences

Positive:

  • The re-scan now catches the employer and manager names it previously missed.
  • Personal prose and backups stay out of the public-facing mirror without per-run manual work.
  • Exclusions show up in the run output and manifest counts, so they stay visible.

Negative / Trade-offs:

  • exclude.txt is a manual list. A new personal file with work context must be added to it.
  • The structural change (about 23 added components, one removed hook) is recorded here as one sync, not as separate ADRs per component.

Ongoing obligations:

  • Add a redaction rule whenever a new work name appears in ~/.claude.
  • Review exclude.txt when a personal skill gains a file with work context.

ADRs are immutable. If this decision changes, create a new ADR with status "Superseded by" pointing here, and update this record's status.