Skip to content

docs(backlog): B5 — event-sourced ledger RFC (tracks #97)#98

Merged
Knapp-Kevin merged 1 commit into
BicameralAI:devfrom
Knapp-Kevin:docs/backlog-event-sourcing-rfc
Apr 29, 2026
Merged

docs(backlog): B5 — event-sourced ledger RFC (tracks #97)#98
Knapp-Kevin merged 1 commit into
BicameralAI:devfrom
Knapp-Kevin:docs/backlog-event-sourcing-rfc

Conversation

@Knapp-Kevin

Copy link
Copy Markdown
Collaborator

Summary

Why

A contributor suggestion arrived during PR #93 review (out of scope for that PR): make the runtime ledger append-only event-sourced with SurrealDB/SQLite as a rebuildable projection. After analysis the conclusion was "v1.0.0 territory, blocked on team-sync roadmap call" — not actionable now, but worth tracking.

Issue #97 carries the full analysis, costs/benefits, the proposed v0.14.0 wedge (extend CHANGEFEED to all mutation-bearing tables), and the open questions for Jin. This PR just logs it in BACKLOG so it doesn't get lost.

Linked

Refs #97

Test plan

  • BACKLOG entry renders cleanly
  • Format matches existing B# entries (multi-line description with rationale)
  • No code changes; no skill changes; no schema changes

Plan / Audit / Seal

Plan: trivial; risk:L1 (single-file docs change, single BACKLOG entry).

Logs the architectural suggestion received during PR BicameralAI#93 review as a
v1.0.0-candidate RFC. The decision is blocked on whether multi-machine /
team sync enters the roadmap; if yes, the RFC is on the critical path,
otherwise META_LEDGER + the existing CHANGEFEED on compliance_check
already provide ~80% of the cited benefits.

Issue BicameralAI#97 carries the full analysis, the proposed v0.14.0 wedge (extend
CHANGEFEED to all mutation-bearing tables), and the open questions for
the maintainer. This BACKLOG entry is the single-line index reference.

Refs BicameralAI#97
@Knapp-Kevin Knapp-Kevin added the documentation Improvements or additions to documentation label Apr 29, 2026
@Knapp-Kevin Knapp-Kevin requested a review from jinhongkuan April 29, 2026 15:13
@coderabbitai

coderabbitai Bot commented Apr 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2d840029-6b82-49c6-aee5-6f322878a515

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@Knapp-Kevin Knapp-Kevin merged commit 695fe39 into BicameralAI:dev Apr 29, 2026
2 checks passed
jinhongkuan pushed a commit that referenced this pull request Apr 30, 2026
Logs the architectural suggestion received during PR #93 review as a v1.0.0-candidate RFC. Decision blocked on multi-machine/team-sync roadmap call; if not on the roadmap, META_LEDGER + the existing CHANGEFEED on compliance_check already provide ~80% of the cited benefits.

Issue #97 carries the full analysis, the proposed v0.14.0 wedge (extend CHANGEFEED to all mutation-bearing tables), and the open questions for the maintainer. This entry is the single-line BACKLOG index reference.

Refs #97
jinhongkuan pushed a commit that referenced this pull request Apr 30, 2026
Triage release per DEV_CYCLE §10.5. Restores Guided-mode post-commit hook
behavior (#124) and ships event vocabulary extension for cross-author
replay (#97), alongside earlier carry-forward fixes (#74 Windows ingest,
#95 telemetry counters + first-boot consent, #98 RFC docs).

Full triage provenance and §10.5.3 adaptation notes in PR #128.
CHANGELOG headline reworked: replaces the cherry-picked v0.14.0 dev-side
heading with a v0.13.5 triage heading covering all 5 commits.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant