The product is under construction
Public claims should match working product support. The portal should not present roadmap goals as live production capability.
SCYNEXUS is under development.
These notes keep public expectations aligned with the current product posture before chain creation, authenticated workflows, and release readiness.
No token or reserve content yet
Settlement can be explained as a workflow concept, but token, reserve, redemption, or investment framing is not part of this public portal version.
Chains require accountability
Chains are provided to accountable owners. Create your Nexus routes through authenticated onboarding instead of public anonymous creation.
Records are hashed and cryptographic
The current public posture is technical proof without default public identity links. Future identity links require user consent and approved visibility rules.
Validation has limits
Validation reviews evidence against defined scope and criteria. It does not replace legal, safety, regulatory, or professional review.
Disputes and governance matter
Contested claims need defined evidence, adjudication, and appeal paths rather than informal trust.
Architecture, research, and implementation are at different stages.
This public summary distinguishes what exists today from the authenticated workflow being built and from longer-term architecture.
Available now
The localized Public Portal, Auth Service prototype, User Portal shell, protocol foundations, and public architecture material exist in the repository.
Current implementation focus
An authenticated request-intake path is selected, but the complete end-to-end workflow for Artifacts, Contracts, delivery, and economics is not implemented.
Architecture and future work
Accepted decisions define important boundaries; proposed decisions, exploration, and future possibilities remain separate from production capability.
Next step