Add an optional data-governance layer (authoritative source, sensitivity, provenance)#3
Open
dubedad wants to merge 1 commit into
Open
Add an optional data-governance layer (authoritative source, sensitivity, provenance)#3dubedad wants to merge 1 commit into
dubedad wants to merge 1 commit into
Conversation
dubedad
force-pushed
the
data-governance-layer
branch
from
July 19, 2026 16:11
ed618c8 to
1af30ef
Compare
…, provenance) Optional references/data-governance.md for workspaces holding shared, regulated, or sensitive data. Formalizes three practices ICM already reaches for informally — one-home-per-fact as a declared authoritative source, generalized sensitivity classification for the one-agent-walks-all model, and provenance on factory outputs — as opt-in frontmatter conventions, mandatory nowhere. Drawn from DAMA-DMBOK. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
dubedad
force-pushed
the
data-governance-layer
branch
from
July 19, 2026 16:16
1af30ef to
bbb659e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an optional data-governance layer
What this adds
One optional reference doc —
references/data-governance.md— plus a single pointer line in SKILL.md's References list. Nothing becomes mandatory. No form requires it; workspaces that don't hold sensitive data ignore it at zero cost.It formalizes three things ICM already reaches for informally, for the case where a workspace holds shared, regulated, or sensitive data (a team brain, client/personal records, anything with a compliance obligation):
source_of_truth:frontmatter + an optional_glossary/), so a reader can tell the master from a mirror and the walk-test dedup check has an answer to "which is real?"access_tieridea to any form. Since ICM's defining move is one agent walks the whole workspace, what the agent may read/quote/send is a first-class concern. Adds a walk-test question: walking cold, could I read or exfiltrate something above its tier?source:/generated_from:frontmatter on factory outputs, turning invariant 9 ("filesystem is the state machine") into an auditable one: status becomes not just "what exists" but "what produced it."Why it fits rather than bloats
access_tier, "one home per fact,"_meta/schema.md— rather than importing an external framework wholesale.Drawn from DAMA-DMBOK (metadata/glossary, data security & privacy classification, master/reference-data authoritative source), reduced to the smallest form that serves a one-agent folder workspace.
Best reviewed after the reference-integrity gate PR, which this references.