NEC-52: Walk the stale gates in launch-readiness.md #147
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!147
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-52-walk-the-stale-gates-in-launch-readinessm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-52 — https://projectron.nerchure.com/tasks/52
Walks Gates A, B and C of docs/launch-readiness.md from observation: every ticked row now cites a dated host observation (docs/manual-testing.md) or a named test. Closes the last unchecked suspended writes (display name, device rename) and judges attachment writes against the folder owner's account too, with WIRE-072..074 stating what suspension refuses and what it never does (reads, sign-in, recovery, credentials, device removal; text sync is never blocked by a quota or non-payment). Corrects the load-bearing 'nothing derived from the passphrase' overclaim in security-model.md, identity.md and CRYPTO-025. The walk found two backup defects, filed as NEC-95 (pre-deploy copies pruned by sha) and NEC-96 (identity host shipped no database or signing keys since 15 Sep; mitigated by a hand snapshot held until ~8 Oct), and rehearsed a shard restore up to the real-client step (NEC-97).
Spec:
docs/changes/NEC-52-walk-launch-gates/spec.mdChangelog
A suspended organisation can no longer change display names or rename devices, and attachment uploads into a suspended owner's folder are refused; reading, downloading, signing in and removing a device still work.
3bece43b263327570e0a3327570e0a0c1827c95d0c1827c95dafd2076e32