Documentation and header comments that no longer match the code
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown, shell, typescript
- Domain
- documentation
Research direction
This is a batch of about 40 stale doc and comment claims, each with a file and line plus the code that contradicts it. Pick a single row, such as the DriftReminder budget in LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:257 checked against hooks/DriftReminder.hook.ts:28, and confirm the code still says what the issue reports. Correct only the doc text to match the code, and split the batch into several pull requests grouped by file. Done means each row you take is fixed and the stated evidence no longer conflicts with the source.
Written by the indexing model from the issue text.
Description
[!NOTE]
🤖 Paulino (AI assistant) responding on behalf of Dr. Paulo
Summary
Each line was checked against the release code. The evidence is in the last column.
| line | what it says that is not so | evidence |
|---|---|---|
LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:257 |
DriftReminder has a 1-per-5-turns budget with dedupe | "Every turn, no rate limit" (hooks/DriftReminder.hook.ts:28) |
LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:378 |
DeployRegistrationGate blocks end-of-turn | it is in ADVISORY_GATES (hooks/StopGates.hook.ts:112) |
LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:388 |
review-state.json is mirrored for the statusline |
nothing under LIFEOS/STATUSLINE reads it |
LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:486 |
ISAStaleWriteGuard is a PostToolObserver member |
retired 2026-10-24 (hooks/PostToolObserver.hook.ts:15) |
LIFEOS/DOCUMENTATION/Hooks/HookSystem.md:1469 |
AlgorithmNudge does skill-routing and depth on prompt submit | those rows were cut (hooks/AlgorithmNudge.hook.ts:829-833) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:152 |
MemoryRetriever is a pure function | it writes generation and index files (LIFEOS/TOOLS/MemoryRetriever.ts:969-972) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:166 |
the reviewer needs idle_minutes >= 2 |
no idle condition (hooks/MemoryReviewFire.hook.ts:366); same at LIFEOS/DOCUMENTATION/LifeosSystemArchitecture.md:336 |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:251 |
cap pressure warns at >=44/48 | warns at >=46 (LIFEOS/TOOLS/MemoryHealthCheck.ts:422) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:313 |
KNOWLEDGE holds People / Companies / Ideas / Research | six types (LIFEOS/TOOLS/KnowledgeSchema.ts:37) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:409 |
5 object types | six, with book (LIFEOS/TOOLS/KnowledgeSchema.ts:37) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:416 |
_index.md has a seedlings section |
it has "Low Quality (need development)" (LIFEOS/TOOLS/KnowledgeHarvester.ts:726-728) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:719 |
LearningPatternSynthesis does not read the live feedback ledger | it reads Errata (LIFEOS/TOOLS/LearningPatternSynthesis.ts:97) |
LIFEOS/DOCUMENTATION/Memory/MemorySystem.md:728 |
ActivityParser is analysis only | --generate writes a file (LIFEOS/TOOLS/ActivityParser.ts:646-647) |
skills/Cortex/References/CompleteGuide.md:438 |
ContextSearch searches five sources | six, with project ISAs (skills/Cortex/Tools/ContextSearch.ts:70) |
skills/Cortex/References/CompleteGuide.md:469 |
JSONL search stays in this install's conversation dir | it searches every project dir (skills/Cortex/Tools/ContextSearch.ts:550-556) |
LIFEOS/TOOLS/Services.ts:129 |
the deriver regenerates Data-Plane pages | its plist runs LearningPatternSynthesis --hypothesize (LIFEOS/PULSE/com.lifeos.deriver.plist:12-13) |
LIFEOS/TOOLS/Services.ts:180 |
DerivedSync regenerates Data-Plane pages | those rebuilds were retired 2026-10-14 (LIFEOS/TOOLS/DerivedSync.ts:7-9) |
LIFEOS/TOOLS/Services.ts:218 |
CommitmentSweep sweeps commitments and reminders | it queries only Type:commitment (LIFEOS/TOOLS/CommitmentSweep.ts:117) |
LIFEOS/TOOLS/WorkSweep.ts:15, LIFEOS/TOOLS/CommitmentSweep.ts:15, LIFEOS/TOOLS/UsageAggregator.ts:13, LIFEOS/PULSE/modules/usage.ts:14, LIFEOS/TOOLS/InstallDerivedSync.ts:4, LIFEOS/DOCUMENTATION/Work/WorkSystem.md:85 |
only launchd runs them | the installers also create systemd user units on Linux (LIFEOS/TOOLS/InstallUsageAggregator.ts:112-136) |
CLAUDE.template.md:111 |
the statusline reads LIFEOS_STATE.json |
it reads USER/STATE/current.json (LIFEOS/STATUSLINE/sections/StateRow.ts:65) |
LIFEOS/TOOLS/AgentState.ts:11 |
AgentWatchdog and CarrierProbe consume agent-starts.json |
CarrierProbe never names it; AgentWatchdog reads subagent-starts.json (LIFEOS/TOOLS/AgentWatchdog.ts:46) |
LIFEOS/DOCUMENTATION/Skills/SkillSystem.md:342 |
FailureToCase turns execution.jsonl into cases |
it takes --prompt/--banned/--expect and never reads that file |
LIFEOS/DOCUMENTATION/Tools/Tools.md:748 |
"INSTALL.md § Capability check" | no such section; there is "Capability gate" (skills/LifeOS/INSTALL.md:35) |
hooks/README.md:286 |
WorkCompletionLearning depends on the Inference API | no inference call (hooks/WorkCompletionLearning.hook.ts:60-65) |
hooks/README.md:496 |
WorkCompletionLearning uses learning-readback.ts |
its only importer is hooks/LoadContext.hook.ts:50 |
AlgorithmUpgrade.md:30 (step 2d) |
reads ROOT_CAUSE_ANALYSIS.md |
no tool writes it; LIFEOS/TOOLS/MemoryRetriever.ts:276 only skips it |
LIFEOS/TOOLS/MemoryHealthCheck.ts:398 |
the next write silently erases the invalid entry | with a ledger head the write is refused (LIFEOS/TOOLS/MemoryWriter.ts:976-988) |
LIFEOS/ROUTER/Depth.ts:6 |
AlgorithmNudge's depth row is a consumer | that row was cut (hooks/AlgorithmNudge.hook.ts:829-833) |
hooks/AlgorithmNudge.hook.ts:8, hooks/AlgorithmNudge.hook.ts:36, hooks/AlgorithmNudge.hook.ts:49, hooks/AlgorithmNudge.hook.ts:55 |
the header documents the routing, depth and doctrine rows | run() no longer emits them (hooks/AlgorithmNudge.hook.ts:829-833) |
derived-artifacts.json:17 |
the per-turn AlgorithmNudge refreshes skill-usewhen-index.json |
loadIndex() has no caller (hooks/AlgorithmNudge.hook.ts:691); only --rebuild-index writes it |
hooks/StopGates.hook.ts:20 |
the first blocking gate wins | all blocking reasons are joined (hooks/StopGates.hook.ts:136) |
hooks/VoiceCompletion.hook.ts:15 |
the main-session check reads kitty-sessions/{sessionId}.json |
it checks CLAUDE_CODE_AGENT_TASK_ID (hooks/VoiceCompletion.hook.ts:38-40) |
hooks/lib/transcript-evidence.ts:13 |
the module fails open and never blocks a Stop | strict mode throws TranscriptUnreadableError (hooks/lib/transcript-evidence.ts:78) |
hooks/lib/context-reduction-core.ts:8 |
the shell hook stays the command-hook path | ContextReduction.hook.sh is retired (RETIREMENTS.json:3247) |
LIFEOS/TOOLS/ProseInCode.ts:20 |
default scan is hooks, LIFEOS, skills, test | DEFAULT_SCAN differs and skips tests (LIFEOS/TOOLS/ProseInCode.ts:32) |
LIFEOS/TOOLS/IntegrityCheck.ts:1183-1187 |
fetch-timeouts is file-level and non-blocking | it judges each call (LIFEOS/TOOLS/IntegrityCheck.ts:1391) with a budget of 0 (LIFEOS/TOOLS/IntegrityCheck.ts:305) |
LIFEOS/TOOLS/GetCounts.ts:18 |
LIFEOS_StatusLine.sh must use GetCounts |
the statusline renderer never calls it; only Banner.ts does |
- Dominant language
- TypeScript
- Stars
- 19.9k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
danielmiessler/LifeOS#2894 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
danielmiessler/LifeOS#2891 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danielmiessler/LifeOS#2888 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2886 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
danielmiessler/LifeOS#2848 ·
Maintainers usually reply within 5 days
All issues in danielmiessler/LifeOS
Similar issues
-
ready-for-agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
LucasSantana-Dev/Lucky#3257 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Maintainers usually reply within 1 day