Skip to content

Retire stale v1 launch guidance - #42

Draft
JamesCarnley wants to merge 1 commit into
mainfrom
pm/stale-guidance-2026-07-23
Draft

Retire stale v1 launch guidance#42
JamesCarnley wants to merge 1 commit into
mainfrom
pm/stale-guidance-2026-07-23

Conversation

@JamesCarnley

Copy link
Copy Markdown
Member

Summary

  • mark this repository as the deployed v1/Sepolia reference during the v2 redesign
  • retire the obsolete April devnet/mainnet checklist
  • close the proxy-pattern and multi-lens questions already settled for v1

Why

The agent entrypoint still claimed an April pre-launch phase with no real data,
while Sepolia has registered schemas and real test data and the project is now
redesigning EFS from scratch. The stale checklist and questions could send an
agent into obsolete v1 launch work or make it treat v1 architecture as the v2
baseline.

Permanence tier

Ephemeral — documentation and agent-routing prose only.

Specs / ADRs touched or checked

  • docs/CHAINS.md — confirmed the 2026-06-19 Sepolia state
  • ADR-0031 — confirmed first-attester-wins for v1
  • ADR-0048 — confirmed the transparent-proxy decision
  • no specs or ADRs changed

Test plan

  • git diff --check
  • searched the edited guidance for obsolete April launch phrases

Agents involved

  • Dev: GPT-5, PM role
  • Orchestrator: James

Mark the contracts repository as the deployed v1/Sepolia reference while
EFS is redesigned from scratch as v2.

Retire the April launch checklist and close the two repo-local questions
already settled by the Sepolia deployment and ADR-0031.

Permanence-tier: Ephemeral
Co-authored-by: GPT-5 <noreply@openai.com>
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