[Layer-0] Candidate lab outreach tracker

[salpida-foundation]

Purpose

Track candidate laboratories for the External Layer-0 feasibility route.

This issue converts the public START HERE route into a bounded execution tracker for identifying, reviewing, contacting, and prioritizing external laboratories that may be suitable for a narrow Layer-0 mini-pilot or feasibility discussion.

This issue is for outreach tracking only.

This issue does not create Sal-Meter validation.

This issue does not create CAIS compliance.

This issue does not create certification.

This issue does not create device readiness.

This issue does not create production readiness.

This issue does not create clinical, diagnostic, therapeutic, counseling, or surveillance status.

This issue does not open a public competition.

This issue does not authorize public claims by candidate labs.

---

Route basis

This issue follows the current START HERE route:

• External Layer-0 feasibility inquiry
• chemistry-first external feasibility support
• not SICS Internal Phase 0
• not Phase 1
• not Sal-Meter validation
• not CAIS compliance
• not certification
• not device designation
• not clinical status
• not diagnostic status

Core question:

Can iodine redox / thiol-interface behavior produce stable, repeatable, auditable signal behavior under bounded feasibility conditions?

---

Candidate lab fit criteria

Candidate labs should have credible experience in one or more of the following:

• electrochemistry
• biosensors
• redox chemistry
• gold-electrode interface work
• iodine / iodide / triiodide electrochemistry
• thiol / disulfide chemistry
• GSH / GSSG perturbation systems
• OCP / CV / DPV / SWV / EIS measurement
• drift control
• repeatability testing
• blank / control design
• raw electrochemical data export
• metadata discipline
• feasibility study reporting

Preferred candidate profile:

A lab that can run a narrow 4–8 week feasibility study with raw electrochemical traces, controlled perturbation conditions, repeated runs, blank/control records, drift table, protocol notes, and a short technical recommendation.

---

Candidate lab tracker

Use the table below for candidate tracking.

#	Lab / PI / Group	Institution / Company	Country	Fit area	Evidence link	Contact status	Technical fit	Boundary risk	Next action
1	TBD	TBD	TBD	TBD	TBD	Not contacted	TBD	TBD	Identify candidate
2	TBD	TBD	TBD	TBD	TBD	Not contacted	TBD	TBD	Identify candidate
3	TBD	TBD	TBD	TBD	TBD	Not contacted	TBD	TBD	Identify candidate
4	TBD	TBD	TBD	TBD	TBD	Not contacted	TBD	TBD	Identify candidate
5	TBD	TBD	TBD	TBD	TBD	Not contacted	TBD	TBD	Identify candidate

Contact status options:

Not contacted
Shortlisted
Email drafted
Email sent
No response
Response received
Meeting requested
Meeting scheduled
Meeting completed
SOW candidate
Hold
Rejected

Technical fit options:

High
Medium
Low
Unknown

Boundary risk options:

Low
Medium
High
Unknown

---

First outreach message requirements

Any first email must remain bounded.

The first outreach message should state:

• this is a research-stage feasibility inquiry;
• the scope is External Layer-0 only;
• the initial focus is iodine redox / thiol-interface feasibility;
• the expected output is bounded feasibility evidence, not validation;
• raw electrochemical traces and metadata discipline are expected;
• no clinical, diagnostic, therapeutic, or surveillance claim is being made;
• no Sal-Meter validation or CAIS compliance is being granted;
• no public statement may be made without approved boundary language.

The first outreach message must not state or imply:

• validated Sal-Meter;
• CAIS-compliant device;
• clinical device;
• diagnostic tool;
• therapeutic system;
• certified system;
• production readiness;
• public competition opening;
• human-state measurement proof;
• consciousness proof;
• successful validation.

---

Initial technical question set

Candidate labs should be evaluated using these questions:

1. Can the lab run gold-electrode iodine / KI electrochemical measurements?
2. Can the lab measure OCP, CV, DPV, SWV, or EIS?
3. Can the lab test iodine redox response under mild redox perturbation?
4. Can the lab test GSH / GSSG or thiol/disulfide-related perturbation?
5. Can the lab run blank and control conditions?
6. Can the lab repeat same-day runs for directional consistency?
7. Can the lab report drift, noise, and repeatability?
8. Can the lab export raw electrochemical data?
9. Can the lab maintain protocol notes and metadata?
10. Can the lab deliver a short technical recommendation after feasibility testing?

---

Mini-pilot deliverable expectation

A candidate Layer-0 mini-pilot should be expected to provide, at minimum:

• raw OCP / CV / DPV / SWV / EIS traces where applicable;
• protocol notes;
• reagent / buffer / electrode notes;
• perturbation condition records;
• blank and control records;
• repeatability summary;
• drift table;
• noise / baseline stability notes;
• anomalies / failure notes;
• summary of whether a next-step feasibility path is justified.

This issue does not approve a mini-pilot by itself.

A separate SOW / agreement / internal approval is required before any paid work begins.

---

Public / private boundary

Public GitHub may contain:

• candidate tracking structure;
• generic criteria;
• non-confidential route description;
• public links;
• bounded status notes;
• non-sensitive summary decisions.

Public GitHub must not contain:

• private emails;
• private quotes from candidate labs;
• confidential technical proposals;
• pricing details;
• personal contact details not already public;
• unpublished experimental data;
• raw electrochemical data from paid work;
• contract drafts;
• legal terms;
• sensitive IP discussion;
• candidate rejection details that could harm reputation.

Private materials should go to the controlled-access data room, not this public issue.

---

Decision categories

Each candidate should eventually be placed into one of the following categories:

A — Strong candidate for first technical meeting
B — Possible candidate; needs additional review
C — Hold; insufficient fit or unclear capability
D — Reject; not appropriate for Layer-0
E — Future contact only

---

Completion condition

This issue is complete when:

• at least 5 candidate labs or groups are identified;
• each candidate has a public evidence link or reason for inclusion;
• each candidate has a preliminary fit area;
• each candidate has a technical fit rating;
• each candidate has a boundary risk rating;
• at least 3 candidates are selected for first outreach or technical inquiry;
• outreach message boundary is confirmed;
• no private candidate data is exposed publicly;
• no validation, certification, CAIS compliance, Sal-Meter status, device readiness, production readiness, or production authority claim is introduced;
• next action is recorded for each candidate.

---

Final boundary

This issue is a candidate lab outreach tracker only.

It is not validation.

It is not certification.

It is not Sal-Meter.

It is not CAIS compliance.

It is not device readiness.

It is not production readiness.

It is not production authority.

It does not create a DOI.

It does not open a public competition.

It does not authorize any public claim by an external lab.

The repository remains a public technical helper and implementation index.

Canonical authority remains fixed in DOI / OSF records and the Salpida Foundation public routing structure.

[salpida-foundation]

Execution tracker opened.

A bounded execution tracker has been opened for the External Layer-0 feasibility route:

• [Layer-0] Candidate lab outreach tracker #7 — [Layer-0] Candidate lab outreach tracker

#5 remains open and pinned as the public START HERE / routing anchor.

#7 is the execution tracker for identifying, reviewing, contacting, and prioritizing candidate laboratories for a narrow External Layer-0 feasibility discussion.

Boundary retained:

• [Layer-0] Candidate lab outreach tracker #7 does not create Sal-Meter validation.
• [Layer-0] Candidate lab outreach tracker #7 does not create CAIS compliance.
• [Layer-0] Candidate lab outreach tracker #7 does not create certification.
• [Layer-0] Candidate lab outreach tracker #7 does not create device readiness.
• [Layer-0] Candidate lab outreach tracker #7 does not create production readiness.
• [Layer-0] Candidate lab outreach tracker #7 does not open a public competition.
• [Layer-0] Candidate lab outreach tracker #7 does not authorize public claims by candidate labs.

Status first. Kernel first. Claims later.

[salpida-foundation]

Founder-seeded candidate list exists.

The initial candidate lab list has been prepared internally by the founder.

However, this list is not yet an outreach-authorized shortlist.

Next required step:

• Bridge Advisor technical review
• PM/COO operational review
• counsel review for data / publication / IP / public-claims boundary
• then selective outreach

Until that review is complete, no candidate lab should be treated as approved, selected, contracted, or research-engaged.

Boundary retained:

• This issue remains a candidate lab outreach tracker only.
• This issue does not create Sal-Meter validation.
• This issue does not create CAIS compliance.
• This issue does not create certification.
• This issue does not create device readiness.
• This issue does not create production readiness.
• This issue does not open a public competition.
• This issue does not authorize public claims by candidate labs.

Founder-seeded longlist → Bridge Advisor-reviewed shortlist → counsel/PM-cleared outreach list → SOW candidate.

[salpida-foundation]

Bridge Advisor technical review issue opened:

• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 — [Bridge Advisor] Layer-0 candidate shortlist technical review

#7 remains the public candidate lab outreach tracker.

#8 provides a technical review layer before any outreach, meeting request, SOW discussion, or paid feasibility work.

Current execution sequence:

Founder-seeded longlist
→ Bridge Advisor-reviewed shortlist
→ PM / counsel-cleared outreach list
→ first technical meeting
→ possible mini-pilot SOW candidate

Boundary retained:

• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not contact candidate labs.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not approve paid work.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create a SOW.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create Sal-Meter validation.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create CAIS compliance.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create certification.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create device readiness.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not create production readiness.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not open a public competition.
• [Bridge Advisor] Layer-0 candidate shortlist technical review #8 does not authorize public claims by candidate labs.