Skip to content

derived-freshness blocks on a fresh 8.761.0 install: state directories that do not exist yet are treated as missing manifest entries #2751

Open

Description

@gjaworski86

Version

LifeOS 8.761.0 · attestation: 8 system file(s) differ from danielmiessler/LifeOS@v8.761.0:

  • skills/LifeOS/SKILL.md
  • LIFEOS/TOOLS/models.ts
  • LIFEOS/TOOLS/model-pricing.json
  • LIFEOS/DOCUMENTATION/ARCHITECTURE_SUMMARY.md
  • LIFEOS/DOCUMENTATION/Hooks/HookSystem.md
  • LIFEOS/DOCUMENTATION/Services/BackgroundServices.md
  • LIFEOS/ALGORITHM/AlgorithmReference.md
  • LIFEOS/ERRATA/fixtures/LabelBrief.md

What is broken

On a fresh 8.761.0 install the derived-freshness integrity check blocks with six findings of the form MEMORY/STATE/<name>: surface read absent from derived-artifacts.json, for agent-jobs, checkpoints, content-pipeline, progress, taint and velocity. All six are directories that hooks and Pulse modules write into on first use (hooks/CheckpointPerISC.hook.ts:433, hooks/lib/taint.ts:18, LIFEOS/PULSE/modules/velocity.ts:14, LIFEOS/PULSE/modules/content.ts:4, LIFEOS/PULSE/modules/workflows.ts:67, hooks/LoadContext.hook.ts:335). The check means to skip directories, but it tells a directory from a file by looking at the disk (IntegrityCheck.ts:882), so a directory that does not exist yet is treated as a file artifact and required in the manifest. On a machine where those features have run, the directories exist and the check passes; on a new install none of them exists and it blocks. The reference regex at line 876 also stops at the slash, so agent-jobs never matches the agent-jobs\/ entry of the ephemeral list at line 874. The three local doc patches the attestation lists are unrelated to this check. Related but separate: the seventh derived-freshness finding on such an install, the stale skill-usewhen-index.json, is already covered by #2725 (its row for derived-artifacts.json:17). Searched issues, PRs and discussions before filing; found no thread about these six directories.

Where (file:line)

LIFEOS/TOOLS/IntegrityCheck.ts:882

Repro on a clean tree

1. Install LifeOS 8.761.0 on a clean machine. Do not use velocity sync, the content pipeline, agent jobs or per-ISC checkpoints yet.
2. Confirm that `LIFEOS/MEMORY/STATE/` has none of: agent-jobs, checkpoints, content-pipeline, progress, taint, velocity.
3. From the config root, run `bun LIFEOS/TOOLS/IntegrityCheck.ts --no-stamp --section derived-freshness`.
4. Result: six BLOCK findings, one per name above.
5. Control: create one of them as an empty directory (for example `LIFEOS/MEMORY/STATE/velocity`) and rerun; that finding disappears, which shows the result depends on disk state, not on the manifest.

Negative control

Probe: bun LIFEOS/TOOLS/IntegrityCheck.ts --no-stamp --section derived-freshness --json | grep -E 'surface read absent|totalBlocking' · exit 0 · captured 2026-11-11T08:55:14.741Z

Red looks like: surface read absent from derived-artifacts.json

  "totalBlocking": 6,
          "detail": "MEMORY/STATE/agent-jobs: surface read absent from derived-artifacts.json",
          "detail": "MEMORY/STATE/checkpoints: surface read absent from derived-artifacts.json",
          "detail": "MEMORY/STATE/content-pipeline: surface read absent from derived-artifacts.json",
          "detail": "MEMORY/STATE/progress: surface read absent from derived-artifacts.json",
          "detail": "MEMORY/STATE/taint: surface read absent from derived-artifacts.json",
          "detail": "MEMORY/STATE/velocity: surface read absent from derived-artifacts.json",

Suggested fix

Suggestion, not tested: decide "directory or file" from the source text, not from the disk. Let the reference regex at IntegrityCheck.ts:876 capture a trailing slash when one follows the name, and skip a reference that ends in a slash; the ephemeral list at line 874 then matches agent-jobs/ as written. For names used without a slash, a "kind": "directory" entry in derived-artifacts.json would state the intent once for every install. The alternative of having the installer create the six empty directories would also turn the check green, but it keeps the result tied to disk state and breaks again with the next new state directory.

Environment

  • OS: macOS 27.2 (arm64)
  • Harness: claude-code
  • bun: 1.4.4 · git: 2.54.0
  • Doctor broken: none

Activity

  1. Luo0oo commented on Nov 15, 2026

    @Luo0oo

    Note

    🤖 Harper (AI assistant) responding on behalf of Luo

    Two more derived-freshness cases from the 8.761.0 payload, beside the missing-directory case in this issue:

    A. MEMORY/STATE paths that payload code uses are missing from the manifest. LIFEOS/TOOLS/derived-artifacts.json has 25 entries and none for these paths:

    Path Payload code that reads it
    MEMORY/STATE/agent-jobs LIFEOS/PULSE/modules/workflows.ts (AGENT_JOB_STATE_DIR, which resolves to LIFEOS/USER/MEMORY/STATE/agent-jobs, not the LIFEOS/MEMORY/STATE/agent-jobs the check looks for)
    MEMORY/STATE/checkpoints hooks/CheckpointPerISC.hook.ts
    MEMORY/STATE/content-pipeline LIFEOS/PULSE/modules/content.ts, via LIFEOS/TOOLS/Conveyor/Ledger.ts
    MEMORY/STATE/progress LIFEOS/TOOLS/SessionProgress.ts
    MEMORY/STATE/taint hooks/lib/taint.ts
    MEMORY/STATE/velocity LIFEOS/PULSE/modules/velocity.ts (written by LIFEOS/TOOLS/VelocityDeeds.ts)

    The check runs only on installs with a git checkout (IntegrityCheck.ts:862) and skips directories that exist (:882). On such an install, absent paths that its text scan finds in the code (comments included, :876-887) become manifest-gap findings, so other STATE paths can show up the same way. The general fix is a manifest entry per artifact the code reads, with its writer and maxAgeHours (or null for stamps), or a rule that skips directory prefixes.

    B. skill-usewhen-index.json has no live writer. The manifest says this file is "refreshed by the per-turn Algorithm nudge hook" (maxAgeHours: 24). In 8.761.0, hooks/AlgorithmNudge.hook.ts still defines loadIndex() at :691, which spawns --rebuild-index when the index is stale, but nothing calls it any more. git log -S 'loadIndex()' -- install/hooks/AlgorithmNudge.hook.ts places the change in fb9aef4 (release 8.761.0), which removes const idx = loadIndex();. The other uses of the index path are the --rebuild-index branch at :1061, reachable only by running the hook with that flag, and the read inside loadIndex.

    So once the file exists, it becomes blocking when its mtime passes 24 hours and stays red unless it is rebuilt by hand. An absent index produces no age finding. Either restore the call, or retire the index, loadIndex, the rebuild branch and the manifest row together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions