bicameral-sync

Sync a decision ledger after a git commit by running bicameral.link_commit to compute hash-level drift, then evaluating pending compliance checks against changed code regions to batch reflected or drifted verdicts into a final summary.

Decision ledger drift detection in post-commit workflows is the process of comparing changed code regions against stored decisions to determine if a commit reflects or drifts from the original compliance requirements, producing a verdict with content_hash guards.

Run a compliance check sync after new commits, merges, or rebases to evaluate pending checks against changed regions. Do not run it for update, upgrade, or new version requests, as those binary upgrade scenarios require a different process.

Evaluate pending compliance checks after merging or rebasing by reading the changed code regions, comparing the decision descriptions against the code, and batching all verdicts into a single resolve_compliance call to report a final summary.

Yes, bicameral-sync supports ledger compliance checks for rebases and merges. It applies to post-commit workflows by computing hash-level drift and resolving pending checks, while explicitly excluding binary upgrade scenarios.