PI Quick Decision Pack
A five-minute Go / Conditional Go / Hold / No-Go surface for deciding whether a PI, lab, engineer, or builder has one bounded layer to evaluate now. PI, 연구실, 엔지니어, 채용 후보가 지금 단계에서 과장 없이 들어갈 수 있는지 빠르게 판단하는 helper 페이지입니다.
This page is an orientation surface, not a canonical specification. It helps a serious PI, lab, engineer, or builder decide quickly whether there is one bounded layer they can responsibly evaluate now.
Current public status: this page supports pre-opening PI readiness. It does not announce a live public competition. Current work remains research-stage, non-clinical, non-diagnostic, non-therapeutic, pre-device, and pre-certification.
이 페이지의 목적은 “참여 신청”이 아니라 “들어갈 수 있는 층위 판정”입니다
PI Quick Decision Pack은 깊은 기술문서를 읽기 전에, 연구실·PI·엔지니어가 지금 이 프로젝트의 어느 층위에 맞는지를 5분 안에 판단하게 만드는 페이지입니다.
핵심은 단순합니다. 현재는 broad opening이 아닙니다. External Layer-0, I₃⁻ aptamer inquiry, ESL / EStL, Sal-Meter kernel, Human-State AI proxy benchmark 중 하나의 좁은 문을 정확히 통과할 수 있는지 보는 단계입니다.
Four questions before deeper review
Should our lab even look at this now?
Yes, if your team can evaluate a scoped research-stage module while respecting terminology, boundary, data-rights, and public-claims control.
What can we evaluate now?
External Layer-0 feasibility, I₃⁻ aptamer development support, ESL / EStL referral, Sal-Meter kernel contribution, proxy benchmark readiness, or later-stage preparedness.
Is this already a broad external competition?
No. This is a pre-opening decision surface. Broader opening belongs after the fixed internal sequence and LOCK 1 / LOCK 2 review.
What should we read next if the answer is maybe yes?
Read Status first, then For PIs, PI Quick, PI Readiness, Technical Snapshot, and the current canonical boundary set.
Go / Conditional Go / Hold / No-Go
The right question is not “Is everything open now?” The right question is: Which bounded layer can this PI, lab, engineer, or builder responsibly support?
Scoped technical fit
The team can own one bounded layer, provide raw data / metadata discipline, avoid overclaims, and accept research-stage uncertainty.
Good expertise, weak structure
The team has the right expertise but needs tighter SOW, data handover, QC checklist, or publication boundary before engagement.
Future readiness only
The team may be useful later, but bandwidth, equipment, metadata discipline, or claims discipline is not ready yet.
Overclaim risk
The team wants clinical claims, product validation, certification language, exclusive public designation, or proxy-as-Sal-Meter framing.
Read the sequence before saying yes
The current program is not one open pool. It is a staged sequence: external feasibility first, internal kernel locking second, broader opening only after locks.
External feasibility support
Outsourced chemistry-first feasibility work. This is not SICS Internal Phase 0 and not SICS Internal Phase 1.
SICS Internal Phase 0
G-only internal state gate and baseline discipline. This is separate from External Layer-0.
I-only reproducibility lock
I₃⁻ target logic, I⁻ calibration discipline, and I-channel repeatability structure.
Twin Mini-Cell and G + I pilot
Cross-talk, leak control, and later locked human pilot evidence package.
Interface Exists / Interface Matters
Broader opening, SDK, and non-exclusive expansion belong only after LOCK 1 / LOCK 2 review.
Broader opening later
Public scaling, SDK, broader participation, and open competition architecture remain downstream.
Do not collapse the sequence. External Layer-0, Internal Phase 0, Phase 1, Phase 2a, Phase 2b, LOCK 1, LOCK 2, and broader opening must not become one present-tense participation claim.
Core signal track and proxy benchmark track are different doors
Sal-Meter / CAIS kernel route
The core track asks whether a new molecular–electrochemical signal interface can exist under the CAIS / Sal-Meter kernel program. This is where External Layer-0, G-only, I-only, Twin Mini-Cell, Phase 2b, LOCK 1, and LOCK 2 belong.
Human-State-Aware AI Interaction
The proxy track builds synchronized multimodal human-state benchmark infrastructure using existing signals such as ECG, HRV, EDA, PPG, EEG, eye / gaze, and interaction timing.
Two GitHub routes
Sal-Meter Kernel GitHub is the core technical gateway. Proxy Benchmark GitHub is the proxy benchmark helper. Neither is canonical authority.
Human-State-Aware AI Interaction and proxy-benchmark-track GitHub materials are proxy benchmark support surfaces only. They support future comparison and builder coordination; they do not substitute for the Sal-Meter molecular–electrochemical core signal track.
Proxy Benchmark v0.1.1 means helper-structure validation only
The current proxy-benchmark-track release should be described with one fixed sentence:
Bounded public helper pre-release
It packages corrected public helper structure after the synthetic sample package validator ran successfully.
No validation crown
It does not validate benchmark performance, scientific truth, Sal-Meter, CAIS compliance, certification, laboratory status, dashboard status, or mediation status.
Synthetic / sample only
It does not include raw human data, identifiable data, clinical data, Sal-Meter input, or CAIS-compliant measurement data.
OSF is the public research hub, not the authority layer
The OSF project is a public routing hub for the Proxy Benchmark Track and Human-State-Aware AI support layer. It helps reviewers, engineers, and collaborators move through the structure without confusing routing with authority.
00_START_HERE
First-read orientation and public boundary summary.
01_CANONICAL_DOI_STACK
DOI documents, license notice, and canonical stack index.
02_SYNTHETIC_EXAMPLES
Synthetic-only sample files for structure demonstration.
03_SCHEMA_HELPERS
Schema placeholders and helper documents.
04_PUBLIC_BOUNDARY_CHECKLISTS
Checks for raw data exclusion, public GitHub boundary, and claims boundary.
05_GITHUB_HELPER_INDEX
Proxy benchmark GitHub route and Sal-Meter kernel GitHub route.
OSF rule: OSF routes. GitHub helps. Website explains. DOI-registered SICS / CAIS / Sal-Meter / CCF records remain the authority layer.
지금 열려 있는 판단 경로
Iodine redox / thiol feasibility
For electrochemistry, biosensor, redox, gold-electrode, thiol / disulfide, drift, controls, and repeatability-capable labs.
Targeted development support
For aptamer and molecular interface groups capable of binding characterization, selectivity, cross-reactivity, and sensor suitability thinking.
Internal lead referral
For people or referrals suited to Electrochemical Systems Lead and Evidence & Standardization Lead roles.
Benchmark support only
For synchronized multimodal benchmark work, biosignal capture, dataset engineering, leakage control, edge inference, and dashboard prototypes.
Saliva compatibility, broad public opening, SDK, device framing, and clinical interpretation are not first-step claims. They belong downstream of baseline stability, modulation, specificity, repeated evidence, and lock review.
Who should read this page
Principal investigators and lab leads
For biosensing, electrochemistry, redox chemistry, aptamer, signal-processing, systems engineering, cognitive-state, or validation-oriented laboratories.
ESL / EStL candidates
For people who can lock physical consistency or evidence consistency: electrode behavior, drift, SOP discipline, metadata, QC, audit trail, holdout, and reproducibility pack.
PBEE · MDE · HSOPM
For biosignal / edge engineers, ML / dataset engineers, metadata architects, dashboard builders, and human-session operators.
GitHub helps builders. It does not create authority.
Sal-Meter Kernel Program
Core technical gateway for the kernel-first Sal-Meter / CAIS program. Use this route for core-track builders, ESL / EStL candidates, PI orientation, electrochemical systems contributors, and evidence-standardization readers.
Proxy Benchmark Track
Technical helper repository for schemas, synthetic examples, notebooks, dashboard drafts, issue templates, reproducibility checklists, and builder coordination.
salpida-canonical
DOI routing and public index helper. It helps users find canonical records, but it does not replace those records.
GitHub helps builders. DOI / OSF records define authority. Foundation pages route readers. No GitHub README, issue, example notebook, release note, or dashboard draft grants Sal-Meter designation, CAIS compliance, certification, conformance, clinical authority, or mark usage.
What belongs in public GitHub, and what must stay out
What belongs in the repository
README, metadata schema drafts, synthetic datasets, sample notebooks, dashboard mockups, issue templates, reproducibility checklists, public roadmap, and builder coordination.
What must stay out
Raw human data, identifiable session records, consent files, private labels, unreviewed performance claims, clinical interpretation, CAIS compliance claims, or Sal-Meter certification language.
The proxy-benchmark-track repository is a technical helper surface. It is not canonical authority and is not a Sal-Meter substitute.
Practical checklist before contact
- Review the current Sal-Meter / CAIS architecture as a research-stage measurement and validation program, not as a finished market product.
- Assess whether the team can work inside strict naming, compliance, publication, data-rights, and public-claims boundaries.
- Map the best fit: External Layer-0, I₃⁻ aptamer support, ESL / EStL referral, Sal-Meter kernel contribution, proxy benchmark, validation, statistics, biosignal engineering, or later readiness.
- Decide whether a narrow 3–6 month scoped feasibility or readiness path is realistic for bandwidth and expertise.
- Move only after reading the canonical layer that fixes designation, boundary, governance, and communication rules.
- If acting as a proxy benchmark team, build public examples without exposing raw human data or implying Sal-Meter status.
- If acting as a core-track team, respect the External Layer-0 → Internal Phase 0 → Phase 1 → Phase 2a → Phase 2b → LOCK 1 / LOCK 2 order.
This page does not authorize medical, diagnostic, therapeutic, certification, compliance, conformance, or Sal-Meter designation claims.
Read these before any public-facing claim
Sal-Meter Canonical Definition
Read this first to understand what the designation “Sal-Meter” is allowed to mean.
CAIS Compliance Boundary
Read this second to understand which conditions must be met before compliance-related language is legitimate.
Claims & Terminology Control
Read this third to prevent naming drift, false compliance claims, and premature certification language.
Publication & Communications Boundary
Read this fourth before any public-facing page, talk, post, hiring notice, recruitment message, or GitHub README claim.
The Future Broader Opening Charter is important, but it should be read as a post-lock governance document, not as proof that broad public competition is active now.
Where to go next
Go next to Status
Use this when the team needs the current operating model, present scope, and what is actually open now.
Go next to For PIs
Use this when the decision hinges on External Layer-0, I₃⁻ aptamer inquiry, ESL / EStL, Sal-Meter kernel, or proxy benchmark readiness.
Go next to Human-State AI
Use this if the team is a biosignal, ML / data, HCI, metadata, dashboard, edge-inference, or human-session operations group.
Roles should match the current operating surface
ESL
Electrochemical Systems Lead: responsible for physical consistency, interface stability, measurement discipline, drift control, SOP discipline, and interface reliability.
EStL
Evidence & Standardization Lead: responsible for evidence integrity, metadata discipline, QC, leakage control, audit trail, holdout design, and reproducibility package logic.
PBEE · MDE
Biosignal / edge engineering and ML / dataset engineering for benchmark-support infrastructure only.
HSOPM
Consent pathway, participant flow, session timing, metadata completion, and raw-data governance.
Public PI-facing pages should reflect the ESL / EStL structure consistently and avoid older public-facing role language that conflicts with the current operating surface.
Questions a serious PI or builder should ask internally
- Can our lab operate inside a research-stage, non-clinical, non-diagnostic boundary without drifting into overclaim?
- Do we have a natural fit in External Layer-0, I₃⁻ aptamer development, Sal-Meter kernel contribution, internal lead referral, proxy benchmark, validation, statistics, or future readiness?
- Can we commit a bounded exploratory effort instead of demanding a fully commercialized surface on day one?
- Can we deliver raw data, complete metadata, control logic, repeatability records, and audit trail if asked?
- Are we willing to work inside a layered architecture where canonical authority and helper surfaces are deliberately separated?
- If we are a proxy benchmark team, can we build public examples without exposing raw human data or implying Sal-Meter status?
- If we are a core-track team, can we respect the External Layer-0 → Internal Phase 0 → Phase 1 → Phase 2a → Phase 2b → LOCK 1 / LOCK 2 order?
This page is a fast gate, not a grant of rights
This page is a non-canonical public helper and routing surface. It does not grant CAIS compliance, Sal-Meter designation, certification status, mark usage, publication authorization, clinical authority, diagnostic authority, therapeutic authority, or broad-opening participation rights.
Proxy benchmark materials support comparison infrastructure and builder recruitment only. Sal-Meter Kernel GitHub and Proxy Benchmark GitHub are helper surfaces only.
Final rule: DOI / OSF records govern. Website explains. GitHub helps. Helper surfaces do not override canonical records.