Skip to content

docs(jarvis): ADR 0009 links the inbox 0012 by file; one rollover instruction; provenance and portfolio scope - #131

Merged
chrisohearn merged 2 commits into
integration/mcp-events-20261109from
docs/jarvis-mirror-sweep-20261116
Nov 16, 2026
Merged

chrisohearn merged 2 commits into
integration/mcp-events-20261109from
docs/jarvis-mirror-sweep-20261116

Conversation

@chrisohearn

Copy link
Copy Markdown
Owner

A docs-only mirror from the private connector repo, which is the source of truth for docs/jarvis. There is no code change.

  • ADR 0009: "(0012, 0014)" pointed at an ambiguous 0012, because two ADRs share that number. It now links 0012-inbox-subscriptions-and-the-heartbeat.md by file.

  • COORDINATORS.md: the rollover section opened with the pre-switch guarantee (the seed holds the thread's unfinished rows) and then overrode it with a 2026-11-14 note. It now gives one current procedure:

    1. update the sidecar;
    2. queue the rollover;
    3. re-read the work list from the sidecar, plus approval rows on this ledger.

    The seed and portfolio_status are described as pre-switch views that go when the fork retires.

  • ADR 0020:

    • A work-state write that still lands on this ledger after the cutover shows in portfolio_status until the reconciliation sweep replays it.
    • The rollover seed is documented as a pre-switch view rather than "tracked" for a fix.
  • ADR 0012: "changedByClient is null" now applies to sidecar history only. Approval-bearing rows that stay on this ledger still get T3's server-recorded senders. It also says the stdio caller label now carries the T3 thread id.

🤖 Generated with Claude Code

…truction; provenance and portfolio scope

Docs-only mirror from the private connector repo:
- ADR 0009's "(0012, 0014)" pointed at an ambiguous 0012; it now links the
  inbox-subscriptions ADR by file.
- COORDINATORS.md gives one current rollover procedure instead of the
  pre-switch seed guarantee followed by an override. The seed and
  portfolio_status are described as pre-switch views that go with the fork.
- ADR 0020: a work-state write still landing on this ledger after the
  cutover shows in portfolio_status until replayed; the seed is documented,
  not fixed.
- ADR 0012: "changedByClient is null" applies to sidecar history only;
  approval rows kept on this ledger still get server-recorded senders. The
  stdio caller label now carries the T3 thread id.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 16, 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-16T08:07:02.315418Z faeb73a New commits
🔒 Security Review ✅ Completed 2026-11-16T08:07:37.083553Z faeb73a New commits
ℹ️ 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.

…ported provenance; persistent stragglers

Mirrors the review repair in the private connector repo:
- rollover updates work kept whole on this ledger here, never in the
  sidecar, and re-reads every owned row that carries or once carried an
  approval;
- history imported from the fork keeps its server-recorded changedByClient;
- a replayed straggler keeps showing in portfolio_status.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chrisohearn

Copy link
Copy Markdown
Owner Author

Review reconciliation before merge, head faeb73a:

  • Hosted Codex review of faeb73a: completed with no findings.
  • CI: Lint, Check, Changes, Agent context budget and Test Server 1–8 pass. The other jobs are skipped for a docs-only change.
  • Content: the four changed files match the connector's merged copy, except where the fork already keeps the connector's issue numbers out. That covers the review repair the connector's hosted review asked for (approval-exception rows stay on this ledger through rollover; imported provenance; persistent stragglers).
    Docs-only. No code change.

@chrisohearn
chrisohearn merged commit d96ce1b into integration/mcp-events-20261109 Nov 16, 2026
18 checks passed
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