Now
Ship a first-class bilingual presentation layer
Make Proteus legible to maintainers and external evaluators without rewriting canonical docs.
Roadmap
The next work is productization work.
The hardest abstraction work is already visible in the current framework. The next sequence is about adoption quality: stronger release checks, better distribution, and a clearer outward-facing story.
Priority now
Changes that raise trust immediately
These items move Proteus from maintainer-legible to adopter-legible without broadening the framework scope.
Now
Expose readiness evidence from primary entry docs
Readers should discover the current verdict from README and onboarding paths.
Now
Strengthen release verification
Move beyond local smoke checks toward standardized CI signals for the framework and the site.
Next after that
Changes required before public-ready claims
These are the moves that make the framework easier to distribute, easier to trust, and easier to adopt across more than one topology.
Later
Define a product-grade distribution path
Public-ready positioning needs a cleaner installation story than clone plus PATH.
Later
Expand adoption recipes
Add more example topologies and clearer migration-to-instantiation guidance.