docs: align Plures identity with evidenced product stages - #45
Draft
kayodebristol wants to merge 2 commits into
Draft
docs: align Plures identity with evidenced product stages#45kayodebristol wants to merge 2 commits into
kayodebristol wants to merge 2 commits into
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
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.
Replace outdated marketplace, creator-revenue and organization-wide MIT claims with the Plures “More, together” identity, an additive draft mark and product-specific documentation, release history and support paths.
Present PluresLM as local memory, decision ledger tracking and procedural execution control for LLMs and agents. Its product overview is independent of a host integration; release metadata explicitly identifies the MCP service. The profile and product guide are generated from the central authoring pipeline. The public roadmap describes maintainable software and demonstrated outcomes.
Validation: generated profile/guide match their authoring output; product and release sources verified without authentication during generation; public docs/assets pass the private disclosure check; staged whitespace checks pass. The new guide and mark are introduced in this PR and become reachable on main after merge. No deployment or commercial-service changes.
Roadmap-Item: none
Roadmap-Exemption: Public documentation distribution and correction of stale organization identity; no runtime or product implementation change.