Specs¶
The specs of Nereus: the plan or the design of one slice, written before its code. The command specs, one file per reef, are the CLI reference.
| Spec | Status | What it settles |
|---|---|---|
| 0001. First slice | Done | init, a Nereid list and a fake Nereid that publishes commands |
| 0002. Reef at runtime | Done | A reef added from the CLI and a Nereid installed into it from its image label |
| 0003. Nereid conformance | Proposed | What a Nereid image declares and how the platform checks it |
| 0004. Init time SLO | Proposed | A fitness function caps how long nereus init takes |
| 0005. Cloud reef | Accepted | How the platform presents itself to a cloud, with no credential kept |
| 0006. Installation identity | Proposed | A name, an id and an alias for each installation |
| 0007. Invitation | Proposed | A link and a QR code that let one person in, for a while |
| 0008. Portal first slice | Proposed | A PWA that says who you are |
| 0009. Build security | Accepted | What a hostile Dockerfile can reach in the build reef |
| 0010. Build trigger | Proposed | A new commit on a Mirror builds a Workload |
| 0011. Authorization first slice | Proposed | The first slice of teams and authorization |
| 0012. Presentations first slice | Not stated | Drive and follow: a phone drives a Session, others follow |