Skip to content

docs(architecture): correct network clients and replay ledger (PR 27 follow-up) - #29

Merged
SomeRandmGuyy merged 2 commits into
mainfrom
bot-02-risk/pr-27-followup
Nov 1, 2026
Merged

SomeRandmGuyy merged 2 commits into
mainfrom
bot-02-risk/pr-27-followup

Conversation

@SomeRandmGuyy

@SomeRandmGuyy SomeRandmGuyy commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Owner-approved follow-up to the PR 27 review. Corrects ARCHITECTURE.md rows 31 and 33 to match the code (the offline replay CLI calls neither LaunchMonitor.stream nor GrokAgent._call; replay runs write var/replay//ledger.sqlite) and allowlists the two follow-up receipts in .gitignore. G-1 passes in diff mode for bot-02-risk paths. Receipt approved by human:SomeRandmGuyy.

RetriggerView in GreptileConfidence Score: 5/5 Tier: apex

This PR appears safe to merge.

Summary

Clarifies the offline replay path and separates the operator ledger from replay ledgers.

  • The architecture guide names the clients offline replay does not call and its separate ledger location.
  • The follow-up receipt records its approval, and both follow-up receipts are tracked in Git.

Reviews (1) · Last reviewed commit: "chore(receipts): bot-02 receipt for the ..." · Reviewed by Greptile

…PR 27 review follow-up)

The package keeps LaunchMonitor.stream and GrokAgent._call; the offline replay CLI calls neither. The operator paper ledger is var/ledger.sqlite; each recorded-data replay run writes var/replay/<dataset>/ledger.sqlite. Adds allowlist lines for the two follow-up receipts.
Approved by human:SomeRandmGuyy. Covers only the ARCHITECTURE wording and the two allowlist lines; commands and exit codes are in the receipt.
@SomeRandmGuyy
SomeRandmGuyy marked this pull request as ready for review November 1, 2026 19:53
@SomeRandmGuyy
SomeRandmGuyy merged commit 4141677 into main Nov 1, 2026
13 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.

1 participant