For PIs
Sal-Meter Kernel Program & Future Broader Opening — PI Readiness Edition v1.2 공모전 공지문이 아니라, 현재 단계와 준비 범위를 정확히 보여주는 PI / 연구실용 입구
This page is the PI-facing public surface for the current kernel program. It is designed to help principal investigators, laboratories, and technically serious teams understand what stage the program is actually in, what is already fixed, what remains open, what can be prepared now, and what must not be publicly overstated.
It is not a mass invitation page, not a product brochure, and not a signal that broad external competition is already active in the present tense.
The current operating model is internal kernel stabilization under ESL / EStL governance. No public competition is active before Lock 1 / Lock 2 confirmation and kernel freeze.
한국 연구자용 짧은 안내. 지금은 “바로 참가 신청”보다 정확한 이해와 준비가 먼저인 단계입니다. 전기화학, 압타머, 적산화환원, 신호처리, ML, 실험 설계, 통계, QC, 재현성 엔지니어링 쪽 연구실이라면 지금 당장 할 일은 한 가지입니다. 우리 팀이 실제로 맡을 수 있는 하나의 layer가 있는지, 그리고 그 layer를 current canonical boundary 안에서 과장 없이 수행할 수 있는지 보는 것입니다.
What this page is / 이 페이지의 정확한 성격
PI readiness surface
A public, non-clinical, pre-opening scientific coordination surface for principal investigators, laboratories, and serious technical teams.
Not a mass invitation
It should not imply that all external participation tracks are fully open now, or that a public competition is already active in the present tense.
Clarify stage and fit
It tells a serious lab what the current stage is, what is meaningful now, and which documents should be read before any claim of participation.
If your lab can realistically own one module and can operate within the present pre-opening boundary without overclaim, then this is early enough to matter and structured enough to test.
Current execution order / 현재 실행 순서
The current program must be read through its execution order. These stages must not be collapsed into “already-open competition.”
External Layer-0
Initial electrochemical feasibility and interface sensitivity work under controlled conditions.
SICS Internal Phase 0
G-axis first-stage state-separability testing under fixed baseline and SOP logic.
Phase 1
I-channel reproducibility fixation and single-channel stability confirmation.
Phase 2a
Twin Mini-Cell structural separation and cross-talk control.
Phase 2b
Human pilot with G + I combined sessions under fixed package architecture.
LOCK 1 / LOCK 2
Interface Exists / Interface Matters. Only after these locks does broader opening become a serious downstream pathway.
SDK / Future Broader Opening
Only after prior technical and validation locks are satisfied does broader opening become justified.
Older helper documents or legacy landing pages that still foreground “Open Competition Charter” language should be read through the current public rule: the kernel comes first, broader opening comes later.
Why PI readiness matters now / 왜 지금 PI readiness가 중요한가
Serious labs do not begin on announcement day
Strong laboratories begin earlier. They assess equipment, personnel, timing, scientific temperament, and governance discipline before any formal opening.
Readiness reduces noise and overclaim
This stage exists to reduce confusion, prevent premature claims, and help labs distinguish between canonical authority, helper surfaces, and what is not yet open.
Early labs shape the field
Long-term importance will not belong only to those who wrote about consciousness. It will belong to those who actually ran the early protocols, fixed the boundaries, and published the first reproducibility-facing results.
Korean labs can move early
한국 연구실은 장비와 프로토콜 감각이 좋은 경우가 많기 때문에, 지금처럼 구조가 아직 굳어지는 시기에 오히려 강한 포지션을 잡을 수 있습니다.
What a serious laboratory can do now / 지금 진지한 연구실이 할 수 있는 일
Read the canonical boundary first
Before any participation language, read the canonical definition, compliance boundary, negative definition, and broader-opening governance documents.
Identify one ownable layer
Determine whether your lab can realistically own one layer: chemistry, hardware, interface sensing, signal processing, statistics, protocol design, validation, or evidence standardization.
Prepare internal readiness
Review personnel, instrumentation, SOP discipline, metadata/QC capacity, and governance fit.
Use helper surfaces correctly
PI Quick, System Overview, Technical Snapshot, Minimal Kernel Diagram, and the GitHub kernel gateway exist to help your lab orient itself without replacing the canonical layer.
Avoid false public description
Do not imply certification, open participation standing, diagnostic legitimacy, or already-open competition status.
Watch the kernel with informed attention
Read the current stage carefully and decide whether your lab should enter later with clarity rather than noise.
지금의 핵심은 “참여 선언”이 아니라 “적합성 판단”입니다. 우리 팀이 무엇을 맡을 수 있는지, 무엇을 아직 말하면 안 되는지를 먼저 정리하는 것이 맞습니다.
Who should read this page / 이 페이지를 특히 봐야 하는 사람
Electrochemical / biosensor labs
Labs working in electrochemistry, redox measurement, biosensors, interfaces, electrodes, cartridges, and signal acquisition.
Signal processing / ML / statistics
Teams strong in noisy data interpretation, feature extraction, QC, validation structure, and auditability.
Neuroscience / cognition / anesthesia
Labs that can design controlled protocols involving sleep, meditation, stress, anesthesia, and related state transitions.
Research managers / governance-aware collaborators
Teams that understand open science without boundary control collapses into noise.
Current public operating structure / 현재 공개 운영 구조
Electrochemical Systems Lead
Owns physical consistency: measurement conditions, electrodes, cartridge logic, drift control, device behavior, and SOP stability.
Evidence & Standardization Lead
Owns evidence consistency: schema, QC, metadata discipline, leakage prevention, evaluation structure, standard documentation, and release logic.
What to read first / 먼저 읽을 문서와 페이지
Canonical anchors / 기준이 되는 canonical 문서
Connected public reading / 대중 서사와의 연결
Third-Party Audit
Why current evaluation still misses the human-state and relational layer.
Questions this page should answer clearly / 이 페이지가 분명히 답해야 할 질문
No. The current program is pre-opening and readiness-oriented. Broader external opening becomes serious only after prior technical and validation locks are satisfied.
A lab should first identify one ownable layer and review its internal readiness rather than assuming immediate full-spectrum participation.
Read PI Quick, System Overview, Technical Snapshot, the GitHub kernel gateway, and the canonical boundary documents; then determine whether the lab can support one concrete layer without overclaim.
Open sal-meter-kernel-program first if you are a technical team, PI, builder, or lab tracking the present kernel-stage program. Open salpida-canonical when you want the public GitHub index that routes outward to DOI-registered canonical records.
The center of gravity moved from “Open Competition Charter” language to “PI Readiness Edition” language, and the public operating model is now expressed through ESL / EStL with a stronger pre-opening boundary.