This repository was archived by the owner on Sep 5, 2026. It is now read-only.
chore: explicitly un-ignore PROVENANCE.md (global rule guards a confidential file elsewhere) - #14
Merged
Merged
Conversation
The new doctor/trust commands and the TOFU trust anchor were only in THREAT-MODEL; add them to the README Quick Start and the PROVENANCE implemented-features list so a user reading the primary docs sees them. (CHANGELOG is git-cliff generated from the conventional commits and picks these up on the next release.)
A global ~/.config/git/ignore rule for PROVENANCE.md kept this file out of the repo, so the two README links to ./PROVENANCE.md were dead on GitHub. Force-add it (content is the public provenance spec) so the links resolve; includes the trust-anchor section.
A global core.excludesFile ignores PROVENANCE.md everywhere because it protects a CONFIDENTIAL file of that name in another repo (scrivener-mcp). That guard must stay, so override it locally: cogmem's PROVENANCE.md is the public spec the README links to. A repo .gitignore negation outranks the global excludes (verified), so 'git add' works without -f and the intent is documented in-tree.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Follow-up to #13. A global
core.excludesFileignoresPROVENANCE.mdeverywhere — it protects a CONFIDENTIAL same-named file in another repo, so it must NOT be removed. Override it locally with a!PROVENANCE.mdnegation (repo .gitignore outranks the global excludes, verified in an isolated test) so cogmem's public spec stays trackable without-fand the reasoning is documented in-tree.