docs: add greenfield adaptation protocol#46
Merged
Conversation
dapi
marked this pull request as ready for review
July 21, 2026 12:11
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.
What changed
memory-bank/, extract confirmed product and project facts from repository instructions, README files and docs, and place them in the correct canonical owners;Why
The repository explained the template and its individual sections but did not provide one direct task that an agent could execute to perform the initial adaptation. The new protocol stays focused on that job: copy, inspect, adapt, create the PRD, update navigation, and lint.
User impact
A user can open a greenfield repository and run the documented Codex command. Codex then adapts Memory Bank from the facts already present in README and docs without inventing missing requirements or starting product implementation.
Routing record
Workflow: Small Change
Design: not required
Reason: the change extends the existing adoption documentation pattern and introduces no runtime, API, configuration, schema, or release contract.
Plan: not required
Reason: the change is an atomic documentation update across one protocol-prompt and its navigation owners.
Validation profile: documentation
Triggers / rationale: Markdown-only public guidance; executable behavior and release path are unchanged.
Downgrade approval: none
Validation
go run ./cmd/memory-bank lintgo test -count=1 -race ./...go vet ./...git diff --check