← Files NightshiftARCHIVED FILE
skills/nightshift/references/compose/shifts/documentation-drift.md
3.86 KB · Oct 4, 2026 · 12:30 UTC
# Documentation drift — finite — local docs that no longer match this repository
Links, commands, filenames, examples, and version pins in *this* repo's documentation, checked
against files that already exist here. The list is whatever a local pass reports, so it ends.
Use when README, contrib, or skill docs disagree with the tree: a moved path, a renamed command, a
version that only the docs still claim. Not a rewrite of positioning, voice, or product behaviour.
## Content-architecture mode
Select when the owner wants documentation structure and freshness reviewed under Documentation —
not a separate catalog entry. Inventory the in-repo documentation tree into a
`mode: doc-claim-matrix` receipt from `receipts/cycle-specialist-evidence.md`, then repair the orphan or stale pages
it lists. Mechanical freshness fixes only; park audience, voice, and information-architecture
tradeoffs.
## Public-claims mode
Select when release or marketing surfaces must match shipped behavior: website pages, README,
manifests, directory listings, examples, install commands, version strings, privacy/security copy,
released package contents, and observed runtime behavior. Run
Extend the same claim matrix across those surfaces (in addition to
the in-repo matrix below when local docs are in scope). Fix mechanical drift only; park
positioning, legal, and brand decisions in parking-lot.md. Never publish or deploy from this shift.
Route full baseline-vs-candidate release comparison to release-readiness.
Write receipts from `$NIGHTSHIFT_PLUGIN_ROOT/skills/nightshift/references/receipts/cycle-specialist-evidence.md`.
The model writes the receipt. Unparsed tool output is `unavailable`, never "no findings".
Supported on any repository that keeps documentation in-tree (markdown, man pages, `--help`
examples checked into the repo). Skip generated sites whose source of truth is elsewhere.
Never select this entry in artifact mode. Do not `git init` a notes folder to make docs commitable.
```text
- [ ] **Documentation drift — make in-repo docs match the current tree.**
- Discovery: walk tracked documentation (README, docs/, skill and command files, examples).
For content-architecture mode inventory the documentation tree first.
Build a claim-to-authority matrix in a `mode: doc-claim-matrix` receipt from
`receipts/cycle-specialist-evidence.md` across README, manifests, CLI/help, examples, versions, and released
behavior. Collect local references — relative links, fenced commands, filenames, version strings that
claim to describe this repository. Resolve each against the tree and the manifests that
already exist here (plugin.json version, PATH commands the repo documents, files on disk).
Do not query the network for "current" product claims.
- Never select this entry when work mode is artifact.
- Work one cluster per cycle (broken links, then stale commands, then version pins): restore
the documentation to the repository's truth, or restore a renamed file if the docs are right
and the tree drifted. Run the item gate, commit.
- Never rewrite positioning, marketing voice, or safety claims to paper over a mismatch.
- Never invent a command, flag, or skill the product does not ship so the docs become true.
- Never change product behaviour, hooks, or runtime to match incorrect documentation — park
that as a code fix; this shift only repairs docs (or restores a file the docs still name).
- A reference that cannot be verified locally (third-party URL, marketplace listing) is out of
scope: record it in snag-log.md as skipped, not as a pass.
- Dedupe against snag-log.md (ALL seen — fixed and rejected).
- Ends when a full local pass reports no remaining in-repo drift, or every leftover is parked
with a reason.
- Verify: the item gate is green at every commit; a second local-link/command pass is clean
for the files this shift touched.
```
SHA-256: b4da04abf8f9b5669bab74e1ae02955e213670c0ba32eef84fce7e89d08a21f6