Working Session
Six topics. Mayo Waypoints September 20 is the spine. ISTAND is now Robert-confirmed best fit. The shotgun approach to parallel programs, the Aug 31 business-plan milestone, training plan, MAYO.md, and the web pages all feed into it.
Attendees
- Marjorie McCubbins · Founder, Nexus Concordat Inc.
- Aislinn McCubbins · COO, Dynamic Hallucination Inc.
- Jason Alba · Board of Directors and investor, Dynamic Hallucination Inc.
- Robert Michalik · External regulatory advisor
- Shailee Desai · Regulatory affairs intern (Northeastern University M.S. Regulatory Affairs); NDA pending e-signature before meeting
Agenda at a glance
| # | Topic | Lead | Time |
|---|---|---|---|
| 1 | Mayo Waypoints status | Marjorie | 10 min |
| 2 | ISTAND pathway (Robert confirmed best fit) and shotgun approach to parallel programs | Robert and Marjorie | 15 min |
| 3 | Training plan update. What we have learned. What we are doing. | Marjorie and Aislinn | 15 min |
| 4 | Where do we want to be by Aug 31. Business plan dust-off. | Jason lead, all input | 15 min |
| 5 | Web pages walkthrough (incl. NeXus LOI live draft) | All | 10 min |
| 6 | Decisions, next steps, Shailee onboarding lane | All | 10 min |
1. Mayo Waypoints status 10 min
The Mayo Clinic Berg Innovation Exchange Waypoints Program application is due September 20, 2026. Selection decisions September 28. Program runs October through December.
We are invited by David Kim, Business Analyst at the Berg Innovation Exchange, following his June 22 personalized invitation.
Application page status
Live working draft at /mayo.html. Pages 1 through 4 of the application have placeholder drafts. Structure is in place. Polishing happens after Jason, Aislinn, and Robert review.
What we are positioning as
A psychiatry residency training simulation platform built on our patent pending neurochemical cascade architecture. Non device. Non diagnostic. Training infrastructure that complements (and partially replaces) standardized patient actor programs.
2. ISTAND pathway and the shotgun approach 15 min
ISTAND is confirmed as the regulatory pathway. The Mayo credibility lever (a submitted ISTAND application in past tense by September 20) is now Robert's framing, not just ours.
The LOI we have drafted
Live working draft at /nexus-loi.html. NeXus framed as deployment of the patent-pending Aether neurochemical cascade architecture. CoU statement at 270 characters. Six-layer proof framework. Appendix A formalizes the opcode definition and fidelity verification protocol. Walk through during this section so everyone is on the same page.
The shotgun approach (Robert's direction)
Per Robert: “Find one or two other similar programs (incubators, investor pools, etc) and generate a core application but tailor to each one. Shotgun approach toward finding resources and potential partners.”
Candidates to scope tonight or in this meeting:
- Golden Seeds info session June 29 (already on Marjorie's calendar)
- Mayo Clinic Berg Innovation Exchange Waypoints September 20 (central commitment)
- Critical Path Innovation Meeting (CPIM) at FDA as a softer parallel touchpoint to ISTAND
- Other targets to identify in meeting: Y Combinator Bio, Indie.vc, Activate Fellowship, MassBio, JLABS, BioInnovation Capital, regional health-tech incubators
Working CoU (locked into the LOI)
In-silico simulation environment to model biomarker dynamics, interactions, and perturbation responses for hypothesis generation in psychiatric drug development, supporting design of subsequent clinical confirmation studies of candidate biomarker contexts of use.
Open question for Robert
The new operating entity. We are forming NeXus Neuroinformatics, Inc. as the FDA-facing entity so it (not Nexus Concordat Inc.) is the Requester. Form before or after LOI submission? Same Harvard Business Services / Delaware C-Corp path as DH Inc.?
3. Training plan update. What we have learned. What we are doing. 15 min
Status of the technical work. Aislinn, Jason, and Robert need the same picture.
What is live (already shipping)
- cardiac_gen3 specialist cell. Serving live at /cell-demo.html. Signed inference manifests. SHA 256 verifiable against the public registry.
- Public cell lineage registry. /registry/cardiac-registry.json for byte exact external verification.
- Vanilla baseline. Running alongside the chemistry conditioned cell on the demo page for direct comparison.
What landed in the last week
- psych_gen1 v3 final checkpoint exists on disk. Training completed against the cardiac_gen4 foundation.
- Corpus format bug from v1 and v2 resolved. Lesson learned: read_int_tokens in Scyla requires one token per line, not space separated. v1 and v2 both mode collapsed to PAD. v3 trains correctly with the one token per line format. Memory anchored so future sessions cannot repeat the mistake.
- Foundation freeze invariant verified empirically. Cardiac brain SHA stayed byte identical across the new psych training run. The architectural claim that frozen heads cannot be corrupted by new specialty training is no longer a design assertion. It is a measurement.
- Cardiac phonics tokenization committed. The two parallel representation problem (whole word IDs vs syllabic IDs in one embedding table) was resolved by retokenizing the cardiac corpus through phonics. Loss recovered from the bridge attempt’s mode collapse.
What is happening next
- Mayo demo harness. Same character, same baseline, change one variable (normal med timing vs missed dose vs sleep loss vs added stressor). Behavior divergence rendered side by side. This is what David Kim should see.
- psych_gen1 v3 probe and coherence check. Run a probe to verify the v3 checkpoint generates coherent psych text. If yes, advance to Mayo harness. If not, train v4 with longer step count and/or per segment chemistry tagging.
- Foundation read only contract. Smoke check cardiac after psych training to confirm freeze invariant still holds for the live deployed brain.
What is in the queue but not yet started
- Third specialist cell (endocrine, neurology, or GI candidate, decided by Q4)
- Per segment chemistry tagging for psych corpus (v2 problem, not v1 blocker)
- DailyMed re pull (currently 0 byte files in raw; deferred from v1 since PubMed pull covered the load bearing dose / half life / missed dose language)
4. Where do we want to be by Aug 31. Business plan dust-off. 15 min
Robert's framing for this section, June 23: “dust off the basic business plan and figure out where you want to be or should be by Aug 31st.”
Aug 31 sits about three weeks before the Mayo Waypoints application deadline (Sept 20). The business plan needs to be coherent enough by Aug 31 to support the Mayo application without scrambling in the final two weeks.
Decisions Jason should drive in this section
- Three-entity structure formalization. Nexus Concordat Inc. (IP holder), NeXus Neuroinformatics Inc. (FDA-facing operating entity, to be formed), Dynamic Hallucination Inc. (consumer / game). Confirm cap-table and governance implications of forming the new entity before Mayo submission.
- Revenue model articulation. SaaS subscription, per-seat, per-simulation, per-opcode access, per-specialty licensing. Which goes in the Mayo deck.
- Funding posture. Bootstrapped vs. angel vs. accelerator. The Waypoints application asks specifically. Same question recurs at Golden Seeds info session.
- Aug 31 milestones we commit to publicly — Mayo deck draft, ISTAND Pre-LOI meeting held or scheduled, NeXus Neuroinformatics incorporation in progress, Shailee design-control deliverables landing.
What Jason and Robert each need from Marjorie
- Jason: business plan dust-off; revenue model articulation; Aug 31 milestone commitment
- Robert: ISTAND Pre-LOI package readiness assessment; regulatory milestone interlock with business milestones
4b. MAYO.md update. Reset the target. 5 min
The MAYO.md file at /home/nexus_concordat/scyla-nca/MAYO.md is the canonical target spec for the prototype. It says, verbatim: the product is the game; the game funds the research; the game is also the safe simulation environment; do not train it to diagnose; train it to support synthetic state simulation.
What needs updating in MAYO.md
- v3 checkpoint exists. Update from “v3 currently running” to “v3 final landed.”
- Mayo demo harness is the next step. Add as Section 9 if needed.
- Cross link to the Waypoints application page at /mayo.html so the file and the public page are connected.
- Add the ISTAND framing as a separate downstream track. Not the primary target. The primary target stays the simulation demo for Mayo.
5. Web pages walkthrough 10 min
Walk through each page live. Take comments. Capture factual corrections.
| Page | What it is |
|---|---|
| patent.nexusconcordat.com | Portfolio home, public face |
| /mayo.html | Mayo Waypoints application working draft |
| /nexus-loi.html | NeXus LOI working draft (new tonight; review during section 2) |
| /our-training-method/ | Four head method explainer (originally for Jason) |
| /cell-demo.html | Live cardiac specialist with signed manifests |
| /jason-plan.html | Architectural plan (cell as opcode tree) |
| /sister-cell.html | Training plan and trajectory |
6. Decisions, next steps, Shailee onboarding lane 10 min
Decisions to extract
- ISTAND July artifact. Pre-LOI meeting request package, Letter of Support, or full LOI submission. Robert calls.
- NeXus Neuroinformatics Inc. formation timing. Before or after LOI submission. Jason and Marjorie call together.
- Shailee reporting line. Under Robert (regulatory natural fit), under Marjorie (CEO direct), or under Aislinn (COO operational). Decide so Shailee has one named supervisor.
- Mayo sign off cadence. When do Aislinn, Jason, and Robert each pass the application sections they are responsible for? Target: Aug 31 review-ready, Sept 15 final.
- Aug 31 business plan commit. Per Robert's prompt. Jason owns.
- MAYO.md update. Marjorie updates this week. Anyone want review rights before commit?
- Next sync cadence. Weekly through July, then twice monthly through September?
Shailee onboarding lane (new)
- NDA. Sent to Robert tonight as
MUTUAL_NDA_NEXUS_CONCORDAT_DESAI.pdfat /uploads/MUTUAL_NDA_NEXUS_CONCORDAT_DESAI.pdf. Robert to have Shailee e-sign before this meeting. - Scope. Design Control system buildout, Design History File compilation per 21 CFR 820.30, IEC 62304, IEC 82304.
- Reporting line. To be decided in this meeting (see decision #3 above).
- Bio standing rule. Shailee sends her own title and description when ready to be named publicly on mayo.html or in the LOI's supporting organizations list. We do not write it for her.
Open items if time
- Critical Path Innovation Meeting (CPIM) as a softer parallel FDA touchpoint
- FDA Town Hall on General Wellness follow up
- Bios from Robert and Jason for the Mayo page (each sends own title, role, LinkedIn URL)
- QP gap analysis review (stage 2 doc structure mapped against current state)
- FQP structure (stage 3) queued for awareness, not action