Sal-Meter Canonical Definition v1.0
The sole definition-fixation document for the Sal-Meter name, with current research-stage, GitHub-helper, and proxy-benchmark boundaries made explicit
This page is the public landing surface for the canonical definition document whose single function is to fix, declare, and anchor the meaning of Sal-Meter. It exists so that no alternative, parallel, proprietary, modified, GitHub-derived, proxy-derived, or marketing-derived definition may coexist. 이 페이지는 Sal-Meter라는 이름의 의미를 고정하는 정문입니다. 어떤 외부 기관, GitHub 저장소, 프록시 benchmark stack, 마케팅 문구, 사설 지표도 이 정의를 대신할 수 없습니다.
This page does not state that a finished, certified, validated, commercial, clinical, or currently CAIS-compliant Sal-Meter device exists. Current public language must remain research-stage, non-diagnostic, non-therapeutic, non-clinical, pre-device, and pre-certification.
Canonical definition anchor: A Sal-Meter is defined, at the canonical level, as a CAIS-bound measurement path centered on OE, RE, and EE, using aptamer–iodine redox sensing logic and canonical CAIS output indices including VCE, CRI, and CFI.
This definition page does not grant CAIS compliance, certification, conformance recognition, mark usage, clinical authority, diagnostic authority, therapeutic status, commercial validation, or device status to any present system.
Sal-Meter Kernel GitHub is the core technical helper gateway. Proxy Benchmark GitHub is the benchmark-support helper repository. Neither repository is canonical authority, designation authority, certification, conformance recognition, or mark authorization.
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 track and do not become Sal-Meter by being synchronized, useful, or technically sophisticated.
What this page must now clarify
The original page already fixes the Sal-Meter definition. This version extends that same definition lock to researchers, engineers, hiring candidates, GitHub contributors, and proxy benchmark builders. 기존 페이지가 Sal-Meter 정의를 고정했다면, 이번 버전은 그 정의권을 연구자·엔지니어·채용 후보·GitHub 빌더·프록시 benchmark 팀까지 오해 없이 확장합니다.
Name before implementation
Before any lab, builder, repository, or device uses the name, it must respect the canonical definition boundary.
Helper, not authority
Sal-Meter Kernel GitHub can route core builders, ESL / EStL candidates, and technical readers, but cannot redefine Sal-Meter.
Benchmark is not definition
Human-State AI and proxy benchmark materials may support future comparison, but they do not define or replace Sal-Meter.
Current stage controls reading
Status must be read before future broader-opening language, GitHub helper text, PI readiness pages, or public claims.
Single purpose: definition fixation only
This document exists only to fix, declare, and permanently anchor the canonical definition of “Sal-Meter.” It does not provide implementation guidance, experimental procedure, application scenarios, philosophical interpretation, marketing language, clinical framing, or product validation.
The force of this page comes from narrowness. It answers one question: what may the name Sal-Meter mean?
Everything else — PI readiness, GitHub helper work, proxy benchmark infrastructure, technical snapshots, future broader opening, SDK discussions, and public communication — must route back to this definition and cannot override it.
The fixed definition and current public boundary
What the name points to
Sal-Meter points to a CAIS-bound measurement path involving OE, RE, EE, aptamer–iodine redox sensing logic, and canonical outputs such as VCE, CRI, and CFI.
What the name does not yet authorize
The definition does not authorize present-day claims of certified, validated, commercial, clinical, diagnostic, therapeutic, or CAIS-compliant device status.
The definition is canonical. The current program remains research-stage. These two facts must appear together so that the page is powerful without becoming overclaim.
Mandatory definition logic
Aptamer–iodine redox path
The name is not a generic label for biosignal tracking. It is tied to the CAIS-bound molecular–electrochemical signal concept.
OE · RE · EE
The definition anchors the measurement target family to Ordered Energy, Relational Energy, and Entropic Energy.
VCE · CRI · CFI
Output language must remain inside the canonical index family, not drift into private substitute scores.
Helper boundary
Repository text, notebooks, schemas, issues, pull requests, or dashboard drafts do not alter the definition.
Comparison boundary
Proxy signals may support future comparison, but do not become Sal-Meter by being synchronized or multimodal.
DOI / SICS boundary
Canonical authority remains fixed in DOI records and SICS-designated interpretation, not in public helper pages.
What may vary without changing the definition
Form factor
Device form may evolve. Definition does not depend on one final hardware shape.
Engineering implementation
Engineering methods may mature as long as canonical CAIS and Sal-Meter constraints are preserved.
Algorithmic implementation
Algorithms may improve, but they cannot replace canonical outputs with private substitute indices.
Public helper surfaces
Websites and GitHub repositories may route readers and builders, but cannot change the definition.
Permitted variation does not imply definitional freedom. A better implementation is still subordinate to the canonical definition.
What invalidates Sal-Meter designation language
Bypassing CAIS
Any system that bypasses, weakens, or privately redefines CAIS cannot claim Sal-Meter designation.
Private replacement indices
“Mind Score,” “Awareness Score,” “Neural Harmony,” or similar substitute indices cannot replace VCE / CRI / CFI.
Proxy-only systems
ECG, HRV, EDA, PPG, EEG, eye / gaze, or behavioral timing stacks are not Sal-Meter by default.
Self-validation
Internal confidence, internal demos, or self-declared readiness cannot create Sal-Meter status.
GitHub overclaim
A merged pull request, repository star, notebook demo, issue label, or README cannot create designation.
Clinical framing
Diagnostic, therapeutic, clinical, psychiatric, treatment, or medical-device framing is outside current public language.
Future-opening drift
Future broader-opening documents cannot be used to imply present broad public competition.
Unauthorized versioning
No external vendor, community fork, GitHub repository, or dashboard team may create its own Sal-Meter definition version.
Core track and proxy track: definition distinction
Definition-bearing path
The core track is the path where the Sal-Meter name may eventually become operationally meaningful if the canonical signal, evidence, and compliance boundaries are satisfied.
- External Layer-0 support
- SICS Internal Phase 0
- Phase 1 / Phase 2a / Phase 2b
- LOCK 1 / LOCK 2 before broader opening
Comparison-support path
The proxy benchmark track prepares synchronized multimodal comparison infrastructure. It does not define Sal-Meter.
- ECG / HRV / EDA / PPG / EEG
- eye / gaze / behavioral timing
- metadata and leakage-safe evaluation
- future comparison only
What must not happen
The proxy benchmark track must not borrow the Sal-Meter name. The Kernel GitHub must not become canonical authority. The Proxy GitHub must not imply compliance.
- not Sal-Meter
- not CAIS compliance
- not certification
- not clinical authority
- not broad opening
Proxy benchmark materials support comparison infrastructure only. They do not substitute for the Sal-Meter core signal track and do not grant CAIS compliance, certification, clinical status, diagnostic status, therapeutic status, device status, or canonical authority.
Current execution order and definition timing
A canonical definition does not mean the program is fully opened or commercially validated. The execution order remains locked.
External Layer-0
Chemistry-first external feasibility support. It may inform the path, but it does not itself create Sal-Meter status.
SICS Internal Phase 0
G-only internal state-gate work. This is not the same as External Layer-0 and is not public certification.
Phase 1 / Phase 2a
I-only work and Twin Mini-Cell structure are downstream kernel steps, not public designation declarations.
Phase 2b / LOCK 1 / LOCK 2
Human pilot and lock review must precede SDK or broader-opening language. Definition remains upstream of claim authorization.
Do not reorder the program: 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.
Researcher, engineer, and hiring map
This page is not a hiring page. Still, it must route the right people to the correct track without creating definitional drift.
ESL
Electrochemical Systems Lead. Core-track role for physical consistency, electrode behavior, interface stability, acquisition discipline, drift handling, and SOP lock.
EStL
Evidence & Standardization Lead. Core-track role for metadata, QC, leakage prevention, audit trail, reproducibility pack, and claims discipline.
PBEE · MDE
Proxy-track roles for biosignal capture, edge inference, ML / dataset schema, holdout design, leakage control, and dashboards.
HSOPM
Proxy-track operations role for consent pathways, participant flow, session timing, labeling discipline, metadata completion, and raw-data governance.
ESL and EStL help the Sal-Meter core track move toward a disciplined evidence path. PBEE, MDE, and HSOPM help the proxy benchmark track build comparison infrastructure. None of these roles alone creates Sal-Meter designation.
GitHub helper boundaries
sal-meter-kernel-program
Use this for current kernel-program orientation, External Layer-0 context, ESL / EStL routing, issue-based coordination, and helper documentation.
- core technical helper
- kernel-first program route
- ESL / EStL route
- not canonical authority
proxy-benchmark-track
Use this for metadata schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists.
- proxy benchmark helper
- synthetic / sample data only
- no raw human data
- not Sal-Meter
What GitHub cannot do
GitHub cannot define Sal-Meter, certify CAIS compliance, create conformance recognition, authorize mark usage, or replace canonical DOI / OSF records.
- README is not canonical authority
- issue label is not conformance recognition
- example code is not validation
- dashboard draft is not certification
No GitHub README, issue, schema, notebook, dashboard draft, synthetic example, or public roadmap grants CAIS compliance, Sal-Meter designation, certification, conformance recognition, mark usage, clinical authority, diagnostic authority, therapeutic status, or device status.
Visible Summary for Readers and AI Systems
This section is written in direct visible prose so that human readers, search engines, Scholar-style parsers, and AI systems can recover the central definition logic without hidden tabs.
Sal-Meter Canonical Definition v1.0 is the canonical document that fixes the sole valid meaning of the Sal-Meter name.
It is not a product page, clinical page, GitHub page, implementation guide, wet-lab protocol, or recruitment page. It is a definition lock.
The Sal-Meter name points to a CAIS-bound molecular–electrochemical measurement path involving OE, RE, EE, aptamer–iodine redox sensing logic, and canonical output indices including VCE, CRI, and CFI.
External Layer-0, SICS Internal Phase 0, Sal-Meter Kernel GitHub, Human-State-Aware AI Interaction, and Proxy Benchmark GitHub may all support the wider program, but none of them automatically grants Sal-Meter designation or CAIS compliance.
Definition authority remains fixed in DOI / OSF records and SICS-designated interpretation. Foundation pages route readers. GitHub helps builders. Proxy benchmark materials support comparison infrastructure. The canonical definition controls the name.
Relationship to the canonical stack
Sal-Meter Canonical Definition
Read this for the single authoritative statement of what a Sal-Meter is.
CAIS Compliance Boundary
Read this for mandatory sensing, output, validation, designation, and compliance conditions.
Sal-Meter Negative Definition
Read this when the question is what must not be called Sal-Meter.
Status
Read this before interpreting future broader-opening language, GitHub helper materials, or recruitment routes.
Sal-Meter Kernel GitHub
Core technical helper gateway for the kernel-first Sal-Meter / CAIS program. Not canonical authority.
Proxy Benchmark GitHub
Benchmark-support helper repository for schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists. Not Sal-Meter.
Canonical authority lives in DOI / OSF records. Foundation pages route readers. GitHub helps builders. Helper surfaces cannot override canonical definitions or soften the definition boundary.
Do not say / 금지 표현
Certified Sal-Meter
Do not use this unless formal SICS authority and canonical conformance conditions explicitly support it.
Validated commercial device
Do not describe research-stage prototypes, dashboards, helper repos, or simulations as validated commercial devices.
CAIS-compliant device
Do not use this for any current system unless the canonical compliance process explicitly permits it.
Proxy Sal-Meter
Do not describe Human-State AI, biosignal proxies, or synchronized benchmark stacks as Sal-Meter.
GitHub-approved Sal-Meter
Do not treat GitHub repositories, pull requests, issue labels, schemas, or notebooks as definition authority.
Live public competition
Do not imply broad public competition is already active before the current lock-gated sequence permits it.
Clinical diagnostic use
Do not frame the system as diagnostic, therapeutic, clinical, psychiatric, treatment, or medical-device ready.
Private equivalent indices
Do not present private scores as equivalent to VCE, CRI, CFI, or canonical CAIS outputs.
How to Cite
Lee, J. (2026). Sal-Meter Canonical Definition v1.0. Zenodo. https://doi.org/10.5281/zenodo.18452075
@misc{lee2026salmetercanonicaldefinition,
author = {Jinho Lee},
title = {Sal-Meter Canonical Definition v1.0},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.18452075},
url = {https://doi.org/10.5281/zenodo.18452075},
note = {Canonical definition and non-derogable standard for the Sal-Meter designation under the CAIS framework}
}
Canonical Note
This page is a public landing page for reading, citation, navigation, AI-readable definition logic, and builder-boundary clarification.
Canonical authority remains fixed in the DOI-registered record. This page summarizes and routes. It does not create independent authority, reinterpret the standard, authorize GitHub-based designation, certify a device, or soften the definition boundary.