Skip to content

Establish ORBISTIUM current accepted-epoch object#37

Merged
verifrax-systems merged 1 commit into
mainfrom
midiakiasat/orbistium-accepted-epoch-object-minimum
Apr 18, 2026
Merged

Establish ORBISTIUM current accepted-epoch object#37
verifrax-systems merged 1 commit into
mainfrom
midiakiasat/orbistium-accepted-epoch-object-minimum

Conversation

@midiakiasat

Copy link
Copy Markdown
Member

Purpose

Publish the current accepted-epoch object as a first-class public object for ORBISTIUM canonical state.

Changes

  • add epochs/current/accepted-epoch-0001.json
  • add epochs/history/README.md
  • extend README.md so the public surface explicitly names the current accepted-epoch object
  • extend WORLD.md so retention doctrine points to the current accepted-epoch object and historical accepted-epoch archive
  • add machine check tests/test_accepted_epoch_object.py

Result

ORBISTIUM now exposes one machine-readable current accepted-epoch object for canonical world-state truth instead of leaving the active accepted-epoch surface compressed only across current/epoch.json, doctrine text, and archive prose.

@verifrax-systems verifrax-systems left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current accepted-epoch object is explicit, machine-readable, and aligned to ORBISTIUM canonical-state doctrine. Approved.

@verifrax-systems
verifrax-systems merged commit bf7fa89 into main Apr 18, 2026
2 checks passed
@verifrax-systems
verifrax-systems deleted the midiakiasat/orbistium-accepted-epoch-object-minimum branch April 18, 2026 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants