docs: add shared operational memory under .claude/memory#678
Open
ecv wants to merge 1 commit into
Open
Conversation
Version-controlled, repo-portable operational notes for working on this repo with Claude Code: gh tooling habits, git hygiene, unattended-loop permission discipline, and the activity-policy ownership model. These are the public, non-sensitive subset of operating knowledge — no credentials, cluster names, project IDs, or internal incident detail. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Considering this in a public repo. RFC. |
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.
Summary
Adds a version-controlled
.claude/memory/directory holding the public,repo-portable subset of operational knowledge for working on this repo with
Claude Code (or any agent). One file per fact, indexed by
MEMORY.md.Opened as a draft for review of both the selection and whether this belongs
in-tree.
What's included
gh-issue-body-file.md--body-filenot a--bodyheredoc so code fences rendergithub-sub-issues-via-graphql.mdghcommand; use theaddSubIssueGraphQL mutationpull-main-on-switch.mdgit fetch+pull --ff-onlyon switching to mainunattended-loop-permission-discipline.md/loopwith zero permission promptsactivity-policies-owned-by-source-repos.mdActivityPolicyCRs underconfig/services/activity/policies/, shipped via an OCI bundle — plus the recurring unguarded-responseObjectDLQ-leak patternWhat's deliberately excluded
Operational notes that are environment-specific or sensitive were left out:
prod alert-triage and incident catalogues, access-control internals, Flux/gateway
production incidents, e2e project IDs and gitignored values files, and
deploy-repo Flux paths. Nothing here contains credentials, cluster names,
project IDs, or internal-only incident detail.
Notes
the items that are both useful here and safe to publish.
activity-policies-*entry overlaps the area touched by feat(iam): re-home audit-log-querier inheritance to activity service #677.🤖 Generated with Claude Code