Repository navigation
docs: establish product delivery standards, portfolio review and homepage plan - #1
Merged
Merged
Conversation
This was referenced Oct 22, 2026
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.
The portfolio has inconsistent product promises and no single product delivery baseline: Payback still advertises desktop Pro, RegexMate's internal-use grant conflicts with portfolio wording, and several product roadmaps describe previous implementations.
This adds a delivery standard, a dated repository-by-repository review and a concrete homepage brief while preserving Keel's existing five-library architecture as the canonical dependency graph. It corrects portfolio wording for product integration, RelayPilot visibility, Payback and RegexMate, and links the maintainer entry points. Follow-up implementation issues will be indexed in the review.
Validation: all relative proposal links checked against fixed repository trees; evidence paths checked against the snapshot. Source/documentation/release/PR review only; native apps, hardware and live payments were not exercised. No application or website implementation changes are included. Existing agent worktrees and active PR ownership were preserved.