Release notes
0.1
Version 0.1 puts a data application on a machine the way you put one on a server, and the machine is a VM on your laptop. You build the application into a signed composition, boot it in a local VM, order an acquisition from a marketplace, and check a delivered image's evidence against a key you hold.
What 0.1 does
- Build.
space initwrites a project, andspace buildcompiles its services inside a disposable builder VM from their Dockerfiles, with no Docker daemon. The build signs the composition under an identity made of an Ed25519 key and an ML-DSA-65 key. A second build recompiles what the edit changed and takes the rest from the content store by digest. - Run.
space runboots the composition in a local VM on macOS on Apple silicon. At a terminal, saving a file restarts the service that reads it. - Deploy.
space deployships the same signed image to a connected target as a durable deploy record, andspace deploy rollbackputs back what the target ran before. Supported targets lists the profiles and their status. - Order. An order buys one acquisition over the area and window in
space.yamlfrom a marketplace target, after printing a plan with a fixed quote. The order is durable and names the machine the scheduler chose. - Verify.
space image verify IMAGE --anchor KEYwalks the evidence chain thatspace runandspace target applycheck before they act on an image: the SBOM and provenance annotations, the blobs they name, the in-toto statements, the signed statement over each, and the partitions the image publishes. It reads no network, and a chain that does not hold names the failing link and exits non-zero.
What 0.1 simulates
The marketplace side of 0.1 runs against simulated supply, and every simulated value says so where it is printed.
| 0.1 shows | What stands behind it |
|---|---|
A pass window graded simulated | A sunlit overlap of the satellite's swath with your area, propagated from its published orbital elements. No operator has offered the window. |
| Supply from Landsat 8 and the two Sentinel-2 satellites | Satellites seeded as simulated supply under one demo account. No operator has put them on offer. |
| An acquisition priced 0.00 EUR | No price is charged for the capacity the order books. |
| A result route that refuses | Nothing produces a result for an order, so asking for one is refused. |
Publishing to the marketplace dates the steps that replace each of these.
What 0.1 leaves out
- Flight. The integrated platform has not flown.
- A witness for keys.
space image verifypasses when the evidence verifies under the key you supplied. A transparency service is an append-only public log, as in IETF SCITT or Certificate Transparency, in which signed statements are registered so that anyone can see which key vouched for which artifact. No transparency service records that key, so a pass does not say anybody vouched for it. - Hosted ordering end to end. No order has run through to a result on run.space.
