Skip to content

add operational memory commitments#165

Merged
pmbstyle merged 1 commit into
mainfrom
feature/operational-memory-commitments
Jun 7, 2026
Merged

add operational memory commitments#165
pmbstyle merged 1 commit into
mainfrom
feature/operational-memory-commitments

Conversation

@pmbstyle

@pmbstyle pmbstyle commented Jun 7, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add a durable operational memory layer for commitments, blockers, follow-ups, decision rules, and related next actions.
  • Extract operational items semantically through the model with JSON schema output, avoiding keyword dictionaries.
  • Surface active operational memory in Octo routing context and link eligible commitments to runtime plans.
  • Resolve linked commitments from structured plan completion/blocker state and document the new memory layer.

Validation

  • uv run ruff check src/octopal/tools/plans/management.py tests/test_operational_memory.py
  • uv run pytest tests/test_operational_memory.py tests/test_plan_tools.py
  • uv run pytest (964 passed, 1 skipped)

@pmbstyle pmbstyle self-assigned this Jun 7, 2026
@pmbstyle pmbstyle marked this pull request as ready for review June 7, 2026 15:30
@pmbstyle pmbstyle merged commit 69fb3c8 into main Jun 7, 2026
4 checks passed
@pmbstyle pmbstyle deleted the feature/operational-memory-commitments branch June 7, 2026 15:30
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