Bug
LifeOS/install/settings.enhancements.json ships two spinner tips with hardcoded version strings that are stale at main (03a969d, v7.1.1), where VERSION is 7.1.1 and ALGORITHM/LATEST is 8.4.0:
spinnerTipsOverride.tips[159] — "LifeOS 7.0.0 with Algorithm v8.2.1 — one loop from current state to ideal state, a claims-based ISA where each claim names its falsifying probe, fourteen-section ISA body, no effort tiers or modes."spinnerTipsOverride.tips[236] — "Algorithm v8.2.1: every capability — context, thinking skills, research, agents, audits, stronger models — exists to sharpen the ISA toward the hard-to-vary shape of done."
Verify:
git show main:LifeOS/install/settings.enhancements.json | grep -o 'Algorithm v8\.[0-9.]*'
git show main:LifeOS/install/LIFEOS/VERSION # 7.1.1
git show main:LifeOS/install/LIFEOS/ALGORITHM/LATEST # 8.4.0
Both tips are two Algorithm minors behind; tips[159] is also a release behind.
Why this isn't just #1079 recurring locally
#1079 ("Thinking tip shows stale PAI/Algorithm version") was closed with:
Closing — the upstream v4.0.3 release already has the correct versions. The stale tip was only in a local settings.json that carried over from an older install. No upstream fix needed.
That rationale doesn't apply this time. The stale strings are committed in the repo, in the file the installer merges — so a clean install of v7.1.1 gets them. This is the same defect class as #1079, but in the shipped artifact rather than a local carryover.
Related: the changelog claims a fix that didn't land
The v8.4.0 entry in LIFEOS/ALGORITHM/changelog.md lists, among its post-ship audit fixes:
...changelog entry relocated here from the doctrine file per the v6.28.0 lean-file rule; ARCHITECTURE_SUMMARY regenerated; spinner tip version bumped...
No bump reached settings.enhancements.json — the tips still read v8.2.1 at main.
Fix
Both tips' claims still describe 8.4.0 accurately (the loop, the claims-based ISA, no effort tiers). Only the version strings are stale:
-LifeOS 7.0.0 with Algorithm v8.2.1 — one loop from current state to ideal state, ...
+LifeOS 7.1.1 with Algorithm v8.4.0 — one loop from current state to ideal state, ...
-Algorithm v8.2.1: every capability — context, thinking skills, research, agents, ...
+Algorithm v8.4.0: every capability — context, thinking skills, research, agents, ...
Suggestion
These strings have now rotted twice. VERSION and ALGORITHM/LATEST are already the source of truth and are read programmatically elsewhere (ArchitectureSummaryGenerator.detectAlgorithmVersion()), so the tips could interpolate them at install/merge time instead of hardcoding. That would end the class rather than the instance — otherwise the next release rots them again and someone files #1079 a third time.
Bug
LifeOS/install/settings.enhancements.jsonships two spinner tips with hardcoded version strings that are stale atmain(03a969d, v7.1.1), whereVERSIONis7.1.1andALGORITHM/LATESTis8.4.0:spinnerTipsOverride.tips[159]— "LifeOS 7.0.0 with Algorithm v8.2.1 — one loop from current state to ideal state, a claims-based ISA where each claim names its falsifying probe, fourteen-section ISA body, no effort tiers or modes."spinnerTipsOverride.tips[236]— "Algorithm v8.2.1: every capability — context, thinking skills, research, agents, audits, stronger models — exists to sharpen the ISA toward the hard-to-vary shape of done."Verify:
Both tips are two Algorithm minors behind; tips[159] is also a release behind.
Why this isn't just #1079 recurring locally
#1079 ("Thinking tip shows stale PAI/Algorithm version") was closed with:
That rationale doesn't apply this time. The stale strings are committed in the repo, in the file the installer merges — so a clean install of v7.1.1 gets them. This is the same defect class as #1079, but in the shipped artifact rather than a local carryover.
Related: the changelog claims a fix that didn't land
The v8.4.0 entry in
LIFEOS/ALGORITHM/changelog.mdlists, among its post-ship audit fixes:No bump reached
settings.enhancements.json— the tips still read v8.2.1 atmain.Fix
Both tips' claims still describe 8.4.0 accurately (the loop, the claims-based ISA, no effort tiers). Only the version strings are stale:
Suggestion
These strings have now rotted twice.
VERSIONandALGORITHM/LATESTare already the source of truth and are read programmatically elsewhere (ArchitectureSummaryGenerator.detectAlgorithmVersion()), so the tips could interpolate them at install/merge time instead of hardcoding. That would end the class rather than the instance — otherwise the next release rots them again and someone files #1079 a third time.