aesthetic.computer
Monorepo for Aesthetic.Computer
aesthetic.computer
1# FedAC Score
2
3FedAC shipping is complete only when users can receive and apply the new build.
4
5## Scope
6
7- `fedac/` is the OS stack (kiosk + native boot flows).
8- `fedac/native/` is the bare-metal kernel+initramfs path.
9
10## Ship Contract
11
121. Build the release artifact.
132. Publish the artifact to the release CDN.
143. Verify CDN metadata (`.version`, `.sha256`, `releases.json`) and binary hash.
154. Trigger the update signal path for running OS instances.
165. Validate install/flash path on real media.
17
18If one step is missing, it is not shipped.
19
20## Native Release Endpoints
21
22- `https://releases.aesthetic.computer/os/native-notepat-latest.vmlinuz`
23- `https://releases.aesthetic.computer/os/native-notepat-latest.version`
24- `https://releases.aesthetic.computer/os/native-notepat-latest.sha256`
25- `https://releases.aesthetic.computer/os/releases.json`
26
27## Running-Instance Alert Rule
28
29- The authoritative update signal is the CDN version bump (`native-notepat-latest.version`).
30- Running native OS instances poll this version URL and emit in-OS update notification (`update!` + beep/TTS) when a newer version is detected.
31- Operator message broadcast (chat/system) is recommended for immediate human visibility, but does not replace the CDN version signal.