Skip to content

feat(governance): add GovernanceStore filesystem boundary - #25

Merged
Kucell merged 4 commits into
mainfrom
feat/rdg-ms002-governance-store
Oct 6, 2026
Merged

Kucell merged 4 commits into
mainfrom
feat/rdg-ms002-governance-store

Conversation

@Kucell

@Kucell Kucell commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Purpose

Implement Remote & Detached Governance MS-002 — GovernanceStore Interface approved by D-RDG-MS002-20261006.

This PR introduces the first provider-independent governance I/O boundary while preserving current local behavior.

Scope

  • add lib/governance/store.js;
  • implement FilesystemGovernanceStore;
  • expose explicit store capabilities;
  • enforce relative governance keys and traversal rejection;
  • provide atomic local writes;
  • provide SHA-256 revision tokens;
  • provide compare-and-write using the MS-001 RevisionConflict contract;
  • migrate lib/branch/registry.js local I/O through the store abstraction as a canary;
  • add focused GovernanceStore tests;
  • add existing branch-registry regression to M-040 validation.

Canary semantics

The branch registry migration is an I/O canary only. It does not change the branch registry lifecycle, make it remote/shared, or reclassify it as durable governance.

Not in this PR

  • GitGovernanceStore;
  • GitHub/GitLab/Gitee adapters;
  • network I/O;
  • remote mutation;
  • init/attach/rebind CLI;
  • migration cutover;
  • Management API remote resolution;
  • Dashboard/MCP remote behavior;
  • branch-registry semantic changes.

Governance

@Kucell
Kucell marked this pull request as ready for review October 6, 2026 05:51
@Kucell
Kucell merged commit 101473f into main Oct 6, 2026
2 checks passed
@Kucell
Kucell deleted the feat/rdg-ms002-governance-store branch October 22, 2026 06:53
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