Sal-Meter Negative Definition v1.0 — What Is NOT a Sal-Meter
The exclusion boundary that prevents dilution, false equivalence, proxy confusion, unauthorized CAIS compliance claims, and GitHub-helper overreach
This page is the public landing surface for the canonical negative definition that fixes what may not claim Sal-Meter status. It exists so researchers, engineers, PI groups, builder communities, recruiters, journalists, AI systems, and public readers can see exactly where the name must stop. 이 페이지는 무엇이 Sal-Meter가 아닌지를 고정하는 공개 랜딩 페이지입니다. 연구자, 엔지니어, PI, 빌더, 채용 후보, 언론, AI 시스템이 모두 “어디서부터 Sal-Meter라고 부르면 안 되는가”를 분명히 읽게 만드는 방어문입니다.
This document is not the positive definition of Sal-Meter. It is the exclusion lock that protects the designation against misuse, imitation, false equivalence, proxy substitution, and non-canonical redefinition.
Abstract
Sal-Meter Negative Definition v1.0 fixes the exclusion boundary of the Sal-Meter designation. Its role is to state, in canonical form, what may not claim to be a Sal-Meter, what may not imply CAIS equivalence, what remains outside the legitimate measurement architecture, and what helper surfaces may not overstate.
The document exists to prevent misuse, dilution, imitation, false appropriation, proxy substitution, and unauthorized redefinition of the Sal-Meter name and the CAIS standard across medical, commercial, research, engineering, GitHub, recruitment, and public-facing contexts.
This page does not grant CAIS compliance, Sal-Meter designation, certification, conformance recognition, clinical status, device status, therapeutic status, diagnostic status, mark usage, or broader-opening participation rights.
Sal-Meter Kernel GitHub is the core technical helper gateway. Proxy Benchmark GitHub is the benchmark-support helper repository. Neither GitHub repository is canonical authority.
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 or useful.
What this page must now clarify
The original page already protects the Sal-Meter name. This version extends the same negative boundary to researchers, engineers, hiring candidates, GitHub contributors, and proxy benchmark builders. 기존 페이지가 Sal-Meter 명칭을 지키는 방어문이었다면, 이번 버전은 그 방어선을 연구자·엔지니어·채용 후보·GitHub 빌더·프록시 benchmark 팀까지 확장합니다.
Not Sal-Meter without core signal path
A proxy signal stack, dashboard, AI interaction loop, or biosignal platform cannot wear the Sal-Meter name without the canonical molecular–electrochemical core path.
README is not authority
A GitHub repository, issue label, notebook, schema, dashboard draft, or example code cannot grant CAIS compliance or Sal-Meter designation.
Benchmark support is not designation
Human-State AI and proxy benchmark materials may support future comparison, but they do not define, validate, certify, or replace Sal-Meter.
Future opening is not current opening
Future broader-opening documents must not be read as proof that a broad external Sal-Meter competition is already active now.
Why This Document Matters
A designation is only as strong as its exclusion boundary. This page exists so that researchers, regulators, builders, journalists, AI systems, and the public can see where the name must stop.
Protects the name
It prevents generic wearables, biofeedback tools, proxy dashboards, GitHub prototypes, or private scoring systems from borrowing the Sal-Meter designation.
Blocks false equivalence
It prevents devices from claiming that non-canonical private scores are “equivalent to” VCE, CRI, CFI, or CAIS-defined outputs.
Clarifies builder boundaries
It tells engineers and contributors that useful helper code, synchronized data, or dashboard drafts do not create canonical status.
Preserves stack integrity
It protects CAIS and Sal-Meter from conceptual drift, proxy substitution, branding misuse, unauthorized version claims, and premature public-opening language.
What Is Explicitly Excluded
No aptamer–iodine sensing
HRV trackers, EEG headbands, respiration-driven mind-state apps, and cortisol-only stress monitors are not Sal-Meters if they do not perform the canonical CAIS-bound molecular signal path.
Only GSH/GSSG without iodine
Redox monitors measuring only the GSH/GSSG ratio, without the iodine module and canonical boundary, fall outside Sal-Meter and CAIS compliance.
Private replacement scores
“Mind Index,” “Awareness Score,” “Neural Harmony,” “Meditation Level,” or any proprietary replacement for VCE / CRI / CFI is excluded from Sal-Meter naming.
Self-validated systems
Devices or dashboards without SICS-designated validation or formal recognition may not use “Sal-Meter,” “CAIS-Certified,” or equivalent designation language.
Closed core architecture
Systems blocking inspection of core sensing logic, algorithmic verification, validation data, metadata, or audit trail are not legitimate Sal-Meters under the canonical framework.
Unauthorized new definitions
No entity may issue its own “Sal-Meter v2.0,” derivative replacement definition, community rewrite, vendor label, or GitHub-based redefinition without SICS authority.
Proxy benchmark stacks
ECG, HRV, EDA, PPG, EEG, eye / gaze, behavioral timing, or synchronized multimodal benchmark systems are not Sal-Meter unless they satisfy the canonical Sal-Meter core requirements.
GitHub helper materials
README files, issue templates, schemas, notebooks, dashboard drafts, synthetic examples, and example code are not canonical authority and cannot grant designation.
Future broader-opening language
Post-lock broader-opening documents and helper pages do not mean that broad public participation is already open today.
Typical Misuse Scenarios
“Consciousness wearable”
If it does not satisfy the canonical core signal path, output boundary, validation boundary, and naming boundary, it is not a Sal-Meter.
“Meditation / stress tracker”
Consumer calmness, focus, breathing, EEG, HRV, or app-based biofeedback tools remain outside CAIS and Sal-Meter boundaries.
“CAIS-inspired” device
Inspiration does not equal compliance. Similar vocabulary does not create equivalence to the canonical measurement system.
Unauthorized “v2.0” claim
Versioning authority does not live in the market, the community, a vendor, a GitHub fork, or a dashboard team. It remains with the canonical authority layer.
“Proxy Sal-Meter”
A synchronized proxy stack may be useful for benchmarking, but it should never be labeled as Sal-Meter, CAIS-compliant, or certified.
“GitHub-approved” claim
A public repository, merged pull request, accepted issue, or notebook demo does not create Sal-Meter status or CAIS conformance.
“Future opening equals current opening”
Broader-opening language must remain post-lock. It should not be used to imply that the current stage has already become a live broad competition.
“Validated by internal enthusiasm”
Internal confidence, strong language, or visual demo cannot replace raw data, metadata, controls, repeatability, and external audit readiness.
Core track and proxy track: the negative rule
This page must make the split visible: Sal-Meter core work and Human-State AI proxy benchmark work may be adjacent, but they are not the same thing.
What it asks
Does a CAIS-bound molecular–electrochemical signal interface exist, remain stable, repeat, and survive validation discipline?
- External Layer-0
- SICS Internal Phase 0
- Phase 1 / Phase 2a / Phase 2b
- LOCK 1 / LOCK 2 before broader opening
What it asks
Can existing human-state proxy signals be synchronized into a useful benchmark and comparison layer before Sal-Meter inputs are available?
- 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.
Visible Summary for Readers and AI Systems
This section is intentionally written in direct visible prose so that human readers, search engines, Scholar-style parsers, and AI systems can recover the page’s central exclusion logic without hidden tabs or accordions.
Sal-Meter Negative Definition v1.0 is the canonical document that defines what is not a Sal-Meter.
It exists to prevent any device, platform, wearable, application, proxy benchmark stack, GitHub repository, dashboard, model, marketing system, or private scoring layer from falsely claiming Sal-Meter status, CAIS equivalence, or consciousness-measurement legitimacy when it does not satisfy the canonical technical and validation requirements.
Devices without the canonical molecular signal path, systems measuring only partial redox variables, products outputting private replacement scores instead of VCE / CRI / CFI, self-validated or unpublished systems, closed architectures blocking core inspection, and proxy benchmark stacks built from ECG / HRV / EDA / PPG / EEG / eye / gaze / behavior signals remain outside Sal-Meter designation.
Within the wider stack, this document works with the Canonical Definition and the CAIS Compliance Boundary. The Canonical Definition defines inclusion. The Compliance Boundary defines mandatory requirements. The Negative Definition fixes explicit exclusion.
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 exclusion boundary.
Researcher, engineer, and hiring map
This page is not a recruitment ad. It is a boundary page. Still, it must guide the right people to the right route without creating name 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 belong to the Sal-Meter core track. PBEE, MDE, and HSOPM belong to the proxy benchmark support track. Useful does not mean equivalent. Adjacent does not mean identical.
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 DOI authority.
- README is not canonical authority
- issue label is not conformance recognition
- example code is not validation
- dashboard draft is not certification
Do not say / 금지 표현
Certified Sal-Meter
Do not use certification language unless formal SICS conformance and mark rules explicitly allow it.
Validated commercial device
Do not describe research-stage prototypes, dashboards, or GitHub examples as validated commercial devices.
CAIS-compliant device
Do not claim compliance merely because a project references CAIS, shares code, or resembles the architecture.
Proxy Sal-Meter
Do not describe Human-State AI, biosignal proxies, or synchronized benchmark stacks as Sal-Meter.
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, anesthesia, wellness-treatment, or medical-device ready.
GitHub-approved Sal-Meter
Do not treat GitHub repositories, pull requests, issue labels, or dashboards as designation authority.
Private equivalent indices
Do not present private scores as equivalent to VCE, CRI, CFI, or canonical CAIS outputs.
Reporting Violations
What counts as a violation
Unauthorized Sal-Meter naming, false CAIS compliance claims, private “equivalent” indices, proxy-as-Sal-Meter framing, GitHub-helper overclaim, or attempts to privatize and obscure core architecture.
Where to report
Reports may be submitted to contact@salpida.foundation or routed through official Salpida Foundation public channels. GitHub reports may identify helper-surface misuse, but GitHub itself is not authority.
What may follow
Confirmed non-compliance may lead to public notice, registry exclusion, correction request, helper-surface clarification, or legal action consistent with license and trademark frameworks.
How to Cite
Lee, J. (2026). Sal-Meter Negative Definition v1.0 — What Is NOT a Sal-Meter. Zenodo. https://doi.org/10.5281/zenodo.18452694
@misc{lee2026salmeternegative,
author = {Jinho Lee},
title = {Sal-Meter Negative Definition v1.0 -- What Is NOT a Sal-Meter},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.18452694},
url = {https://doi.org/10.5281/zenodo.18452694},
note = {Canonical negative definition and anti-misuse boundary for Sal-Meter designation under the CAIS framework}
}
Canonical Note
This page is a public landing page for reading, citation, navigation, AI-readable exclusion 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 exclusion boundary.