Adopt memory graph in agent runtime by st00pidctl · Pull Request #6 · st00pidctl/fullstack-agent · GitHub
Skip to content

Adopt memory graph in agent runtime - #6

Merged
st00pidctl merged 1 commit into
mainfrom
runtime-memory-v1.3
Aug 26, 2026
Merged

st00pidctl merged 1 commit into
mainfrom
runtime-memory-v1.3

Conversation

@st00pidctl

Copy link
Copy Markdown
Owner

Summary

  • initialize the evidence-based memory graph during bootstrap and repair
  • make memory domains operator-owned and fail closed when unconfigured
  • preserve historical claims while retiring removed domains
  • enforce active-domain, verification, correction, and relation gates at point of use
  • add the version 4 runtime configuration and an independent memory-graph verifier
  • extend fresh-VM CI and regression coverage for runtime adoption

Validation

  • bash -n on operator shell scripts
  • python -m py_compile corectl.py agentctl.py memory_engine.py memoryctl.py verify-memory-graph.py
  • python -m unittest discover -s tests -v (15 tests)
  • git diff --check
  • JSON validation for config/fullstack-agent.example.json

Scope

This phase does not change the selected reasoning core. It adds the repository-side runtime adoption and one-command repair path; applying it to the Peter VM remains an operator rollout step.

@st00pidctl
st00pidctl merged commit 95a1ac6 into main Aug 26, 2026
1 check 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