Skip to content

chore: merge main 3045d54 into release/phase1 (D2, keeps #376 conflict-free) - #423

Merged
cyberia-apparatus merged 5 commits into
release/phase1from
sync/main-3045d54
Oct 27, 2026
Merged

cyberia-apparatus merged 5 commits into
release/phase1from
sync/main-3045d54

Conversation

@cyberia-apparatus

Copy link
Copy Markdown

What

Merges main 3045d54 into release/phase1 (plan D2, for R0). main gained four commits of the owner's after 2e5ba00, the base soft3#376 was opened on. As a result, release/phase1 was 4 behind main (git rev-list --left-right --count origin/main...origin/release/phase1 → 4 358):

  • 130ceed docs: cyberia foundation pages moved to the repo root
  • ff06667 mimi: the project is closed and removed
  • 9d6f5e5 proposals(state-economics)
  • 3045d54 agents: one instruction file, AGENTS.md; CLAUDE.md is gone

Verified

  • git merge-base origin/main origin/release/phase1 = 2e5ba00, and git merge-tree --write-tree is clean (exit 0). The merge commit's tree equals that result.
  • The merge changes five files: CLAUDE.md => AGENTS.md, docs/README.md, proposals/README.md, proposals/metabolic-oracle.md and proposals/state-economics.md (+90 −5). release/phase1 never edited any of them since 2e5ba00. No specs/ file is touched, and no code, crate or workflow changes.
  • git grep 'CLAUDE\.md' over release/phase1's *.py *.yml *.sh *.nu *.toml *.rs finds nothing. No gate or workflow reads the renamed file.

Remains

After this merges, #376 is again 0 behind main, with no conflict, and still waits on the owner's review.

Risk

Low. This is the owner's own text, already on main. The diff of release/phase1 → main (#376) does not change.

🤖 Generated with Claude Code

mastercyb and others added 5 commits October 23, 2026 14:16
…achine forever — spec-ifies steps-blocks-epochs §3e

two products: writing state is energy (landauer, one-time at the margin), holding is persistence (free forever — no rent, no dormancy, no eviction, zero mortality terms). four rules + one curve: net-new slots priced W0×M(phi) on the 1-2-4-8 occupancy ladder, payable as burn (ephemeral) or lock (reservation, unlock on delete — the no-death mechanism for long-term agents); expansion valve at sustained 75%; security funded by one asymptotic curve supply(h)=C(1-q^h) with C <= field size — eternal budget with a provable cap, rent as a class dies. survey: nervos' two-layer structure + parano1d's pricing + the closing curve; W0 anchored to the block reward, not a constant. six-number complexity budget; open questions: per-dim phi, lock k, rescaled expansion window for 1 s steps, machine share
…conflict-free (D2)

main gained four commits of the owner's after 2e5ba00, the base #376 was
opened on: 130ceed (docs: foundation pages), ff06667 (mimi removed),
9d6f5e5 (proposals: state-economics), 3045d54 (CLAUDE.md -> AGENTS.md).
They touch five doc and proposal files that release/phase1 never edited;
git merge-tree is clean, and no code or workflow reads CLAUDE.md.
@cyberia-apparatus cyberia-apparatus added contained lane: contained (deliver.md § lanes) ready agent-reviewed, green, waiting for a merge labels Oct 27, 2026
@cyberia-apparatus
cyberia-apparatus merged commit 4ae13d9 into release/phase1 Oct 27, 2026
cyberia-apparatus added a commit that referenced this pull request Oct 27, 2026
…t-free again

Both sides renamed CLAUDE.md to AGENTS.md (#406 and the main sync #423);
GitHub's merge check reports the rename/rename as a conflict. The merged
AGENTS.md is #407's (blob 3eedb35), a superset of release/phase1's (513321e):
the crate/ row, the cybernode boundary, the node-status note. No other file
overlaps; no code, specs or lock changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contained lane: contained (deliver.md § lanes) ready agent-reviewed, green, waiting for a merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants