Uh oh!
There was an error while loading. Please reload this page.
docs(rfc-0001): Rev 9 — offboarding via tracebloc delete + single-machine CLI scope - #157
Merged
Merged
Conversation
…+ single-machine CLI scope Decided by Lukas 2026-07-07. Two coupled decisions: - The CLI is scoped to THIS machine (one client per machine — the §7.2 anchor); the account's fleet lives in the web-UI. So `client use` is removed and `client list` is internal-only (hidden; still callable for the installer pre-flight). Amends the §6.2 surface; folds in the cli#136 client-surface prototype. - Offboarding is a top-level `tracebloc delete` (not `client delete --uninstall`): a SOFT offboard that revokes the machine credential, tears down the local install, wipes local data, and RETAINS all backend artifacts (client record, dataset catalog, use cases, trained models) as history. A hard row-destroy is REJECTED — it would cascade the client's training telemetry (weight refs, confusion matrices, carbon). New §7.10 (design of record) + Rev 9 callouts on §6.2/§7.4; R12 flipped to addressed; C.6 corrected to name the built machine-revoke endpoint (POST /edge-device/<id>/revoke, backend#886) and note DELETE is unrouted. Supersedes the cli#136 proto's client delete/DELETE offboarding draft. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
LukasWodka
commented
Jul 7, 2026
ContributorAuthor
Implemented: cli#160 (Phase 1 — |
saadqbal
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The design-of-record for the offboarding work (Phase 1 cli + Phase 2 backend, in flight). Decided by Lukas 2026-07-07.
§7.10 (new) —
tracebloc deleteis a top-level SOFT offboard: revoke the machine credential (POST /edge-device/<id>/revoke, backend#886 — not the 405DELETE), tear down the local install, wipe local data; retain all backend artifacts (client record, datasets, use cases, models) as history. Hard row-destroyrejected (it would cascade the client's training telemetry). Tombstone gaps to build: decommissioned client state, dataset-unavailable-on-offboard, launch-time availability gate.Rev 9 callouts — §6.2/§7.4:
client useremoved,client listinternal-only, delete → top-level; the CLI is single-machine, the fleet is the web-UI. R12 flipped to addressed. C.6 corrected to name the built revoke endpoint + noteDELETEis unrouted.Supersedes cli#136's
client delete/DELETEoffboarding draft. Verified: cross-refs resolve, fences balanced.🤖 Generated with Claude Code