Skip to content

CHANGE_REJECTED: Repository error: Invalid operation: tree projection kind for inode 106 disagrees with DIRECTORIES #291

Open

Description

@stanheckman

Claude's calls to "atomic record" fail.

Here are my calls to "atomic doctor check" and my attempt to repair.

b$ atomic doctor check
ℹ Verifying native derived indexes against graph authority...
⚠ 64 native derived-index problem(s) found:
✗ TREE missing row 'voltageStateMachine_v25.c' expected=11
✗ TREE stale row 'baseline' actual=115
✗ TREE stale row 'baseline/protoread.c' actual=112
✗ TREE stale row 'baseline/voltage_state_machine.c' actual=113
✗ TREE stale row 'baseline/voltage_state_machine.h' actual=114
✗ TREE stale row 'dbook.tgz' actual=137
✗ TREE stale row 'disturbance_examples_2' actual=119
✗ TREE stale row 'disturbance_examples_3' actual=138
✗ TREE stale row 'event-truth-806a10315682-20260914T130508047-rising.png' actual=120
✗ TREE stale row 'event-truth-806a10315682-20260914T130508372-falling.png' actual=126
✗ TREE stale row 'event-truth-806a1034c284-20260922T131925414-rising.png' actual=131
✗ TREE stale row 'tools/fetch_minutes.py' actual=139
✗ TREE stale row 'tools/find_disturbances.py' actual=117
✗ TREE stale row 'transcripts' actual=118
✗ TREE stale row 'transcripts/prototype-half-cycle-algorithms' actual=116
✗ TREE stale row 'zoomedbigfonts1.png' actual=136
✗ REV_TREE missing row '11' expected=voltageStateMachine_v25.c
✗ REV_TREE stale row '112' actual=baseline/protoread.c
✗ REV_TREE stale row '113' actual=baseline/voltage_state_machine.c
✗ REV_TREE stale row '114' actual=baseline/voltage_state_machine.h
✗ REV_TREE stale row '115' actual=baseline
✗ REV_TREE stale row '116' actual=transcripts/prototype-half-cycle-algorithms
✗ REV_TREE stale row '117' actual=tools/find_disturbances.py
✗ REV_TREE stale row '118' actual=transcripts
✗ REV_TREE stale row '119' actual=disturbance_examples_2
✗ REV_TREE stale row '120' actual=event-truth-806a10315682-20260914T130508047-rising.png
✗ REV_TREE stale row '126' actual=event-truth-806a10315682-20260914T130508372-falling.png
✗ REV_TREE stale row '131' actual=event-truth-806a1034c284-20260922T131925414-rising.png
✗ REV_TREE stale row '136' actual=zoomedbigfonts1.png
✗ REV_TREE stale row '137' actual=dbook.tgz
✗ REV_TREE stale row '138' actual=disturbance_examples_3
✗ REV_TREE stale row '139' actual=tools/fetch_minutes.py
✗ INODES missing row '121' expected=81:7488157
✗ INODES missing row '122' expected=81:4350364
✗ INODES missing row '123' expected=81:2716842
✗ INODES missing row '124' expected=81:9513236
✗ INODES missing row '125' expected=81:5118223
✗ INODES missing row '127' expected=81:2345883
✗ INODES missing row '128' expected=81:14655054
✗ INODES missing row '129' expected=81:2129464
✗ INODES missing row '130' expected=81:11601089
✗ INODES missing row '132' expected=81:10495494
✗ INODES missing row '133' expected=81:3428034
✗ INODES missing row '134' expected=81:1442218
✗ INODES missing row '135' expected=81:9790226
✗ REV_INODES missing row '81:10495494' expected=132
✗ REV_INODES missing row '81:11601089' expected=130
✗ REV_INODES missing row '81:1442218' expected=134
✗ REV_INODES missing row '81:14655054' expected=128
✗ REV_INODES missing row '81:2129464' expected=129
✗ REV_INODES missing row '81:2345883' expected=127
✗ REV_INODES missing row '81:2716842' expected=123
✗ REV_INODES missing row '81:3428034' expected=133
✗ REV_INODES missing row '81:4350364' expected=122
✗ REV_INODES missing row '81:5118223' expected=125
✗ REV_INODES missing row '81:7488157' expected=121
✗ REV_INODES missing row '81:9513236' expected=124
✗ REV_INODES missing row '81:9790226' expected=135
✗ DIRECTORIES stale row '104' actual=0x01
✗ DIRECTORIES stale row '106' actual=0x01
✗ DIRECTORIES stale row '115' actual=0x01
✗ DIRECTORIES stale row '118' actual=0x01
✗ DIRECTORIES stale row '77' actual=0x01
✗ DIRECTORIES stale row '82' actual=0x01
Run atomic doctor repair-native-indexes to rebuild derived caches atomically from graph and change facts.
✗ Internal error: native derived-index verification found 64 problem(s)

Hint: This appears to be a bug. Please report it at: https://github.com/atomicdotdev/atomic/issues
b$ cd /2026/hcc && atomic doctor repair-native-indexes
cd /2026/hcc && atomic doctor check
ℹ Rebuilding native derived indexes from graph authority...
✓ Repaired 64 native derived-index problem(s); wrote 508 rows atomically; journaled as operation HTZNEYRY6XDS2JFDJ3NRZIFYOGCMUTECPII2NDGUSMIYY36ALEIQ.
ℹ Verifying native derived indexes against graph authority...
✓ Native derived indexes are consistent (508 rows).
Verifying working-copy consistency against the graph...
ℹ Checked 46 clean file(s); 0 with uncommitted edits skipped; 0 conflicted.
✓ Working copy is consistent with the graph.

That message seems encouraging, but Claude still can't record anything after this check. Claude reports:

Why nothing has recorded: every atomic record here fails with:
✗ atomic:CHANGE_REJECTED: Repository error: Invalid operation: tree projection kind for inode 106 disagrees with DIRECTORIES

  • The end-of-turn hook almost certainly hits the same error. Its failures are hidden, which is why nothing has been recorded since 01:07.
  • I re-ran atomic doctor check in /2026/hcc and it passes (534 rows consistent).
  • Recording only plothc.py, plot_voltage_state.py, reconstruct_vctcxo_zcticks.py and .atomicignore gives the same error, so it isn't caused by the new or re-added files.
  • Before the repair, inode 106 was one of the directory entries the doctor flagged ("DIRECTORIES stale row '106'"). Its current check doesn't look at whatever is still inconsistent, so
    repair-native-indexes doesn't fix it.

I've stopped trying further atomic repairs. I don't know atomic's internals well enough to guess safely, and these commands change the shared repository.

Suggested next steps:

  1. Report it to atomic. Their error message asks for that (https://github.com/atomicdotdev/atomic/issues). Include the record error above and the doctor output you pasted.

Is this a bug, or should I just be trying "atomic doctor reconcile-working-copy"?

Activity

  1. leefaus commented on Oct 28, 2026

    @leefaus
    Contributor

    2 things:

    1. can you run at atomic --version
    2. what where you doing at the time when did the record. was this agent initiated or just a manual record?
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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions