Skip to content

Consume runtime state as memory posture#65

Merged
mdheller merged 4 commits into
mainfrom
work/runtime-state-memory-consumer
Jun 1, 2026
Merged

Consume runtime state as memory posture#65
mdheller merged 4 commits into
mainfrom
work/runtime-state-memory-consumer

Conversation

@mdheller
Copy link
Copy Markdown
Member

@mdheller mdheller commented Jun 1, 2026

Purpose

Continue the runtime parity bridge by adding Superconscious/Subconscious memory posture fixtures for Sociosphere runtime states.

Scope

This PR adds:

  • examples/runtime-state-memory-event.allocated.json
  • examples/runtime-state-memory-event.failed.json
  • scripts/validate-runtime-state-memory.py
  • .github/workflows/state-memory.yml

Posture

For runtime_allocated, memory records allocated-but-not-certified state, requires human review, and preserves teardown/leak-check blocking gaps.

For runtime_failed, memory records failed-and-not-certified state, requires operator review, forces report-only planning bias, and preserves runtime failure gaps.

Boundary

Superconscious consumes Sociosphere runtime state as memory and planning context only. It does not execute environment actions, run Sociosphere commands, issue or verify receipts, certify runtime parity, or grant autonomy. Subconscious remains non-authority.

Expected validation

  • python3 scripts/validate-runtime-state-memory.py

@mdheller mdheller merged commit 8ae3265 into main Jun 1, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant