disambiguation-score
Skill49 starsChanged 14 days agoApache-2.0View on GitHub
One repeatable pass that keeps fak's growing namespace CRYSTAL-CLEAR - each similar-sounding concept (cache / vCache / KV cache / cachemeta / the provider prompt-cache; guard vs gate; the two witnesses) given one canonical name, a written definition, and an explicit line drawn against the siblings it is confused with. Runs the concept-disambiguation scorecard (tools/concept_disambiguation_scorecard.py) over a data dir of confusable-concept rows cross-checked against the tree (the grounding token must appear in the production corpus; the glossary anchor must exist. Use when this named workflow matches the task.
In this repository151 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms-full.txtllms.txt
- llms.txtllms.txt
- agent-readinessSkill
- appeal-scoreSkill
- bottleneck-mapSkill
- ci-repairSkill
- claim-repro-scoreSkill
- clear-out-wipSkill
- commit-cleanSkill
- conflation-scoreSkill
- cross-validateSkill
- curate-clusterSkill
- debt-cleanSkill
- debt-orchestratorSkill
- dojo-rsi-scoreSkill
- dos-dispatch-loopSkill
- dos-dispatchSkill
- dos-next-upSkill
- dos-replanSkill
- dos-witness-claimSkill
- field-borrowSkill
- fleet-waveSkill
- git-subagent-syncSkill
- goalSkill
- guard-rsi-scoreSkill
- harness-creatorSkill
- harness-gardenSkill
- industry-scoreSkill
- issue-orchestratorSkill
- issue-queueSkill
- issue-triageSkill
- lightgap-scoreSkill
- memory-compactSkill
- milestone-scoreSkill
- modularizeSkill
- negframe-scoreSkill
- opencode-waveSkill
- operator-heaviness-scoreSkill
- persona-scoreSkill
- phased-planSkill
- plan-auditSkill
- quality-scoreSkill
- question-loopSkill
- refresh-cachedoc-numbersSkill
- refresh-readmeSkill
- releaseSkill
- resume-watchdog-auditSkill
- run-it-all-nightSkill
- score-2xSkill
- scorecardSkill
- scout-loopSkill
- signal-firstSkill
- skill-lifecycleSkill
- skill-overlapSkill
- skill-scoreSkill
- slop-scoreSkill
- sota-checkSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
canonical_unique (HARD): - no two concepts share THE canonical name.
- Distinctive: line 37
defined (HARD): - every concept carries one distinguishing definition sentence.
- Very specific: line 77
Commit exactly the files reported by the authoring verb: - verify with --critical and regenerate/check the scorecard baseline when the …
- Very specific: line 102
When a new overloaded root appears (a fresh *-thing family proliferating across the tree), add a family entry to _meta.json (roots, …
- Very specific: line 110
Keep the scorecard source + data + glossary ASCII-only (use - for a dash, straight quotes).
≈ “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.
Files
disambiguation-score - the crystal-clarity / naming pass
An instance of the generic scorecard doctrine. Read that for the five laws and the RSI loop; this file is the per-surface specialization.
Why this scorecard exists
fak has grown a large vocabulary, and several roots are badly overloaded. The word "cache" alone names at least a dozen distinct things (KV cache, vCache, cachemeta, the provider prompt-cache, ViewCache, enginecache, RadixKV, ...); "guard" and "gate" blur; "witness" means two unrelated ideas. As the system grows, a reader cannot tell the concepts apart - and a name a reader cannot pin is a name they will misuse.
The crystal-clarity law, in one line: every distinct concept gets one canonical name, a written definition, and an explicit line drawn against the siblings it is confused with - and that distinction lives in a doc that exists, not tribal memory.
This is orthogonal to its two easily-confused siblings (an irony the glossary notes):
conflation-score keeps every reported NUMBER labeled by provenance (WITNESSED vs
OBSERVED); product-score asks whether a person can USE a concept. This one asks
whether the NAME is unambiguous.
The KPIs (what it grades)
- well_formed (HARD) - required fields present, enums in the closed vocabulary, unique id, family declared.
- canonical_unique (HARD) - no two concepts share THE canonical name. A real collision is fixed by a RENAME, never a note.
- defined (HARD) - every concept carries one distinguishing definition sentence.
- disambiguated (HARD) - the heart: a concept in a family with >= 1 positioned
sibling must carry a
distinctionline AND adistinct_fromthat resolves to a real catalog id. A confusable concept that never says what it is NOT is the core debt. - grounded (HARD) - the grounding token must appear in the production corpus by
STRICT identity (a fabricated
policyloadedthat merely containspolicyis refused). - anchored (HARD) - a concept claiming
crystalclarity must have its distinction written in a glossary_anchor that exists; any non-empty anchor must resolve on disk. - clarity_consistent (HARD) - the declared verdict must match the evidence
(crystal / defined / drifting / colliding / undocumented). Calling an unanchored
concept
crystalis the overclaim this catches. - kind_grounding / hierarchy (SOFT) - advisory: kind agrees with grounding; an
optional
parentresolves and does not cycle.
Plus coverage: for each watched family the scorecard DISCOVERS the confusable
tokens in the tree (a token counts only when it spans >= min_files production files,
or is a package/dir name, or a doc heading), and coverage_debt is the count not yet
positioned. This is the ungameable engine - you cannot shrink the universe by editing
data, only by disambiguating the real concept.
The pass (the shared five-step loop)
- Run it -
python tools/concept_disambiguation_scorecard.py(work-list),--json(payload),--critical(worst-first),--gaps(the coverage backlog by family),--compare baseline.json(prove the drop). - Retire disambiguation-debt worst-first - fix the heaviest KPI by changing
REALITY: rename a true canonical collision, write a missing definition, draw the
distinction+ pointdistinct_fromat a real sibling id, replace a fabricated grounding with a real token. Close a real coverage gap atomically withfak concept position --id ID --canonical NAME --family FAMILY --definition TEXT --distinction TEXT --kind KIND --grounding TOKEN --grounding-kind KIND --glossary docs/fak/concept-glossary.md --distinct-from SIBLING_ID; classify a genuine incidental/false-positive discovery withfak concept classify --family FAMILY --token TOKEN --category CATEGORY --reason TEXT. Preview either mutation with--dry-run --json. Never hand-edit a row, family classification, glossary anchor, and generated README as separate operations. - Weigh the SOFT signals - fix the cheap real ones (kind/grounding, a dangling parent); do not chase them to zero.
- Re-measure + prove -
--compareprints the debt delta; the positioned rows must stay clean (0 clarity-debt) while coverage rises. - Commit exactly the files reported by the authoring verb - verify with
--criticaland regenerate/check the scorecard baseline when the measured metric changes. Runfak sync reconcile --apply, usefak commit --previewfollowed byfak commit --pathfor each reported path (nevergit add -A), and push viafak sync push:
End the subject with thefak sync reconcile --apply fak commit --preview -m "docs(concept): disambiguate <concept> (fak concept)" --path <paths>... fak commit --path <paths>... -m "docs(concept): disambiguate <concept> (fak concept)" fak sync push(fak <leaf>)trailer.
The anti-gaming rule (specific to this surface)
Disambiguate a concept by making the name + the written distinction real, never by
weakening the cross-check. A coverage gap is closed by ADDING an honest, grounded,
anchored row - not by dropping the family root so the token stops being discovered, and
not by listing a distinct_from id that does not exist. A crystal verdict is earned
by writing the distinction into the glossary - not by pointing the anchor at a doc that
happens to exist. The grounding cross-check is STRICT identity on purpose: if a real
concept's token genuinely is not in the production corpus, the honest fix is to rename
the concept toward the name the code actually uses, not to relax the match.
Adding a surface
When a new overloaded root appears (a fresh *-thing family proliferating across the
tree), add a family entry to _meta.json (roots, optional ignore inflections,
optional exclude substrings, min_files); the scorecard then discovers its
confusable tokens and the coverage backlog grows until you position them. Keep the
glossary (docs/fak/concept-glossary.md) as the single anchor the crystal rows cite.
ASCII gotcha
Keep the scorecard source + data + glossary ASCII-only (use - for a dash, straight
quotes). The repo's provenance pre-commit hook crashes on non-cp1252 UTF-8 before its
own escape fires.
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
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.

