DevDay / share / QR follow-up
Operator-controlled follow-up
Private access is not self-serve. This is an informational route for continuing an existing operator-led conversation; it does not collect contact details, submit a request, create an account, or grant access.
Share or encode the existing route: /request-invite. During an in-person handoff, agree on the operator-controlled channel for continuing the conversation. A shared link or QR code does not submit a request or grant an invitation.
Existing invited account identity is used only for authentication; it must not be included in case inputs or remote content.
Invite-only remains enforced
Private evaluation stays authenticated and operator-controlled. Visiting or sharing this page cannot grant access.
Manual follow-up only
Use an existing face-to-face or operator-established channel. There is no form, public signup, inbox, or request submission.
Public demo stays available
The frozen deterministic NepsisCGN public proof remains separate from NepsisMC and any private evaluation.
How to follow up safely
Use only a channel the operator has already established. This page does not provide or invent a public contact address.
- Continue through your face-to-face conversation or an operator-established channel you already have.
- Distinguish the local NepsisMC governed cockpit from the separate private CGN evaluation path.
- Keep case inputs and remote content non-sensitive and operator-cleared: no PHI, direct identifiers, private communications, or secrets.
- Wait for a separate explicit operator decision before any private access or evaluation.
No information is submitted or stored here. Only the operator can make a separate access decision. Operational audit or usage telemetry is not human-study or participant evidence, and CGN authority remains inactive.