agentleFS
GCarin1GCarin1/Doctrina/.agents/skills/ledger-abandoned-entries-are-ledger-only/SKILL.md

ledger-abandoned-entries-are-ledger-only

Skill1 starsChanged 4 days agoMITView on GitHub

Two-source cross-checks must exempt entries that one source records by design and the other deletes — an abandoned change is ledger-only, never archived Use when: Adding or editing a validate check that cross-references two records of the same history (LEDGER.md ↔ index.json, file ↔ index), or touching `change abandon`

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before requiring "every id in A exists in B", enumerate the writers of A and B and ask: is there a lifecycle where one side is written and …

    line 18
  2. Very specific:

    Add a test: abandon a change, run doctrina validate, assert exit 0.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- doctrina:skill-export — generated from .doctrina/skills/ledger-abandoned-entries-are-ledger-only.md by `doctrina index rebuild`; edit that file, not this one. -->

Skill — ledger-abandoned-entries-are-ledger-only

When to use this skill

  • Writing or changing a validate check that requires two artifacts to agree (e.g. changes/archive/LEDGER.md ↔ index.json.changes_archive).
  • Touching change abandon or any command that deliberately writes to ONE of two mirrored records.

Procedure

  1. Before requiring "every id in A exists in B", enumerate the writers of A and B and ask: is there a lifecycle where one side is written and the other is deleted BY DESIGN? (change abandon appends — abandoned to the ledger and deletes the change folder — there is deliberately no archive entry.)
  2. Exempt that lifecycle explicitly in the check, keyed on the recorded marker (the ledger line's trailing abandoned), not on heuristics.
  3. Add a test: abandon a change, run doctrina validate, assert exit 0.
  4. Grep for other two-source checks with the same blind spot before closing (metadataDrift, orphan checks, LEDGER cross-checks).

Anti-patterns

  • Requiring set-equality between two records whose writers are not symmetric: every change abandon turned validate permanently red (found while dogfooding change 0001-review-followups on 2026-07-12) and the only "fix" was hand-editing history.
  • Fixing the symptom by deleting the ledger line — the abandonment record IS the point; the check was wrong, not the ledger.

Related material

  • packages/doctrina-cli/src/commands/validate.js (ledger ↔ index check)
  • packages/doctrina-cli/src/commands/change.js (changeAbandon)
  • ADR 0014 — field-review follow-ups

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.