| ... | @@ -1,6 +1,24 @@ | ... | @@ -1,6 +1,24 @@ |
| 1 | # Knife sign-in and archive storage | 1 | # Knife sign-in and archive storage |
| 2 | | 2 | |
| 3 | Open https://knife.paperclover.net and sign in through Snow Globe. The server | 3 | The production service was taken offline on 2026-10-19. Its declaration has |
| | 4 | `enabled = false`, so later deployments do not restart it. The complete |
| | 5 | `globe/prod/knife` dataset remains mounted at `/srv/prod/knife`, including runtime |
| | 6 | state, archive objects, environment identity, and workspaces. The stopped dataset |
| | 7 | has snapshot `knife-retired-20261019T213553Z`, held with |
| | 8 | `knife-archive-retention`. Private verification evidence is in |
| | 9 | `/var/lib/snowglobe/retirements/knife/`. |
| | 10 | |
| | 11 | Keep `data` and `archives` together; archive objects alone are not a complete |
| | 12 | restoration. Preserve the service UID and `archives/.knife-archive-store-id`. |
| | 13 | Retirement does not delete or migrate any conversations. The separate disposable |
| | 14 | preview remains independent of this production dataset. |
| | 15 | Later deployment backups omit retired jobs; retain the held snapshot and private |
| | 16 | retirement evidence separately from routine release-backup retention. |
| | 17 | |
| | 18 | ## Restoring service access |
| | 19 | |
| | 20 | Re-enabling the service requires a deliberate production deployment. After that, |
| | 21 | open https://knife.paperclover.net and sign in through Snow Globe. The server |
| 4 | accepts only the configured issuer and Clover's immutable owner subject. The NAS | 22 | accepts only the configured issuer and Clover's immutable owner subject. The NAS |
| 5 | environment is **snow globe**. Provider accounts can stay on each laptop; the NAS | 23 | environment is **snow globe**. Provider accounts can stay on each laptop; the NAS |
| 6 | needs none for archive storage or outbound environment routing. | 24 | needs none for archive storage or outbound environment routing. |