Skip to content

docs(board): DISCOVERY-MAP and EPIPHANIES frozen; new entries go to Linear - #372

Merged
AdaWorldAPI merged 1 commit into
mainfrom
ccr-7a4f3a52-1mvica
Nov 6, 2026
Merged

AdaWorldAPI merged 1 commit into
mainfrom
ccr-7a4f3a52-1mvica

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Shared append-only ledgers conflicted in every concurrent session: in report-rs, two sessions each wrote a D-39 at the same time. New entries now go to Linear, one issue each, so no two sessions share a file or a counter. Decision: Linear EXO-187.

Epiphanies and discoveries stay separate

  • New discoveries go to OGAR · Discovery Map (P-EXO-15), titled DISCOVERY: D-<NAME> — <claim>. Grade, status and home are recorded on the issue, and dependencies become Linear relations, so the map keeps its topology.
  • New epiphanies go to OGAR · Epiphanies (P-EXO-16).
  • Decisions go to P-EXO-14, and agent coordination goes to the A2A board P-EXO-13.

In the repo

  • docs/DISCOVERY-MAP.md and .claude/board/EPIPHANIES.md each get a freeze notice. No entry is changed, and every D-… and E-… id stays citable. DISCOVERY-MAP §6 says rules 1–5 still govern the entries already in the file.
  • Every instruction that writes to either file now points at the Linear projects: CLAUDE.md (doc family item 1, the append-only-canon rule with the board list and tier split), .claude/AGENTS.md, .claude/VISION.md, docs/INTEGRATION-MAP.md §10, docs/INTEGRATION-TEST-PLAN.md, .claude/board/LATEST_STATE.md.
  • The doctrine-keeper and runtime-archaeologist cards now also check P-EXO-15, so audits cover discoveries filed after the freeze.
  • References that only cite an id are unchanged.

Behaviour: none, docs only.


Generated by Claude Code

…inear

Shared append-only ledgers conflicted in every concurrent session. Both
files stay as the historical record (no entry changed; every D-/E- id stays
citable) and carry a freeze notice. New discoveries go to Linear OGAR ·
Discovery Map (P-EXO-15), new epiphanies to OGAR · Epiphanies (P-EXO-16),
kept separate; decisions to P-EXO-14; agent coordination to the A2A board
P-EXO-13. CLAUDE.md, AGENTS.md, VISION.md, INTEGRATION-MAP §10,
INTEGRATION-TEST-PLAN, LATEST_STATE and the doctrine-keeper /
runtime-archaeologist cards are redirected. Decision: Linear EXO-187.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XAqKMM44PgMCtYoqx6XYnh
@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 375f0251-d48d-4663-855f-5cc810fff538
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review November 6, 2026 23:35
@AdaWorldAPI
AdaWorldAPI merged commit 1074774 into main Nov 6, 2026
4 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-06T23:36:10.801913Z 6b4bdcb Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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