Add memory-boundaries rule, drift checks, and a solo-PM field report#3
Open
vibecodingproductled wants to merge 1 commit into
Open
Add memory-boundaries rule, drift checks, and a solo-PM field report#3vibecodingproductled wants to merge 1 commit into
vibecodingproductled wants to merge 1 commit into
Conversation
Contributes learnings from four months running Shannon: - New rule .claude/rules/memory-boundaries.md: the single-source-of-truth principle (one home per fact, pointers not copies) with a layer-ownership table and a tie-break rule. Prevents the always-loaded files from drifting out of sync with agent-maintained Brains. - system-health-check: add a memory-boundary drift check (template artifacts, duplicated facts across files, stale personal config, rule echo). - quality-gates Gate 0: add a "duplicated fact" red flag. - Shanon-Docs/field-notes-solo-pm.md: an honest field report (what worked, the struggles, how these improvements came about). All additive and generic. No proprietary or organization-specific content. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Hi, and thank you for building Shannon in the open. I have been running it daily as a solo PM since March, and this PR contributes back the biggest lesson I learned plus a short field report. Everything here is additive and generic PM methodology, with no proprietary or organization-specific content.
What is in this PR
1. New rule:
.claude/rules/memory-boundaries.md(the main contribution)The single-source-of-truth principle: each fact has exactly one home, and everywhere else stores a pointer, not a copy. Includes a layer-ownership table and a tie-break rule. This addresses the failure mode where the always-loaded files (
CLAUDE.md,CLAUDE.local.md) drift out of sync with the Brains an agent keeps current, so the model ends up reading two conflicting "truths." Shannon currently has no source-of-truth / memory-boundaries rule, so this is net-new.2.
system-health-check: memory-boundary drift checkA new check section that greps for the signs of drift (unfilled
[bracket]placeholders, a fact duplicated across files, aCLAUDE.local.mdolder than the newest Brain, rule echo). Reports as warnings only; preserves all existing checks.3.
quality-gates.mdGate 0: a "duplicated fact" red flagOne line pointing to the new rule.
4.
Shanon-Docs/field-notes-solo-pm.md: an honest field reportFour months of use: what worked (Brains, auto-activating skills, personas, hooks), where it hurt (skill bloat, context drift, monolith CLAUDE.md), and how these improvements came about.
Notes
Thanks again for the project and the welcoming CONTRIBUTING guide.