Sal-Meter
The CAIS-aligned core signal track CAIS / CCF 구조 안에서 살미터의 현재 위치, 코어 신호 트랙, 프록시 benchmark 경계, PI·랩·엔지니어 진입 경로를 정리하는 토픽 허브
Sal-Meter is currently presented as a research-stage CAIS-aligned molecular–electrochemical core signal path, not as a certified, validated, commercial, clinical, diagnostic, or therapeutic device.
This page distinguishes the Sal-Meter core signal track, the Sal-Meter Kernel GitHub helper route, the Sal-Meter Kernel Pre-SRA Helper Package v0.1.0, the Human-State-Aware AI proxy benchmark track, PI / laboratory readiness routes, engineer and builder roles, and the canonical DOI records that control naming, claims, compliance, and public language. 이 페이지의 목적은 살미터 코어 트랙과 프록시 benchmark 트랙을 혼동하지 않게 하고, 연구자·PI·엔지니어·채용 후보가 현재 단계에서 무엇을 읽고 어디로 들어가야 하는지 안내하는 것입니다.
Sal-Meter Kernel Pre-SRA Helper Package v0.1.0 has been released as a GitHub public helper pre-release. It supports External Layer-0 feasibility inquiry, Layer-0 data deliverables, public/private data boundary, aptamer inquiry boundary, ESL/EStL role separation, Layer-0 task routing, and 90-day pre-SRA execution gates. It does not create Sal-Meter validation, CAIS compliance, certification, device readiness, clinical status, public SDK release, or public competition opening.
Sal-Meter is a future-facing CAIS-bound measurement pathway under active research. Current public materials should describe it as research-stage, pre-opening, non-clinical, non-diagnostic, non-therapeutic, pre-device, and pre-certification.
This page does not grant CAIS compliance, Sal-Meter designation, certification, conformance recognition, clinical status, device status, or mark usage. Canonical authority remains fixed in DOI / OSF records.
Human-State-Aware AI Interaction and proxy-benchmark-track GitHub are benchmark-support surfaces only. They do not replace the Sal-Meter core molecular–electrochemical signal path.
Sal-Meter Kernel GitHub is the core technical gateway for builders. Proxy Benchmark GitHub is the benchmark-support helper repository. Neither GitHub repository is canonical authority.
GitHub proxy-benchmark-track v0.1.1 is a post-validator-pass public helper pre-release. It is not Sal-Meter. It is not CAIS compliance. It is not benchmark validation. It contains no raw human data. DOI-registered SICS records remain the authority layer.
Authority map / 권위 경로
This page is a public explanation and routing surface for the Sal-Meter topic. Canonical definitions and claims boundaries remain fixed in DOI-registered records. OSF organizes public research routes. GitHub provides technical helper surfaces. The Salpida Foundation website explains the path. 이 페이지는 Sal-Meter 주제의 공개 설명과 경로 안내를 위한 표면입니다. 정본 정의와 주장 경계는 DOI 등록 문서에 고정되어 있고, OSF는 공개 연구 경로를 정리하며, GitHub는 기술 보조 표면으로만 사용됩니다.
Zenodo DOI
Canonical definitions, version records, naming boundaries, claims limits, and certification language remain fixed in DOI records.
OSF
OSF routes public research materials and document stacks. It is not raw human-data storage and does not override DOI authority.
GitHub
GitHub helps builders and technical readers. It does not create canonical authority, CAIS compliance, Sal-Meter validation, or certification.
Website
The Foundation website explains the public route, separates core and proxy tracks, and directs readers to the correct authority layer.
Fast reading rule / 가장 먼저 읽을 규칙
Current stage comes first
Read the current program state before reading future-opening, competition-related, or GitHub-based helper material.
Pre-SRA route comes before negotiation
Use v0.1.0 to understand Layer-0 scope, data deliverables, public/private boundary, aptamer inquiry boundary, and ESL/EStL role separation.
Sal-Meter core is molecular–electrochemical
The core track concerns the existence and stability of a new signal interface.
Proxy benchmark is not Sal-Meter
ECG, HRV, EDA, PPG, EEG, eye, and gaze signals may support benchmarking, but they do not replace the core Sal-Meter signal track.
Core track vs Proxy benchmark track
Does a new signal interface exist?
The core track tests whether the CAIS / Sal-Meter molecular–electrochemical pathway can produce stable, directional, repeatable, auditable signal behavior.
- External Layer-0: iodine redox / thiol interface feasibility
- SICS Internal Phase 0: G-only internal state gate
- Phase 1: I-only reproducibility lock with I₃⁻ target logic
- Phase 2a: Twin Mini-Cell leak and cross-talk control
- Phase 2b: G + I human pilot under locked evidence package
- LOCK 1 / LOCK 2 before SDK or broader opening
Can we build the comparison baseline now?
The proxy track builds a synchronized multimodal benchmark platform using existing signals. It prepares data discipline, synchronization, labeling, leakage control, edge inference, and future A/B comparison.
- ECG / HRV
- EDA / PPG
- optional EEG
- eye / gaze / behavioral timing
- local dashboard and synthetic public examples
- future comparison layer for Sal-Meter inputs
The proxy benchmark track supports the program, but it does not define, validate, replace, or certify the Sal-Meter core signal track.
Sal-Meter Kernel Pre-SRA Helper Package v0.1.0
The v0.1.0 release freezes the first public helper package for the Sal-Meter Kernel Program before SRA-facing External Layer-0 and aptamer inquiry work. It exists to make a serious lab, advisor, PM/COO, and legal conversation executable without inflating public claims.
Layer-0 SOW
External Layer-0 mini pilot scope and feasibility question.
Data deliverables
Raw traces, metadata, run map, QC, failed-run and anomaly expectations.
Public / private boundary
What may be public on GitHub and what must remain private or controlled-access.
Aptamer inquiry boundary
Public I₃⁻ / Aptamer G-Iodine inquiry without sequence-sensitive leakage.
ESL / EStL split
Physical measurement review separated from evidence-standardization review.
Issue template
Public-safe Layer-0 task routing, boundary checks, and completion criteria.
Release snapshot
First public helper package frozen as v0.1.0.
What it does not grant
No validation, compliance, certification, device readiness, clinical status, public SDK, or public competition opening.
Fixed program order / 고정 실행 순서
External Layer-0
Chemistry-first external feasibility support for iodine redox / thiol interface behavior, baseline stability, perturbation response, and repeatability.
SICS Internal Phase 0
G-only internal state gate. This is separate from External Layer-0 and must not be collapsed into it.
Phase 1
I-only reproducibility lock with I₃⁻ target logic and I-channel discipline.
Phase 2a / 2b
Twin Mini-Cell, cross-talk control, G+I pilot, then LOCK 1 / LOCK 2 before SDK or broader opening.
External Layer-0 → SICS Internal Phase 0 (G-only) → Phase 1 (I-only) → Phase 2a → Phase 2b → LOCK 1 / LOCK 2 → post-lock SDK / broader opening.
Current research entry / 현재 연구 진입 경로
Iodine redox / thiol feasibility
External Layer-0 is a chemistry-first feasibility support track. It checks iodine redox baseline, thiol-linked perturbation response, drift, stability, controls, repeatability, raw data, and metadata completeness.
Targeted development inquiry
The aptamer track concerns I₃⁻-targeted development support, binding characterization, selectivity, cross-reactivity, immobilization suitability, and sensor-oriented readiness.
Internal lead recruitment
Internal leads are needed to lock physical consistency and evidence consistency before the program can move safely downstream.
Human-State AI / Proxy Benchmark route
Human-State-Aware AI Interaction
This track builds synchronized multimodal benchmark infrastructure before Sal-Meter inputs are available. It is useful for testing capture, synchronization, labeling, holdout, leakage control, baseline models, and feedback loops.
proxy-benchmark-track v0.1.1
Use the current v0.1.1 release for public helper orientation, schemas, synthetic examples, repository hygiene, and boundary documentation. It is not validation.
05_GITHUB_HELPER_INDEX route
OSF routes DOI stack, synthetic examples, public boundary checklists, and GitHub helper index. It should point to v0.1.1 while preserving authority boundaries.
Public GitHub may contain sample data, synthetic data, example code, metadata schemas, and dashboard drafts. Raw human data, consent records, identifiable session records, private labels, and unreviewed performance claims must stay out.
Role map / Execution functions and candidate routes
These are execution functions and candidate routes, not immediate full-time hiring positions. In the current lean execution model, functions may be fulfilled through external SRA laboratories, mini-pilot contractors, Bridge Advisors, fractional reviewers, contracted technical teams, or future hires. 아래 항목은 즉시 정규직 채용 포지션이 아니라 실행 기능과 후보 경로입니다. 현재 lean execution model에서는 외부 SRA 랩, mini-pilot 계약자, Bridge Advisor, fractional reviewer, 계약형 기술팀 또는 향후 채용 인력이 일부 기능을 담당할 수 있습니다.
ESL
Electrochemical Systems Lead function. Owns physical consistency: electrode behavior, interface stability, acquisition discipline, drift handling, cleaning discipline, and SOP lock.
May be fulfilled initially by a Bridge Advisor, external electrochemistry lab lead, or fractional technical reviewer.
EStL
Evidence & Standardization Lead function. Owns evidence consistency: metadata, QC, leakage prevention, audit trail, reproducibility pack, and claims discipline.
May initially be fulfilled through a fractional EStL function or a Validation/Data Engineer under PM/COO supervision.
PBEE · MDE
Proxy benchmark engineering function. Supports biosignal / edge engineering, ML / dataset engineering, synthetic samples, baseline models, dashboard flow, and leakage-safe evaluation.
May be fulfilled by a contracted proxy team, ML/data contractor, or future internal engineer.
HSOPM
Human-session operations function for future consent-bound pilots. Supports consent pathway, participant flow, session timing, labeling discipline, metadata completeness, and raw data governance when real human pilots begin.
Not required for synthetic-only helper work.
GitHub route separation / GitHub 경로 분리
sal-meter-kernel-program
Core technical gateway for the kernel-first Sal-Meter / CAIS program. Use this for core-track orientation, External Layer-0 context, ESL / EStL routing, technical issues, and builder helper materials.
- Core program orientation
- Layer-0 and kernel path
- ESL / EStL candidate route
- PI / engineer helper surface
- Not canonical authority
proxy-benchmark-track v0.1.1
Technical helper release for synchronized multimodal benchmark infrastructure: schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists.
- Metadata schema drafts
- Synthetic / sample data
- No raw human data
- Not Sal-Meter
- Not CAIS compliance
- Not benchmark validation
DOI / OSF controls meaning
GitHub is a public helper and builder surface. It cannot redefine Sal-Meter, grant CAIS compliance, certify a system, or override DOI / OSF canonical records.
- README is not canonical authority
- Issue labels are not conformance recognition
- Example code is not validation
- Dashboard drafts are not certification
- Canonical DOI / OSF records prevail
Browse by purpose / 목적별로 보기
Understand what Sal-Meter is
Start here if the goal is to understand the measurement path and why it is not interchangeable with conventional biosignal devices.
살미터가 정확히 무엇인지, 왜 일반 생체신호 장치와 같은 것이 아닌지 먼저 알고 싶을 때 적합합니다.
Check what is open now
Start here if the main question is what is active now, what is readiness only, and what remains future-facing.
지금 열려 있는 것과 아직 열리지 않은 것을 구분하고 싶을 때 먼저 봐야 합니다.
Check scoped entry routes
Start here if the reader is a PI, lab lead, engineer, or technical contributor evaluating current fit.
External Layer-0, I₃⁻ 압타머 개발 의뢰, ESL/EStL 채용 연결, 내부 lab readiness를 확인할 때 이 길이 가장 빠릅니다.
Enter the Sal-Meter Kernel GitHub
Start here if the reader is an electrochemical systems contributor, evidence-standardization contributor, ESL / EStL candidate, or core technical collaborator.
코어 기술 기여자는 GitHub에서 README, current routes, issue structure, helper docs를 먼저 확인하면 됩니다.
Main reading anchors / 핵심 읽기 축
What the name points to
Sal-Meter refers to a CAIS-bound research-stage measurement pathway. It should not be used as a free label for any biosignal device, proxy stack, or wellness monitor.
What does not count
EEG-only devices, HRV-only trackers, private renamed scores, closed unverifiable systems, or proxy-only stacks should not be presented as Sal-Meter.
What stage this belongs to
The correct public language is research-stage, pre-opening, non-clinical, non-diagnostic, non-therapeutic, pre-device, and pre-certification.
Why it matters
Sal-Meter is the path where the CCF / CAIS architecture is pressured into measurable reality. It is an execution path, not a slogan.
Browse by document interest / 관심 문서별로 보기
What it is
Start here for the definitional anchor and the first clear answer to “what is Sal-Meter?”
What it is not
Start here for prohibited substitutions, closed-score exclusions, proxy confusion, and naming drift prevention.
What is open now
Start here to avoid confusing future broader opening with present scoped readiness.
Where core contributors enter
Start here for kernel-program helper docs, current routes, technical issue orientation, and ESL / EStL pathway.
Next pages / 다음에 이어서 볼 페이지
Status
Best next page for readers who need the present program posture: what is open now, what is readiness only, and what remains downstream.
Sal-Meter Kernel v0.1.0
Best next route for labs, counsel, advisors, PM/COO candidates, and technical candidates who need execution boundaries before discussion.
For PIs
Entry page for principal investigators, laboratories, technical contributors, and readiness-oriented external groups.
Sal-Meter Kernel GitHub
Public helper repository for core program orientation, ESL / EStL routing, Layer-0 context, and technical issue coordination.
Human-State AI
Entry page for biosignal engineers, ML/data builders, metadata owners, dashboard builders, and human-session operators.
Canonical boundary documents / 정본 경계 문서
Do not say / 금지 표현
Certified Sal-Meter
Certification requires formal recognition under the proper conformance and mark-usage pathway.
Validated Sal-Meter
Current work is research-stage and pre-opening.
CAIS-compliant device
Compliance language is reserved and controlled by canonical records.
Proxy stack as Sal-Meter
Proxy benchmark infrastructure is not the Sal-Meter core molecular–electrochemical signal track.
v0.1.0 as validation
v0.1.0 is a public helper pre-release, not Sal-Meter validation, CAIS compliance, certification, or public competition opening.
v0.1.1 as validation
v0.1.1 is a public helper pre-release, not benchmark validation or Sal-Meter validation.
GitHub as authority
GitHub is a helper surface. DOI and OSF records define authority.
Raw human data release
Public GitHub and public OSF helper surfaces must not publish raw human data.