docs(rfc): define long-horizon workloads - #1229
Merged
Merged
Conversation
This was referenced Aug 13, 2026
PsiACE
marked this pull request as ready for review
August 13, 2026 11:10
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new RFC proposal describing a unified workload contract for deterministic and long-horizon (model-backed) Memory evaluation, intended to define the acceptance/evidence/artifact/rescoring contracts before implementation lands in the stacked PRs.
Changes:
- Add new RFC document in English and Chinese describing unified workloads and long-horizon Memory evaluation.
- Link the new RFC from the docs navigation for both locales.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
zensical.toml |
Adds the new RFC to the English/Chinese RFC navigation. |
docs/en/rfcs/0000_unified_workloads_and_long_horizon_memory_evaluation.md |
Introduces the English RFC text for unified workloads/long-horizon evaluation. |
docs/zh/rfcs/0000_unified_workloads_and_long_horizon_memory_evaluation.md |
Introduces the Chinese RFC text for unified workloads/long-horizon evaluation. |
Suppressed comments (1)
zensical.toml:90
- 中文 RFC nav 条目目前指向
0000_...文件名，并使用了“RFC 提案”这种特殊标题。根据 RFC 流程说明（docs/zh/rfcs/README.md），PR 打开后应将 RFC 编号/文件名前缀改为与 PR 编号一致（1229），因此需要同步更新这里的路径与标题。
{ "RFC 提案：统一工作负载与长程 Memory 评估" = "zh/rfcs/0000_unified_workloads_and_long_horizon_memory_evaluation.md" },
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| @@ -0,0 +1,298 @@ | |||
| - Proposal Name: `unified_workloads_and_long_horizon_memory_evaluation` | |||
| - Start Date: 2026-08-13 | |||
| - RFC PR: [oceanbase/powercontext#0000](https://github.com/oceanbase/powercontext/pull/0000) | |||
| { "0051 Experience and Skill Artifact Families" = "en/rfcs/0051_experience_skill_artifact_families.md" }, | ||
| { "0080 Memory Search Reranking" = "en/rfcs/0080_memory_search_reranking.md" }, | ||
| { "0081 End-to-end Evaluation Architecture" = "en/rfcs/0081_end_to_end_evaluation_architecture.md" }, | ||
| { "RFC Proposal: Unified Workloads and Long-horizon Memory Evaluation" = "en/rfcs/0000_unified_workloads_and_long_horizon_memory_evaluation.md" }, |
| @@ -0,0 +1,271 @@ | |||
| - Proposal Name: `unified_workloads_and_long_horizon_memory_evaluation` | |||
| - Start Date: 2026-08-13 | |||
| - RFC PR: [oceanbase/powercontext#0000](https://github.com/oceanbase/powercontext/pull/0000) | |||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack
Merge in this order.
Which issue or RFC does this PR close?
Introduces RFC 1229, Unified Workloads and Long-Horizon Memory Evaluation.
Rationale for this change
Define one workload and acceptance contract before adding the implementation layers.
What changes are included in this PR?
modelcapability.Are there any user-facing changes?
Documentation only.
How was this change tested?
make docs-testAI usage statement
OpenAI Codex (GPT-5) assisted with the RFC structure and wording. The author is responsible for the submitted changes.