Eight standalone specialist studios are connected by three purpose-built control rooms. No installation, account, package manager or internet connection is required.
Open RELEASE_SELF_CHECK.html, choose the complete extracted folder and run the SHA-256 comparison. Investigate any missing or altered file before classroom use.
Open index.html. Use the Studio Shell for a connected learner journey, the Teacher Director for orchestration, the Portfolio Hub for review, or open one specialist app directly for a single-station lesson.
Enter an alias, commission, essential question, BUILD/GROW/LAUNCH pathway and mission code in the Studio Shell. Apply the passport to the current station. The same code reproduces the teaching challenge; it does not make synthetic history authentic.
Move through Understand → Predict → Make → Test → Revise → Explain. Commit the expected direction, estimate, confidence and reason before revealing the specialist diagnostic. Freeze Design A before the main revision.
Use the relevant physical bridge: shadow-photo comparison, cold-craft token matrix, hidden route channel, relief plan, calibrated steelplate pattern, contour/cam pack, collagraph proof comparison or source-grounded economic argument.
The Studio Shell can translate Token → Economy, Hydro-Board → Smuggling Rig and Architectural Relief → Collagraph. The receiving app records the transfer as a model transformation, not proof or an exact material equivalence.
Open Studio record inside an app and export its .makerlab record and printable dossier. Export .makerstudio from the shell for a multi-station journey, then import project files into the Portfolio Hub.
Safety and truth boundary: the suite does not authorise hot-metal casting, reactive patination, powered machinery, structural fabrication, historical attribution, navigation or accreditation. Use setting-approved physical processes, current risk controls and verified sources.
Deployment guide · Privacy and retention · Safety and truth boundary