[codex] Finalize mindspace spec#7
Draft
dudash wants to merge 11 commits into
Draft
Conversation
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
docs/mindspace/section for the optional Mindspace workspace layer.mdm mindspace ...namespace.docs/mindspace/REFERENCE.mdand the navigation/value docs.Why
Mindspace should be optional and self-contained:
mdmandmdmindcan support it, but workspace-specific concepts should not bleed into core single-map behavior. This PR makes that boundary explicit while preserving the planned value: local-first workspace understanding, deterministic scan/lint/context contracts, and reviewable agent-safe maintenance.Validation
git diff --checkdocs/reference/MINDSPACE.mdlinks and stalemdm agent session/reviewexamples.