neuron-technologies/neuron
3
0
Fork 0
Code Issues 44 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

Reshape fb0bb55 boot-counter to be immutability-safe (stop per-boot tombstone accrual) #106

New Issue
Open
opened 2026-08-03 18:55:05 +00:00 by will.anderson · 1 comment
will.anderson commented 2026-08-03 18:55:05 +00:00
Owner
Copy Link
Copy Source

Tag: POST-BETA · ORTHOGONAL
Owner: @tim.lingo

Why

The boot counter added in fb0bb55 does an HTTP DELETE + create every boot, so it accrues one tombstone per boot for what is just a plumbing counter. That quietly pollutes the immutability arc (tombstones are meant to record real deletions of real content, not restart bookkeeping).

Fix

Replace the delete+create pattern with either:

  • an idempotent soul-state counter (in-place state that isn't part of the immutable memory graph), or
  • a supersede of a single counter node (one live node, history preserved) instead of delete+recreate.

Whichever keeps the memory graph honest: no tombstone should be generated by a normal boot.

Acceptance criteria

  • Booting the soul N times produces zero new tombstones from the counter.
  • The counter still reports an accurate boot count.
  • Reference commit: fb0bb55.
**Tag:** POST-BETA · ORTHOGONAL **Owner:** @tim.lingo ## Why The boot counter added in `fb0bb55` does an HTTP **DELETE + create every boot**, so it accrues **one tombstone per boot** for what is just a plumbing counter. That quietly pollutes the immutability arc (tombstones are meant to record real deletions of real content, not restart bookkeeping). ## Fix Replace the delete+create pattern with either: - an **idempotent soul-state counter** (in-place state that isn't part of the immutable memory graph), or - a **supersede** of a single counter node (one live node, history preserved) instead of delete+recreate. Whichever keeps the memory graph honest: no tombstone should be generated by a normal boot. ## Acceptance criteria - Booting the soul N times produces **zero new tombstones** from the counter. - The counter still reports an accurate boot count. - Reference commit: `fb0bb55`.
will.anderson added the POST-BETAORTHOGONAL labels 2026-08-03 18:55:05 +00:00
tim.lingo was assigned by will.anderson 2026-08-03 18:55:06 +00:00
will.anderson commented 2026-08-03 19:17:01 +00:00
Author
Owner
Copy Link
Copy Source

@tim.lingo Design decision is yours: replace the fb0bb55 delete+create boot counter with (a) an idempotent soul-state counter outside the immutable graph, or (b) a single-node supersede? Which do you want to take?

@tim.lingo Design decision is yours: replace the fb0bb55 delete+create boot counter with (a) an idempotent soul-state counter outside the immutable graph, or (b) a single-node supersede? Which do you want to take?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BETA-CRITICAL
On the beta critical path — must resolve before ship
 blocks-public-beta
Must be fixed before any public beta
 HELD
Blocked pending an external decision (counsel / dual sign-off)
 ORTHOGONAL
Parallel workstream (testing/hardening) — safe to assign off critical path
 P0
Drop-everything severity
 POST-BETA
Important but not blocking the beta ship
 security
Security vulnerability
No labels ORTHOGONAL POST-BETA
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
andre.almeida (Andre Almeida) tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees tim.lingo
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron#106
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?