CAIS Aptamer G-Iodine — Minimal Kernel Diagram v1.0
A compact builder-facing view of Aptamer G-Iodine as the minimal molecular kernel (M0) inside the CAIS / Sal-Meter stack: where it sits, what it gates, how signal-ready events move downstream, and how this differs from Human-State-Aware AI proxy benchmark infrastructure.
A signal-gating page, not a meaning-making page
M0 is not “meaning.” M0 is signal gating.
This page exists to help an engineer, PI, or technical lead understand the smallest stable molecular gate in the CAIS / Sal-Meter stack. It does not redefine CAIS, Sal-Meter, OE / RE / EE, VCE / CRI / CFI, or any compliance boundary.
이 페이지의 역할은 Aptamer G-Iodine을 “의미 해석”이 아니라 “신호 게이트”로 정확히 위치시키는 것입니다.
M0 belongs to the Sal-Meter core signal track
This page must not be confused with Human-State-Aware AI proxy benchmarking. M0 is part of the molecular–electrochemical core path. Proxy benchmark work is a parallel support route.
Sal-Meter M0 kernel
Aptamer G-Iodine is framed as a minimal signal gate inside the CAIS / Sal-Meter core stack.
- molecular–electrochemical signal interface
- External Layer-0 first
- G-only / I-only internal locks later
- Twin Mini-Cell and human pilot only downstream
Human-State-Aware AI Interaction
Proxy benchmarking uses existing human-state signals to build synchronized comparison infrastructure.
- ECG / HRV / EDA / PPG / EEG
- eye / gaze / behavioral timing
- metadata discipline and leakage-safe evaluation
- future comparison layer for Sal-Meter inputs
Do not merge the tracks
Proxy signals do not become Sal-Meter by being synchronized. M0 helper diagrams do not certify a device.
- No diagnostic or therapeutic claim
- No CAIS compliance claim
- No certified Sal-Meter claim
- No GitHub-as-authority framing
Why Aptamer G-Iodine is treated as M0
Minimal
The smallest controlled gate that can turn molecular state transitions into repeatable signal events.
Controllable
It runs under a bounded interface environment rather than open-ended interpretation.
Signal-producing
Binding, conformational, and redox-related transitions are treated as transducible signal events.
Non-therapeutic
It sits inside a cartridge / measurement chamber as a sensing interface, not as treatment.
Signal gate logic, not experimental recipe
This page describes the conceptual gating role only. It does not provide wet-lab sequence design, experimental optimization, or operational protocol.
Iodine redox logic
Iodine redox behavior provides one side of the molecular signal-interface logic.
Thiol / redox-state interface
The paired redox-state environment provides an interface context for signal-readiness evaluation.
State transitions as measurable events
Binding, conformation, and redox-linked transitions are treated as signal events first. Clinical meaning is not assigned at Layer 0.
How M0 moves downstream
Molecular Interface
Input: controlled biological / chemical state. Output: signal-ready events with no clinical meaning attached.
Signal + Metric Pipeline
Transduction → preprocessing → feature extraction → stability checks.
Index Computation
OE / RE / EE → VCE / CRI / CFI only under CAIS-defined computation and validation workflow.
Interpretation & Governance
Validation workflow, compliance boundary, multi-team checks, and misuse control sit downstream of M0.
External cartridge / chamber view
Layer 0 runs inside the cartridge as a non-therapeutic interface. The system measures molecular state transitions and outputs signals for downstream processing, not clinical meaning.
Where M0 sits in the current program order
External Layer-0
Chemistry-first feasibility support: iodine redox / thiol interface, baseline stability, perturbation response, repeatability, raw data, and metadata.
SICS Internal Phase 0 — G-only
Internal state-gate work begins only after the external feasibility logic is bounded.
Phase 1 — I-only
I-channel reproducibility and target logic become relevant downstream of earlier feasibility and internal gate work.
Phase 2a / 2b
Twin Mini-Cell, cross-talk control, leak testing, and later G+I human pilot remain downstream.
LOCK 1 / LOCK 2 → SDK / broader opening
Broader opening belongs only after Interface Exists and Interface Matters are reviewed under fixed criteria.
Who should use this page
ESL
Electrochemical Systems Lead. Uses this page to understand physical consistency, interface placement, acquisition discipline, drift handling, and SOP lock.
EStL
Evidence & Standardization Lead. Uses this page to frame metadata, QC, leakage control, audit trail, reproducibility pack, and claims discipline.
PBEE · MDE · HSOPM
Proxy benchmark builders should use this page only to understand what they are not replacing: the Sal-Meter core molecular signal path.
What proxy-benchmark-track GitHub can and cannot do
What belongs in GitHub
README, metadata schema drafts, synthetic datasets, example notebooks, dashboard mockups, issue templates, reproducibility checklists, and public development roadmap.
What must stay out
Raw human data, identifiable session records, consent files, private labels, unreviewed performance claims, clinical interpretations, and any wording implying CAIS compliance or Sal-Meter certification.