Repository navigation
docs: introduce Neuron through real user value - #22
Merged
Merged
Conversation
Reframe the README around Synapse replacement, expressive control, and an extensible hardware layer. Add a human-first FAQ and manual compatibility paths while keeping agent skills optional. Align safety, device-evidence, onboarding, and issue-report wording. Documentation-only; no application behavior changed.
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.
Why
Neuron already replaces Synapse on my own desk. The public docs should start there: what a Razer owner can do, what is verified, and how to try it. The deeper protocol details are still available when someone wants them.
The new opening describes reverse-engineering how Synapse talks to Razer hardware, not the whole Synapse application, and makes no REA claims.
What changed
Verification / limits
57525f4: one commit, 14 documentation/YAML files; no runtime code changed.Deliberately left alone
Historical release notes, implementation, hardware command data, licensing terms and application UI. GitHub's short repository description and the separate woflo.dev homepage also remain unchanged.
Suggested repo description for a later metadata update:
Review the wording before merging;
mainhas not been changed.