Non-Canonical Overview System Map Sal-Meter / CAIS Core Track + Proxy Boundary

Sal-Meter System Overview

A rapid overview of the Sal-Meter as a CAIS-aligned molecular–electrochemical measurement architecture: what it measures, how the stack is organized, how it differs from proxy benchmark systems, where researchers, engineers, PIs, and builders can enter, and which canonical records control designation, boundary, and interpretation.

This page is a rapid overview. It does not replace canonical definitions. Current execution order is External Layer-0 → SICS Internal Phase 0 (G-only) → Phase 1 (I-only) → Phase 2a (Twin Mini-Cell) → Phase 2b (G+I human pilot) → LOCK 1 / LOCK 2 → SDK / broader opening. All current work remains research-stage, non-diagnostic, non-therapeutic, non-clinical, and pre-device.
Authority rule: This overview is a public helper page. If this page, GitHub, a landing page, or a helper document conflicts with DOI / OSF canonical records, the canonical layer controls.
Figshare DOI Status For PIs CAIS Topic Sal-Meter Core Sal-Meter Kernel GitHub Human-State AI Proxy Benchmark GitHub Publications
Document Type
Non-canonical public technical helper / system overview
Audience
Readers, PIs, engineers, ESL / EStL candidates, proxy benchmark builders
Status
Research-stage · non-diagnostic · non-therapeutic · non-clinical · pre-device
Authority
Canonical authority remains fixed only in DOI / OSF records
Document identity

What this page does

This page gives a fast structural answer to four questions: What does the Sal-Meter measure? How is the stack organized? Where do researchers and engineers enter? and how does the Sal-Meter core track differ from the proxy benchmark track?

It is intentionally written as a public helper surface for readers, engineers, research leads, PIs, and hiring candidates. It does not fix naming authority, compliance interpretation, certification status, conformance status, mark usage, or canonical definitions. Those remain in the DOI / OSF canonical layer.

Modification logic

What this page must now clarify

Core track first

Sal-Meter is the core molecular–electrochemical signal path. The page must show External Layer-0, internal locking, Twin Mini-Cell, and LOCK 1 / LOCK 2 as the core execution logic.

Kernel GitHub added

Sal-Meter Kernel GitHub must appear as the core technical gateway for ESL / EStL, PIs, electrochemical systems contributors, and evidence-standardization readers.

Proxy track separated

Human-State-Aware AI and Proxy Benchmark GitHub must remain proxy benchmark support routes, not Sal-Meter core validation.

This page should not read like product validation, clinical readiness, live competition opening, or CAIS certification. It should read like a system map with locked routes and hard public-claims boundaries.
Core track vs proxy benchmark track

Two tracks must not be confused

The Sal-Meter core track asks whether a new molecular–electrochemical signal interface can exist. The Proxy Benchmark Track builds synchronized multimodal comparison infrastructure using existing human-state proxy signals.

Sal-Meter core signal track

  • Aptamer–iodine redox sensing
  • Iodine redox / thiol interface feasibility
  • G-only and I-only kernel locking
  • Twin Mini-Cell leak and cross-talk control
  • LOCK 1 / LOCK 2 before SDK or broader opening
Sal-Meter Topic Kernel GitHub

Proxy benchmark track

  • ECG, HRV, EDA, PPG, EEG, eye / gaze, and behavioral timing
  • Synchronized multimodal benchmark platform
  • Metadata discipline and leakage-safe evaluation
  • Baseline models, replayable notebooks, and local dashboards
  • Future comparison layer for Sal-Meter inputs
Human-State AI Proxy GitHub

Boundary rule

  • Proxy signals are not Sal-Meter
  • GitHub helper materials are not canonical authority
  • No diagnostic or therapeutic claim
  • No CAIS compliance or certification claim
  • No broad opening claim before LOCK 1 / LOCK 2
Status Declaration
Human-State-Aware AI Interaction is a proxy benchmark support track. It does not replace the Sal-Meter core signal track and does not grant CAIS compliance, certification, mark usage, device status, clinical authority, diagnostic authority, or therapeutic authority.
Core measurement axes

OE · RE · EE

OE

Ordered Energy

Structural coherence, alignment, and informational order within conscious-state processes.

RE

Relational Energy

Interconnection quality, synchrony, and resonance between conscious entities or systems.

EE

Entropic Energy

Disorder, instability, dispersion, and entropy dynamics within consciousness-related systems.

Output indices

VCE · CRI · CFI

VCE

Vibrational Consciousness Energy

Individual-level alignment and dynamical pattern output.

CRI

Consciousness Resonance Index

Relational and group-level synchrony across interacting systems.

CFI

Conscious Field Index

Large-scale social, institutional, and civilizational coherence representation.

System architecture

From molecular interface to readable output

1

Aptamer G-Iodine molecular sensor

Signal-facing molecular interface operating as a non-therapeutic sensing kernel.

2

Electrochemical transduction layer

State-linked molecular events are converted into measurable electrochemical signal events.

3

CAIS signal processing

Preprocessing, extraction, normalization, and OE / RE / EE feature construction under fixed evidence rules.

4

Interpretation engine

CAIS-defined computation of VCE, CRI, and CFI under compliance and terminology constraints.

5

App / dashboard layer

Human-readable display, comparison, logging, and downstream research interfaces.

Measurement architecture only. This page does not create diagnostic, therapeutic, certification, mark usage, or commercial-device claims.
Use-case structure

Where this overview places the system

Non-clinical human-state interaction research

  • Research-stage observation of state-linked signal patterns
  • Non-clinical interaction and feedback-loop prototypes
  • Longitudinal research logs under consent and metadata discipline
  • No diagnosis, therapy, treatment, or medical interpretation

Research

  • Consciousness science hypothesis testing
  • Exploratory validation across controlled state transitions
  • Signal separation and reproducibility studies
  • Cross-lab protocol development

Future downstream layers

  • AI alignment and governance analytics
  • Aggregate civilizational-scale coherence observation
  • Institutional dashboards under separate validation paths
  • Any applied medical path only through separate evidence and regulatory routes
Execution logic

Current program order

1

External Layer-0

Gold-electrode iodine redox / thiol interface feasibility. This is chemistry-first external feasibility support, not Internal Phase 0.

2

SICS Internal Phase 0 — G-only

Internal state-gate work focused on the G channel, baseline rule, acquisition discipline, and repeated directional persistence.

3

Phase 1 — I-only

I-channel reproducibility lock with I₃⁻ target logic and I⁻ calibration discipline.

4

Phase 2a — Twin Mini-Cell

G and I channel coexistence, cross-talk control, structural separation, and leak testing.

5

Phase 2b — G+I human pilot

Human pilot under fixed package architecture, repeated state separation, replayable metadata, and locked data discipline.

6

LOCK 1 / LOCK 2

LOCK 1 asks whether the interface exists. LOCK 2 asks whether the interface matters. SDK release and broader opening belong after these locks.

The Proxy Benchmark Track runs in parallel as a support and comparison layer. It does not count as External Layer-0, Internal Phase 0, Phase 1, Phase 2a, Phase 2b, LOCK 1, or LOCK 2.
Researcher / engineer / hiring route

Who should use this overview

This overview is also a routing page for researchers, engineers, technical contributors, and hiring candidates who need to understand where they fit.

ESL

Electrochemical Systems Lead. Owns physical consistency: electrode behavior, chamber logic, drift handling, acquisition reliability, cleaning discipline, and SOP lock.

EStL

Evidence & Standardization Lead. Owns evidence consistency: metadata, QC, leakage prevention, holdout design, audit trail, and reproducibility package.

PBEE / MDE

Proxy benchmark builders. Build biosignal capture, edge inference, dataset schema, labels, holdout logic, baseline models, and dashboards.

HSOPM

Human-session operations. Manages consent path, participant flow, session timing, metadata completion, and raw-data governance.

Core candidates should enter through Status → For PIs → Sal-Meter Topic → Sal-Meter Kernel GitHub. Proxy candidates should enter through Status → Human-State AI → Proxy Benchmark GitHub.
GitHub route separation

GitHub helps builders, but does not create authority

Sal-Meter Kernel GitHub

Core technical gateway for the kernel-first Sal-Meter / CAIS program. Use this for core-track orientation, ESL / EStL routing, Layer-0 context, 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
Open Kernel GitHub

Proxy Benchmark GitHub

Technical helper repository for schemas, synthetic examples, notebooks, dashboard drafts, issue templates, reproducibility checklists, and builder coordination.

  • Metadata schema drafts
  • Synthetic / sample data
  • Notebooks and dashboard drafts
  • No raw human data
  • Not Sal-Meter
Open Proxy GitHub

Canonical Index GitHub

Public DOI routing and repository index helper. It helps users find canonical records, but it does not replace Zenodo or OSF authority.

  • DOI routing
  • Document family map
  • Index helper
  • Not research execution
  • Not certification surface
Open Canonical Index
GitHub helps builders. DOI / OSF records define authority. Foundation pages route readers. No GitHub README, issue, notebook, schema, dashboard draft, or public example grants Sal-Meter designation, CAIS compliance, certification, conformance, clinical authority, or mark usage.
Navigation

Read quickly, then go deeper

Start here for the overview. Move next to Status if current opening and boundary are the question, to For PIs if participation is the question, to CAIS Topic if the architecture is the question, to Sal-Meter Kernel GitHub if core technical contribution is the question, to Human-State-Aware AI Interaction if proxy benchmark infrastructure is the question, and to the DOI / OSF layer if naming, compliance, or canonical interpretation is the question.

Status For PIs PI Quick Decision Pack Technical Snapshot CAIS Topic Sal-Meter Topic Sal-Meter Kernel GitHub Human-State AI Proxy Benchmark GitHub Publications
Final boundary: this overview is a non-canonical helper surface. It does not grant CAIS compliance, Sal-Meter designation, certification status, conformance status, mark usage, publication authorization, clinical authority, diagnostic authority, therapeutic authority, or device status. Proxy benchmark materials support future comparison and builder coordination; they do not substitute for the Sal-Meter molecular–electrochemical core signal track. Sal-Meter Kernel GitHub and Proxy Benchmark GitHub are helper surfaces only.