PI Readiness · Kernel-First · Pre-Opening · Research-Stage

Sal-Meter Kernel Program & Future Broader Opening

PI Readiness Edition v1.2 커널 프로그램의 현재 위치, 연구실 준비 경로, GitHub helper 상태, OSF routing, future broader opening의 순서를 한 화면에서 고정합니다.

DOI authority fixed · GitHub helper only

This page is the public PI-facing readiness surface for the Sal-Meter / CAIS kernel program. It clarifies what is active now, what remains downstream, and how serious laboratories, PIs, engineers, and technical candidates should read the current research-stage program.

The central rule is simple: kernel first, reproducibility first, pre-opening first. Broader opening belongs after the technical and validation locks, not before them.

Current language lock. This is not a broad external competition announcement. This is not a consumer device page. This is not a clinical, diagnostic, therapeutic, certified-device, or mark-usage page. It is a research-stage · pre-opening · PI readiness edition.

Document: Sal-Meter Kernel Program & Future Broader Opening — PI Readiness Edition v1.2
Page Role: PI / laboratory readiness route
Version DOI: 10.5281/zenodo.19509841
Concept DOI: 10.5281/zenodo.18645699
Program Status: research-stage · pre-opening · kernel-first
Snapshot Alignment: 2026-05-08 public helper status
Core Track: Sal-Meter / CAIS molecular–electrochemical signal path
Proxy Track: Human-State-Aware AI benchmark support path

Boundary: DOI / OSF records remain the authority layer. The Foundation website explains and routes. GitHub helps builders. GitHub does not create canonical authority, does not validate Sal-Meter, does not grant CAIS compliance, and does not certify any system.

한국 연구자용 빠른 판정

지금은 “열린 공모전”이 아니라 “커널을 잠그는 준비 단계”입니다

이 페이지를 보는 국내 연구자, PI, 전기화학팀, 압타머팀, 신호처리팀, 데이터 표준화팀이 가장 먼저 잡아야 할 것은 지금 무엇을 할 수 있는가입니다.

지금의 올바른 행동은 참여 선언보다 먼저, 장비 적합성, 인력 적합성, SOP 가능성, 데이터 무결성, 경계 언어, DOI 문서 숙지, 그리고 어느 layer를 맡을 수 있는지의 냉정한 판단입니다.

과학은 큰 문으로 들어오지 않습니다. 먼저 작은 신호가 흔들리지 않는지 확인하고, 그 다음에야 문을 넓힙니다.
Current status lock

What is open now, and what is not open now

Open now

Scoped readiness

Serious teams may review fit, read the DOI stack, assess equipment and personnel, and prepare for scoped discussion.

  • PI / lab readiness review
  • External Layer-0 feasibility discussion
  • I₃⁻ aptamer development support inquiry
  • ESL / EStL candidate identification
  • Human-State-Aware AI proxy benchmark preparation
Not open now

No broad competition yet

Public language must not imply that a mass external competition, consumer launch, certification pathway, or validated device program is active now.

  • no live broad public competition
  • no consumer device claim
  • no clinical or diagnostic use
  • no therapeutic platform claim
  • no CAIS-compliant device claim
Public helper surfaces

Useful, but not sovereign

Website pages, GitHub repositories, OSF routing files, and helper documents support orientation. They do not replace canonical DOI authority.

  • Foundation website explains
  • OSF routes
  • GitHub helps
  • Zenodo / DOI records govern
Fixed execution order

The sequence must not be collapsed

The current program sequence must be read as a locked order: external feasibility first, internal kernel locking second, broader opening only after the locks.

1Layer-0
2Phase 0
3Phase 1
4Phase 2a
5Phase 2b
6LOCK 1/2
7Post-lock
1

External Layer-0

Signal feasibility before device language

Gold-electrode iodine redox and thiol-linked electrochemical feasibility. This stage asks whether the signal interface survives at all.

2

SICS Internal Phase 0

G-only first-stage state gate

G-only state-separability testing under fixed baseline, SOP, metadata, and evidence discipline.

3

Phase 1

I-only reproducibility

I-channel fixation and single-channel stability confirmation before twin-channel interpretation.

4

Phase 2a

Twin Mini-Cell structure

Twin Mini-Cell architecture, G/I separation logic, and cross-talk control.

5

Phase 2b

G + I human pilot

Human pilot sessions under fixed package architecture, QC discipline, and evidence review.

6

LOCK 1 / LOCK 2

Claims wait for locks

LOCK 1 means Interface Exists. LOCK 2 means Interface Matters. No broad claim comes before this gate.

7

Post-lock Opening

Only after technical justification

SDK, broader participation, and expanded competition architecture belong only after LOCK 1 / LOCK 2.

Do not compress the order. External Layer-0 is not Internal Phase 0. Proxy benchmark preparation is not Sal-Meter validation. A helper release is not benchmark validation. A future broader opening charter is not a present-tense public competition.

GitHub v0.1.1 alignment

Proxy Benchmark GitHub v0.1.1 must be treated as helper-structure validation only

The current proxy-benchmark-track release should be described with one fixed sentence:

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.
What it is

Public helper pre-release

Repository hygiene, schemas, synthetic examples, helper routing, and public structure validation.

What it is not

No validation crown

It does not validate benchmark performance, scientific truth, Sal-Meter, CAIS compliance, or certification.

Data boundary

Synthetic / sample only

It contains no raw human data, no identifiable data, no clinical data, no Sal-Meter input, and no CAIS-compliant measurement data.

OSF P alignment

OSF is the public research hub, not the authority layer

The OSF project should be understood as 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.

Two-track clarity

Sal-Meter Core Track and Proxy Benchmark Track must stay separate

PI Readiness must show both tracks, but never merge them. One is the core signal-interface path. The other is the synchronized benchmark support path.

Core Track

Sal-Meter / CAIS molecular–electrochemical signal path

The core track asks whether a new CAIS-aligned molecular–electrochemical signal interface can produce stable, repeatable, auditable signal behavior under bounded research conditions.

  • External Layer-0 iodine redox / thiol feasibility
  • I₃⁻ aptamer development support inquiry
  • SICS Internal Phase 0 G-only state gate
  • Phase 1 I-only reproducibility
  • Phase 2a Twin Mini-Cell
  • Phase 2b G+I human pilot
  • LOCK 1 / LOCK 2 before SDK or broader opening
Proxy Track

Human-State-Aware AI benchmark support path

The proxy track builds synchronized multimodal benchmark infrastructure using existing proxy signals before Sal-Meter inputs are available.

  • ECG / HRV / EDA / PPG
  • optional EEG
  • eye / gaze / behavioral timing
  • feedback event logs
  • session labels and metadata
  • leakage-safe evaluation planning
  • future comparison with Sal-Meter I/G-channel inputs

Fixed distinction: Core Track = signal existence and repeatability. Proxy Track = synchronized benchmark and comparison infrastructure. The proxy stack is not Sal-Meter.

What a serious lab can do now

Practical readiness actions

1

Read the boundary stack

Canonical Definition, Compliance Boundary, Negative Definition, Claims Control, Certification / Mark Policy, Conformance Suite.

2

Choose one layer

Layer-0 chemistry, aptamer, electrode/device, signal processing, evidence package, or proxy benchmark support.

3

Map equipment and personnel

Potentiostat, gold electrode setup, wet-lab handling, SOP capacity, metadata discipline, IRB awareness if human samples later appear.

4

Prepare without overclaiming

Use readiness language only. Do not imply validation, certification, clinical status, or active broad public competition.

Internal lead structure

Two-lead architecture: one locks measurement, one locks evidence

For the current program, ESL / EStL is clearer than vague operational titles. The project needs one person to prevent physical signal drift, and another to prevent evidence drift.

ESL

Electrochemical Systems Lead

Owns the physical measurement consistency layer.

  • electrode / cartridge / chamber logic
  • potentiostat and measurement sequence
  • drift, repeatability, and SOP stability
  • Layer-0 feasibility coordination
  • signal survival before interpretation
EStL

Evidence & Standardization Lead

Owns the evidence consistency and submission architecture layer.

  • raw data / metadata package rules
  • QC and leakage control
  • holdout / split discipline
  • versioned schema and audit logs
  • standardization before public claims

한국어 핵심: “누가 실험을 굴리는가”와 “누가 증거를 잠그는가”는 분리되어야 합니다. 이 둘이 분리되지 않으면 빠르게 달릴 수는 있어도, 증명 단계에서 무너집니다.

Read together

Documents that must be read together

Canonical Core

Sal-Meter Canonical Definition

Fixes what Sal-Meter means and prevents loose substitution.

Boundary

CAIS Compliance Boundary

Fixes what may legitimately count as CAIS compliance or Sal-Meter designation.

Negative Definition

Sal-Meter Negative Definition

Fixes what is not Sal-Meter, including proxy-only and non-molecular substitutes.

Governance

Future Broader Opening Charter

Explains post-lock broader opening logic without making it present-tense.

Implementation Bridge

From Theory to Implementation

Connects the philosophical architecture to proof-of-concept and infrastructure.

Builder Route

GitHub Helper Surfaces

Routes builders into the current technical helper repositories without granting authority.

Public language rule

Use these words. Avoid these words.

Use

Safe public language

  • research-stage
  • pre-opening
  • kernel program
  • future broader opening
  • External Layer-0 feasibility
  • PI / laboratory readiness
  • non-clinical
  • non-diagnostic
  • non-therapeutic
  • pre-device
  • pre-certification
  • GitHub helper surface
  • DOI authority layer
Avoid

Unsafe or premature language

  • already-open full competition
  • validated Sal-Meter
  • certified Sal-Meter
  • CAIS-compliant device
  • clinical consciousness diagnosis
  • therapeutic feedback system
  • consumer device launch
  • proxy stack as Sal-Meter
  • v0.1.1 as benchmark validation
  • raw human data public release
  • GitHub as canonical authority
  • private replacement indices
Final position

This page is a gate, not a crown

PI Readiness Edition does not ask laboratories to pretend certainty where certainty does not yet exist. It asks something more valuable: understand the current stage correctly, prepare seriously, and respect the order by which a fragile idea becomes an experimental structure.

In the event of any perceived inconsistency between this page and a DOI-registered canonical record, the DOI-registered canonical record prevails. This page is public, useful, readable, and intentionally practical. It is not sovereign.

Final boundary: No page, repository, helper document, public post, release note, OSF route, or website landing page grants CAIS compliance, Sal-Meter designation, certification, mark usage, benchmark validation, clinical authority, diagnostic authority, therapeutic authority, or human-ranking authority.