docs: non-goals note and ecosystem-feedback summary - #127
Merged
Conversation
The non-goals note collects what the reference intentionally excludes and why. The ecosystem-feedback page records the external integration, the findings from it, and the resulting changes.
The public testnet onboards testers as hosted parties on the operator's validator, with assets issued locally by its own Token Standard V2 registry, until the general-purpose wallet tooling supports V2.
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.
Two documentation pages that close the remaining paper deliverables.
docs/concepts/non-goals.md— a consolidated account of what the reference intentionally does not include and why: not a generic settlement engine, single registry admin per pair, not a production matching engine, a minimal instrument model, the reference registry as one option rather than the mechanism, the hosted testnet as a demo surface rather than self-custody, and operational hardening left to the operator. The scope statements were previously scattered through the architecture note; this gathers them andarchitecture.mdnow points to it.docs/reference/ecosystem-feedback.md— the single summary of how the reference was evaluated externally and what changed. It records the external integration (canton-trading-toolkit, which lists this DEX as an adapter alongside a mainnet AMM and a perpetuals testnet), links the public evaluation reports, and maps the findings to the resulting changes by theme.Both are linked from the docs hub and pass the internal link check.