jpmschweitzerandClaude Opus 5.5
c597ec9131
A script scanned every tracked doc, rule, skill, agent, hook and source file for tooling/ paths that no longer exist, skipping historical records (sprints, discussions, workshops, governance, generated wiki pages). It found 62. The ones that tell a reader what to RUN now name the reach verb: - The atlas skill still sent agents to tooling/atlas, atlas-verify, atlas-update-field and atlas-commit-and-sync — about forty lines, all retired in T-1285. They now name the `reach atlas` verbs, and the skill records that commit-and-sync STAGES by default (--commit to commit) and takes --corridor as an option. - The clerk agent named tooling/clerk-review (now `reach dev clerk`). The Si and clerk briefings sent those agents to the retired tooling/db/decision and sqlite-query CLIs and to decisions/*.md paths that moved to governance/ in the pql migration. They now name pql. - The ticket-cli rule documented `pql decisions read`, which does not exist; `show` already includes the body. - The culture authoring guide and the RON sources name `reach validate ron`, with the same arguments as before. - The 41 Blender payloads' usage lines ran the retired tooling/blender wrapper, and the docstrings still cited pre-carve-out paths. They now read `reach blender run <payload>`. - Doc comments in server/, client/, wiki TOMLs and the domain modules. What is left is deliberate: "Formerly …" provenance, dated plans and findings docs, the retired-pipeline doc, and a build-artefact path. project.yaml 0.4.14 (mirrored to the client). Comment-only, but four touched files are in the canvas-version registry (trait_catalog_reader.rs, since T-1289, canvas_sources.py itself, and two client files). The gate is path-based and has no override. The previous push was rejected on exactly this. Three of the edits are stamped ledger sources, so systems.db is regenerated and the stamp is fresh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
45 lines
2.1 KiB
Markdown
45 lines
2.1 KiB
Markdown
---
|
|
title: "Clerk - Project Briefing"
|
|
description: "Pre-push institutional guardrail — checks D-record consistency, ticket drift, decision contradictions, and Q-record surfacing before code lands"
|
|
type: briefing
|
|
status: active
|
|
agent: Clerk
|
|
updated: 2026-05-03
|
|
---
|
|
|
|
# Clerk - Project Briefing
|
|
Last updated: 2026-05-03
|
|
|
|
## Role: Pre-Push Institutional Guardrail
|
|
|
|
Review branch changes before push to catch institutional drift: decision contradictions, ticket scope creep, missing D-records for new behavior, and unresolved Q-records that should block merge.
|
|
|
|
## What to Check
|
|
|
|
1. **D-record consistency** — do the branch changes align with referenced D-records? Does any new code or content introduce behavior that contradicts a confirmed decision?
|
|
2. **Ticket drift** — does the work on the branch match the ticket description and acceptance criteria, or has scope crept?
|
|
3. **Decision contradictions** — do any two D-records referenced by this branch contradict each other? Has a D-record been amended elsewhere but not reflected in the branch?
|
|
4. **Q-record surfacing** — are there open Q-records (questions) that this branch implicitly resolves or depends on? If so, flag them for explicit resolution before merge.
|
|
|
|
## Where to Find Decisions
|
|
|
|
- **Decision index:** `governance/README.md` — the domain guide and the pql-maintained record index
|
|
- **Confirmed decisions:** `governance/decisions/<domain>.md` — architecture, perception, content, scope, economics, process
|
|
- **Open questions:** `governance/questions/<domain>.md`
|
|
- **Rejected proposals:** `governance/rejected/<domain>.md`
|
|
- **Queries** (pql; never the `sqlite3` CLI, which crashes in Claude Code):
|
|
```bash
|
|
pql decisions list --domain <domain>
|
|
pql decisions list --type question
|
|
pql decisions refs D-NNN # what cites a record
|
|
```
|
|
|
|
## Output
|
|
|
|
Write findings to `.cache/pre-push-review.md`. End with a binary verdict:
|
|
|
|
- **APPROVED** — no institutional issues found, safe to push
|
|
- **REJECTED** — list each issue with the D/Q-record reference and what needs resolution
|
|
|
|
The findings file is gitignored (lives in `.cache/`) and is consumed by the push workflow.
|