StoreSpace · Native retained-source builds
Keep your files and their context together.
StoreSpace’s native service retains its source, build artifacts and verification receipts on an admitted host with a dedicated storage boundary.
What you can accomplish
Build the retained KEX C source in an isolated native workspace and verify the resulting artifacts.
What you bring
An admitted native host with gcc and a dedicated persistent state directory. The current interface builds the service’s retained KEX C source; it does not expose an arbitrary-source upload. Define the source revision, who owns the resulting artifacts and the recovery requirement.
Work through the task
- Agree the host and storage boundary before a build. The source service creates an isolated build directory and retains its C input and compiled binary.
- Inspect the build receipt, source and binary digests, and expected directory readback.
- Run verification against the retained artifacts. Keep the receipt and storage backup together, then qualify restart and recovery separately.
What you leave with
A native-build receipt with source/binary digests and isolated directory readback. This proves that build and local readback only, not fleet, DNS, tunnelling or mining.
Where your work stays
The native service needs its own persistent mount and keeps its build artifacts and last-build receipt there. The separate SERVERspace browser file and workstation environment offers Local Vault and Cloud Drive modes; neither provides this native build service. Check the selected destination and readback, and retain original files.
If something fails
A concurrent build returns BUILD_IN_PROGRESS. Missing compiler/artifacts, no retained receipt, a digest mismatch or failed directory readback blocks verification. Inspect the failure and preserve existing artifacts before another build; recovery is not established by a receipt alone.
Available access
The native retained-source/build service is by arrangement; native host not bound for public customers. The separate SERVERspace browser file and workstation environment is available at the historical storage route. In VFS Vault → Files, check Local Vault or Cloud Drive before adding a sample. Export and recovery are not verified; keep your original copy.
Scope your native StoreSpace service
Carry the source revision, host, artifact ownership and recovery questions into an editable brief. Review it before sending; preparing the draft does not provision storage or grant access.
Alternative: SERVERspace browser file and workstation environment
The existing browser application at the historical storage route identifies itself as SERVERspace, Cloud Server v6.8. It provides a broader file and workstation environment, including VFS Vault and HTML applications. It is separate from the native StoreSpace build service described above.
- Open VFS Vault, then Files. Check whether Local Vault or Cloud Drive is selected before adding anything.
- Keep the original file and use a non-sensitive sample. Check the selected destination and read back the stored item before relying on it.
- Recheck the selected mode, access and retained result after reopening. Local Vault and Cloud Drive have different boundaries; neither the page nor a successful preview establishes backup or recovery.
Read-only inspection confirms Upload, New Folder, filtering and file actions such as preview, run, share and delete. Export behavior has not been verified. Keep your original copy; do not assume that every file is browser-local or that every file is cloud-backed.