refactor: group internal packages by domain - #95
Merged
Conversation
Inspect each package directory independently and compare full internal import paths so nested Memory and Agency packages cannot collapse into one component. Validated with umask 022; make test.
Move Memory storage, search, graph, embedding, import, and Host setup packages under internal/memory while preserving their package APIs and runtime paths. Update deterministic package lists, architecture guards, and path-sensitive tests without changing Memory behavior. Validated with go build -o mnemon . and umask 022; make test.
Move Agency authority, artifact, peer transport, client, and Pi attachment packages under internal/agency while keeping the protocol root and daemon composition boundary stable. Update imports, package guards, ownership docs, and path-sensitive runtime tests without changing wire, persistence, or workspace paths. Validated with go build -o mnemon ., focused Agency and architecture tests, and umask 022; make test.
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.
What
Why
Prepare explicit Memory and Agency implementation boundaries before introducing the H0 View infra. This PR is structural only: the CLI surface, wire protocol, database schema, runtime state paths, and host projection paths remain unchanged.
Validation
Checklist