neuron-technologies/neuron-web
3
0
Fork 0
Code Issues 2 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

Correct Safety section to claim only what the product does #160

Open
will.anderson wants to merge 1 commits from fix/safety-claims-match-shipped-behavior into main
pull from: fix/safety-claims-match-shipped-behavior
merge into: :main
Conversation 1 Commits 1 Files Changed 1
+10 -13
will.anderson commented 2026-07-21 14:50:36 +00:00
Owner
Copy Link
Copy Source

The marketing Safety section (src/safety.el) claimed crisis capabilities the product does not have. Verified against products/neuron/safety.el and the desktop safety flow: shipped behavior is on-device keyword detection that surfaces crisis resources (988, hotlines) to the user, abuse-aware guidance that never points a victim at their own contacts, a locally-stored Hard Bell contact (never uploaded), and on-device-only bell logging. There is no telephony/SMS/email dispatch anywhere - nothing is transmitted and no third party is contacted.

Corrected false claims:

  • content 'routes to emergency services and crisis lines' -> surfaces crisis resources to the user
  • 'emergency services or relevant authorities may be contacted ... cannot opt out' -> no auto-reporting exists; now states on-device, never transmitted
  • 'that contact is reached directly' / 'the contact is made by your local instance' -> contact is stored locally only; no dispatch exists
  • 'I'm also establishing a Neuron crisis line - free, 24/7, staffed' -> no such service; removed

SOURCE ONLY. Site deploy is held per Will's gate - do not deploy. The live site still shows the old copy until Will deploys; that is expected. dist/ and index.html are build artifacts, regenerated at build time, unchanged here.

NOTE for reviewer: src/terms.el (lines ~146, ~157) carries the same 'emergency services or relevant authorities may be contacted ... cannot opt out' language. It is a binding legal document and is being edited on a separate branch (legal/18plus-terms-privacy-reconcile); flagging so the false-capability claim is reconciled there too.

Do not merge - Will's review gate.

The marketing Safety section (src/safety.el) claimed crisis capabilities the product does not have. Verified against products/neuron/safety.el and the desktop safety flow: shipped behavior is on-device keyword detection that surfaces crisis resources (988, hotlines) to the user, abuse-aware guidance that never points a victim at their own contacts, a locally-stored Hard Bell contact (never uploaded), and on-device-only bell logging. There is no telephony/SMS/email dispatch anywhere - nothing is transmitted and no third party is contacted. Corrected false claims: - content 'routes to emergency services and crisis lines' -> surfaces crisis resources to the user - 'emergency services or relevant authorities may be contacted ... cannot opt out' -> no auto-reporting exists; now states on-device, never transmitted - 'that contact is reached directly' / 'the contact is made by your local instance' -> contact is stored locally only; no dispatch exists - 'I'm also establishing a Neuron crisis line - free, 24/7, staffed' -> no such service; removed SOURCE ONLY. Site deploy is held per Will's gate - do not deploy. The live site still shows the old copy until Will deploys; that is expected. dist/ and index.html are build artifacts, regenerated at build time, unchanged here. NOTE for reviewer: src/terms.el (lines ~146, ~157) carries the same 'emergency services or relevant authorities may be contacted ... cannot opt out' language. It is a binding legal document and is being edited on a separate branch (legal/18plus-terms-privacy-reconcile); flagging so the false-capability claim is reconciled there too. Do not merge - Will's review gate.
will.anderson added 1 commit 2026-07-21 14:50:42 +00:00
Correct safety section to claim only what the product does bb419dc98c 
The Safety section described crisis capabilities the product does not have.
Grounded against products/neuron/safety.el and the desktop safety flow, the
shipped behavior is: on-device keyword detection that surfaces crisis
resources (988, hotlines) to the user, augments the assistant's reply with
warmth and resources, uses abuse-aware guidance that never points a victim at
their own contacts, stores a Hard Bell contact locally (never uploaded), and
logs bell events on-device only. Nothing is transmitted; no one is contacted.

Corrected the false claims:
- "content routes to emergency services and crisis lines" -> it surfaces
  crisis resources to the user (card: Emergency routing -> Crisis resources)
- "emergency services or relevant authorities may be contacted ... cannot opt
  out" -> no auto-reporting exists; card now states on-device, never
  transmitted (Mandatory reporting -> On your device)
- "that contact is reached directly" / "the contact is made by your local
  instance" -> the contact is stored locally; there is no dispatch mechanism
- "I'm also establishing a Neuron crisis line - free, 24/7, staffed" -> no
  such service exists; removed
- reframed the "routing" copy that justified the above to the real
  abuse-aware guidance the HHS stat actually supports

Source only. Site build/deploy is held; dist and index.html are regenerated
at build time and are unchanged here.
will.anderson commented 2026-08-03 18:59:48 +00:00
Author
Owner
Copy Link
Copy Source

GROOMING — 2026-08-03
Status: HELD pending attorney/counsel sign-off — corrects the marketing Safety section to claim only what the product does (removes false emergency-services/auto-reporting/crisis-line claims). Source-only, held per Will's gate; live copy unchanged until landed.
Next action: Reconcile against the counsel-gated Terms/Privacy wording, then land with sign-off. Do not merge or deploy.
Owner: Daniel/counsel (Will to land after sign-off)
Priority: HELD

**GROOMING — 2026-08-03** **Status:** HELD pending attorney/counsel sign-off — corrects the marketing Safety section to claim only what the product does (removes false emergency-services/auto-reporting/crisis-line claims). Source-only, held per Will's gate; live copy unchanged until landed. **Next action:** Reconcile against the counsel-gated Terms/Privacy wording, then land with sign-off. Do not merge or deploy. **Owner:** Daniel/counsel (Will to land after sign-off) **Priority:** HELD
will.anderson added the HELD label 2026-08-03 18:59:53 +00:00
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix/safety-claims-match-shipped-behavior:fix/safety-claims-match-shipped-behavior
git checkout fix/safety-claims-match-shipped-behavior
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
BETA-CRITICAL
On the beta critical path — must resolve before ship
 HELD
Blocked pending an external decision (counsel / dual sign-off)
 ORTHOGONAL
Parallel workstream (testing/hardening) — safe to assign off critical path
 POST-BETA
Important but not blocking the beta ship
No labels HELD
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
andre.almeida (Andre Almeida) tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron-web#160
Delete Branch "fix/safety-claims-match-shipped-behavior"

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?