StoreSpace
Build, retain and verify source-backed objects in a dedicated virtual filesystem.
Separate service package • native host not bound
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.
Technical background, package access and updates
Purpose
StoreSpace is the retained-source and build service. It provides distinct build and verification interfaces for stored C source, resulting binaries and directory readback.
Working path
Retained source → native compiler → execution/build receipt → source and binary digest verification → retained-object readback. StoreSpace needs its own persistent state mount.
Deployment boundary
StoreSpace and ServerSpace have independent process identities, storage and host admission. One service cannot stand in for proof that the other is active.
A build receipt establishes that build and local readback only. It does not establish DNS delivery, fleet control, network tunnelling, mining or recovery.