Skip to content

docs: reframe roadmap callout as forward-looking, not defensive - #25

Merged
Protocol-zero-0 merged 1 commit into
mainfrom
docs/readme-roadmap-callout
May 14, 2026
Merged

docs: reframe roadmap callout as forward-looking, not defensive#25
Protocol-zero-0 merged 1 commit into
mainfrom
docs/readme-roadmap-callout

Conversation

@Protocol-zero-0

Copy link
Copy Markdown
Owner

Summary

Tightens the one-line callout above the SWE-bench worked example. The previous wording repeated "not a logged run / not a checked-in artifact / for runs you can reproduce today" — three negations in two sentences that telegraph absence rather than direction.

Same honest disclosure ("this is v1.1, not already shipped"); lower defensive register.

Diff

Before

📋 ROADMAP TARGET · NOT A LOGGED RUN. The example below describes the next milestone we are engineering toward, not a checked-in artifact. When the run lands, the full ledger will be committed under `evidence/` and this README will link to it. For runs you can reproduce today, see `examples/sandbox_demo/` and the 99-test suite in `tests/`.

After

📋 Next milestone (v1.1). The example below is the run we are engineering toward as v1.1 — a single overnight evolution on SWE-bench Verified, end-to-end. Once it lands, the full ledger lands under `evidence/` and gets linked from here. Reproducible v1.0 artifacts are `examples/sandbox_demo/`, the 99-test suite in `tests/`, and the capabilities listed above.

Test plan

  • No code changes. Test suite untouched.
  • Both README.md and README.zh.md in lock-step.

🤖 Generated with Claude Code

The previous callout repeated the same caveat three times: "not a
logged run", "not a checked-in artifact", "for runs you can
reproduce today, see ..." — a triple negation that telegraphs
absence rather than direction.

This pass keeps the honesty (still clearly marked as v1.1, not
already shipped) but reframes the language toward what is coming
and what is already here, rather than what is missing:

- "ROADMAP TARGET · NOT A LOGGED RUN" → "Next milestone (v1.1)"
- "describes the next milestone we are engineering toward, not a
   checked-in artifact" → "the run we are engineering toward as
   v1.1 — a single overnight evolution on SWE-bench Verified,
   end-to-end"
- "For runs you can reproduce today, see ..." → "Reproducible v1.0
   artifacts are ..." (declarative, not contrastive)

Same disclosure, lower defensive register.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 14, 2026 06:15

Copilot AI 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.

Pull request overview

Documentation-only tweak rewording the v1.1 roadmap callout above the SWE-bench worked example in both README files to a more forward-looking tone, without changing meaning or links.

Changes:

  • Reframe callout from "ROADMAP TARGET · NOT A LOGGED RUN" to "Next milestone (v1.1)".
  • Keep the same disclosure that v1.1 is not yet shipped and point to v1.0 reproducible artifacts.
  • Apply identical change to the Chinese README to keep them in lock-step.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
README.md Rewords the v1.1 callout block to a forward-looking tone.
README.zh.md Mirrors the English README wording change.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Protocol-zero-0
Protocol-zero-0 merged commit 910fe9c into main May 14, 2026
6 checks passed
@Protocol-zero-0
Protocol-zero-0 deleted the docs/readme-roadmap-callout branch May 14, 2026 06:19
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.

2 participants