Skip to content

docs(rfc): propose scope sharing and processing - #2611

Draft
PsiACE wants to merge 1 commit into
masterfrom
rfcs/scope-sharing-and-processing
Draft

PsiACE wants to merge 1 commit into
masterfrom
rfcs/scope-sharing-and-processing

Conversation

@PsiACE

@PsiACE PsiACE commented Nov 12, 2026

Copy link
Copy Markdown
Member

Which issue or RFC does this PR close?

Related to #2570. Proposes the Scope sharing and processing RFC.

Rationale for this change

Team/project memory needs automatic reuse of authorized material and target-owned processed outputs. The transitional RAG collection Artifact also introduces cascading lifecycle work. Both need common Scope capabilities.

What changes are included in this PR?

  • Add English and Chinese RFCs for business relationships, continuous sharing, processing inputs and outputs, and explicit Scope lifecycle controls.
  • Compare current and proposed behavior with code evidence and ASCII examples, including responsibilities and unresolved contracts.

Are there any user-facing changes?

Documentation-only proposal. No runtime or API changes.

How was this change tested?

Validation scope: bilingual structure, pinned source links, ASCII diagrams, and MDX rendering. Runtime acceptance scenarios are specified in the RFC.

AI usage statement

OpenAI Codex assisted with drafting and evidence review, using GPT-6 Luna and GPT-6 Sol subagents.

This branch has not been deployed

No deployments
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