Skip to content

draft: evaluate scope organization runtime for RFC #1345 - #1401

Draft
PsiACE wants to merge 17 commits into
masterfrom
codex/scope-organization-runtime
Draft

draft: evaluate scope organization runtime for RFC #1345#1401
PsiACE wants to merge 17 commits into
masterfrom
codex/scope-organization-runtime

Conversation

@PsiACE

@PsiACE PsiACE commented Aug 30, 2026

Copy link
Copy Markdown
Member

Note

This draft PR is an implementation probe for #1345. It makes the affected behavior and code paths reviewable. It is not proposed as a merge-ready product change.

Which issue or RFC does this PR close?

Related to #1345.

Rationale for this change

The Scope model in #1345 affects storage, runtime queries, reports, and Agent integrations. This branch applies the model across those paths so reviewers can assess its behavior, impact, and implementation cost.

What changes are included in this PR?

Area Coverage
Scope model Durable hierarchy, metadata, bindings, and direct references
Artifacts Exact revision references across Scope boundaries
Runtime Scope-based context reads and statistics aggregation
Handoff Scope selection, exact references, and report generation
Agent integrations Session or workspace Scope binding for Codex, Claude Code, WorkBuddy, and Hermes
Interfaces HTTP API, MCP, generated clients, Dashboard views, and configuration
Cleanup Removal of the Project and Workstream report model and its compatibility paths
Validation Unit, integration, E2E, contract, documentation, and build checks

Are there any user-facing changes?

Yes. If adopted, this design would be breaking:

  • Project and Workstream report APIs and persisted state are removed.
  • Scope selection becomes the common boundary for context, reports, and statistics.
  • Agent integrations must create, resolve, or reuse a Scope binding.
  • No compatibility or migration period is included in this evaluation.

How was this change tested?

  • make check
  • make test: 920 passed, 10 skipped
  • make docs-test
  • make build

AI usage statement

OpenAI Codex with GPT-5 was used for code analysis, implementation, tests, and documentation editing.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

license-eye has checked 978 files.

Valid Invalid Ignored Fixed
704 21 253 0
Click to see the invalid file list
  • integrations/codex/plugins/powercontext/hooks/bind_tools.py
  • integrations/codex/plugins/powercontext/hooks/session_binding.py
  • integrations/codex/plugins/powercontext/scripts/scope_binding.py
  • src/powercontext/builtin/handoff_report/init.py
  • src/powercontext/builtin/handoff_report/adapters.py
  • src/powercontext/builtin/handoff_report/canonical.py
  • src/powercontext/builtin/handoff_report/errors.py
  • src/powercontext/builtin/handoff_report/protocols.py
  • src/powercontext/builtin/handoff_report/rendering.py
  • src/powercontext/builtin/scope/init.py
  • src/powercontext/builtin/scope/application.py
  • src/powercontext/builtin/scope/errors.py
  • src/powercontext/builtin/scope/models.py
  • src/powercontext/builtin/scope/repository.py
  • src/powercontext/server/static/handoff-report.js
  • src/powercontext/server/static/scope-selection.js
  • src/powercontext/server/templates/pages/handoff_report.html
  • tests/builtin/test_scope_application.py
  • tests/codex_plugin/test_scope_binding.py
  • tests/test_handoff_report.py
  • tests/test_scope_api.py
Use this command to fix any missing license headers
```bash

docker run -it --rm -v $(pwd):/github/workspace apache/skywalking-eyes header fix

</details>

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