RMT Next Steps

You now know the core RMT-vNext flow: templates define boundaries, surfaces define renderable units, state and selectors define data, actions handle intent, resources describe lifecycle ownership and lanes express scheduling priority.

Where To Go Next

Use RMT vNext Authoring as the guided entry point and RMT Reference for the complete operator syntax. Read the App DSL when you want to model full applications, then continue with XTend Maraca, the Runtime Bridge, RMT Linter and Language Server.

For UI integration, read SurfaceManager Authoring and XTend Fabric RMT Lane Mapping.

Practice

Open the RMT Playground, add a second surface and give it a lower lane weight. Then compare the compiled output with the reference docs.

Production Path

When your practice document contains state, actions, validation or surface transitions, continue it as a Maraca app. Start with XTend Maraca, then check Maraca Orchestration and compare your document with products/rmt-maraca-kernel-orchestration/kernel-orchestration-app.rmt. The decisive local check is the strict build, because it proves public app orchestration rather than only the parser path.

Local completion check

Verify the learning path, playground, and reference together. The JSON report identifies the failing suite and remains machine-readable in CI:

node scripts/run_xtend_tests.js rmt-playground-docs rmt-reference-docs --json

If the run fails, correct the RMT source against tools/rmt-language/vnext-parser.js first, then rerun the command unchanged.