BRAINK Workstation Studio
Keep workstation files, receipts and runtime references together.
Owner-controlled browser application • access by arrangement
What you can accomplish
Keep an engineering note, its source references and the relevant receipts together.
What you bring
A safe local filename and the text of the work item. Include the source version, what you observed and the receipt identifier so another review can follow the result.
Work through the task
- Write a note describing one work item and its expected result.
- In the approved Studio, save the text, load it again and inspect the native receipts. Compare the loaded text with the original.
- Export the notebook as a plain-text file and keep it with the referenced evidence. Decide separately whether any preserved BRAINK runtime should execute.
What you leave with
A retained text note and an exported notebook. Reading receipts does not start BRAINK AI, a remote worker or a physical host.
Where your work stays
Notes are saved in the Studio’s browser-local VFS with immediate readback. The exported text is a separate copy; runtime references in a note do not carry the referenced runtime or its data.
If something fails
Invalid filenames, missing notes, a detached AetherOS host or a readback mismatch stop the operation. Recover from your exported note and recheck the receipt instead of assuming another browser has the same state.
Available access
The workstation Studio is owner-controlled. The customer workspace has separate public tools for your own records; it does not grant access to these receipts or preserved owner runtimes.
Technical background, package access and updates
Purpose
Organize engineering work around retained files and operation receipts, with the preserved BRAINK runtime kept as a distinct source component. This supports workstation preparation and inspection without silently starting that runtime.
Working path
Work item → scoped workstation files → receipt → later inspection.
Source identity
AetherOS, BRAINK native-host adapter and converged workbook lineage. This Studio is a new derivative, not a renamed historical application. The original components retain their identities.
Availability and authority
The notebook surface does not establish original BRAINK execution, remote worker execution, model inference or physical host actuation.
The four Studios have been installed, launched and reloaded in the owner-controlled AetherOS browser host. That qualification does not establish public access or cross-device state. Customer sign-in does not grant installation or administration rights.