NEC-50: positioning.md and competition-relay.md credit Relay with RBAC they do not ship #141

Merged
nectenda-agent merged 2 commits from worktree-nec-50-positioningmd-and-competition-relaymd-cre into main 2026-09-24 12:39:03 +01:00
Collaborator

Task: NEC-50 — https://projectron.nerchure.com/tasks/50

Correct positioning.md, competition-relay.md, go-to-market.md and sync-limitations.md, which credited Relay with role-based access control. Relay's 'RBAC' is private folders (their pricing label), which we have via folder_members; their docs say read-only is unsupported. Review then found their Reader role merged on main (c0264c64) but in no release, so the docs now say neither has released read-only as of 24 Sep 2026, that Relay's is coming, and what to say once it lands — never that we are ahead. Also corrects the claim that NEC-16 enrolled signing keys: the identity key is the signing key and no update is signed yet. docs/v1 ADR 0007 and invariants.md still carry the old competitor sentence; left for a follow-up since this spec has no docs/v1 deltas.

Spec: docs/changes/NEC-50-relay-rbac-correction/spec.md

Changelog

NONE

Task: NEC-50 — https://projectron.nerchure.com/tasks/50 Correct positioning.md, competition-relay.md, go-to-market.md and sync-limitations.md, which credited Relay with role-based access control. Relay's 'RBAC' is private folders (their pricing label), which we have via folder_members; their docs say read-only is unsupported. Review then found their Reader role merged on main (c0264c64) but in no release, so the docs now say neither has released read-only as of 24 Sep 2026, that Relay's is coming, and what to say once it lands — never that we are ahead. Also corrects the claim that NEC-16 enrolled signing keys: the identity key is the signing key and no update is signed yet. docs/v1 ADR 0007 and invariants.md still carry the old competitor sentence; left for a follow-up since this spec has no docs/v1 deltas. Spec: `docs/changes/NEC-50-relay-rbac-correction/spec.md` ## Changelog NONE
Their pricing page's "Role-based access control (private folders)" is
private folders, which folder_members already gives us, and their own
docs say read-only access is unsupported. Both positioning.md and
competition-relay.md conceded a gap that does not exist; reframe the
read-only weakness as a feature neither product ships, with sources and
read dates, and without claiming a lead we do not have.

Task: NEC-50

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D2R3ydtiJaKqPToLj4RaCS
Say Relay's Reader role is merged and coming, and that NEC-16 shipped nothing
All checks were successful
Release note / release-note (pull_request) Successful in 13s
CI / build (pull_request) Successful in 4m19s
CI / e2e (pull_request) Successful in 6m33s
CI / promote (pull_request) Has been skipped
CI / build (push) Successful in 4m36s
CI / e2e (push) Successful in 5m5s
CI / promote (push) Successful in 31s
da32a6aaec
Review found c0264c64, "feat: add the Reader role", on Relay's main but in
no release, so "neither ships read-only" holds for releases only and will
lapse; both docs now say so and give the line to use when it does. NEC-16
was closed because the identity key is the signing key, not because
enrolment shipped. go-to-market.md repeated the RBAC claim twice.

Task: NEC-50

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D2R3ydtiJaKqPToLj4RaCS
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Nectenda/nectenda!141
No description provided.