Non-Canonical Technical Helper Structural Snapshot Engineers · PIs · Technical Leads · Builders

CAIS Architecture & Sal-Meter Technical Snapshot

A fast technical view of the buildable CAIS / Sal-Meter stack: layer separation, current execution order, minimal implementation flow, canonical DOI map, engineering checklist, hiring-role map, and builder routes for both the Sal-Meter core signal track and the Human-State-Aware AI proxy benchmark track.

Current public execution order: 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 review → post-lock SDK and broader opening. This page is research-stage, non-diagnostic, non-therapeutic, non-clinical, and pre-device.
Authority rule: This page is a public technical compression. It does not redefine CAIS, Sal-Meter, OE / RE / EE, VCE / CRI / CFI, certification, conformance, or publication boundaries. Canonical authority remains fixed only in DOI / OSF records.
Figshare DOI Status For PIs PI Quick Decision Pack System Overview CAIS Topic Sal-Meter Core Sal-Meter Kernel GitHub Human-State AI Proxy Benchmark GitHub Publications
Document Type
Non-canonical technical helper / structural snapshot
Audience
Engineers, PIs, technical leads, ESL / EStL, PBEE, MDE, HSOPM
Public Status
Research-stage · non-diagnostic · non-therapeutic · non-clinical · pre-device
Authority
Canonical authority remains fixed only in DOI / OSF records
Document role

What this page is for

This page answers one concrete builder question: How can a serious technical team understand the CAIS / Sal-Meter stack without mistaking helper language for canonical authority?

It is a compressed technical landing page for the current CAIS / Sal-Meter build path. It helps engineers, PIs, technical leads, and candidate roles understand the architecture, but it does not create new naming authority, statistical authority, compliance authority, certification status, publication authorization, or clinical authority.

Modification logic

What this page must now clarify

Core technical gateway

Add Sal-Meter Kernel GitHub as the primary GitHub route for Sal-Meter / CAIS core-track builders, ESL / EStL candidates, PIs, and electrochemical systems contributors.

Proxy benchmark gateway

Keep Human-State-Aware AI and Proxy Benchmark GitHub as synchronized multimodal benchmark-support routes, not as Sal-Meter core validation.

Status-first routing

Technical readers must check Status before interpreting PI pages, future broader-opening language, GitHub helper content, or proxy benchmark materials.

The page should not read like product validation, clinical readiness, public competition opening, or CAIS certification. It should read like a technical map with locked boundaries.
Core track vs proxy benchmark track

Two technical routes, one boundary

The technical snapshot must help builders distinguish the Sal-Meter molecular–electrochemical core signal path from the proxy benchmark support path.

Sal-Meter core signal track

  • Aptamer–iodine redox sensing
  • Gold-electrode iodine redox / thiol 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, behavioral timing
  • Synchronized multimodal benchmark platform
  • Metadata discipline and leakage-safe evaluation
  • Baseline models, replayable notebooks, dashboard drafts
  • 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 broader opening 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, clinical authority, diagnostic authority, therapeutic status, or device status.
CAIS layer stack

Layer stack at a glance

0

Molecular Interface

Consciousness–material interface at the cartridge / chamber level, realized as a signal-producing non-therapeutic interface under controlled conditions.

1

Acquisition & Preprocessing

Hardware-level signal capture, baseline correction, averaging, metadata discipline, and low-noise acquisition readiness.

2

Signal Processing

Noise suppression, feature extraction, normalization, state separation, and leakage-aware evaluation across controlled conditions.

3

Index Computation

Algorithmic conversion of approved features into downstream outputs only under the appropriate canonical conditions.

4

Interpretation & Governance

Application domain boundaries, research-only claims discipline, compliance limits, communication boundaries, and governance rules for allowed public language and downstream usage.

Layer 0 remains a non-therapeutic signal interface. This stack describes how signals move into downstream processing and indices, not clinical meaning.
Current execution order

Program order for technical builders

1

External Layer-0

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

2

SICS Internal Phase 0 — G-only

Internal state-gate work focused on G-channel baseline rule, acquisition discipline, and 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, metadata completeness, 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.
Minimal implementation flow

Five-step builder path

1

Interface boundary

Specify the interface, target boundary, excluded scope, authority layer, and what must not be claimed.

2

Hardware / acquisition readiness

Build a stable measurement bench and define raw signal export, metadata capture, and acquisition auditability before interpretation.

3

Signal pipeline

Implement fixed preprocessing, feature extraction, leakage control, holdout logic, and repeatable analysis structure.

4

Evidence package

Prepare data package, metadata sheet, QC checklist, versioned analysis, audit trail, and raw data handover discipline.

5

Validation gate

Move forward only after the current gate produces enough evidence for the next gate. Do not skip directly to product, certification, or clinical language.

Engineering and hiring route

Who should use this technical snapshot

This snapshot is now also a routing page for researchers, engineers, and hiring candidates who need to understand where they fit technically.

ESL

Electrochemical Systems Lead. Owns physical consistency: electrode behavior, chamber logic, drift handling, acquisition stability, SOP lock, and measurement hygiene.

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, labeling, 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.
Engineering checklist

What a serious team should have checked

Layer 0 · Interface

  • Target scope and excluded scope are explicitly documented.
  • The chosen interface has been checked against current CAIS / Sal-Meter boundary language.
  • External Layer-0 is not being confused with Internal Phase 0 or Phase 1.

Layer 1 · Hardware

  • At least one channel shows stable, repeatable signals across repeated measurements.
  • Basic stress tests for noise, contact stability, drift, and fouling have been considered.
  • Raw signal export and metadata capture are designed before interpretation.

Layer 2 · Signal Processing

  • A fixed preprocessing pipeline is implemented and versioned.
  • Signal-pattern differences are checked under controlled states rather than anecdotal sessions.
  • Leakage prevention, holdout logic, and audit trail are part of the plan.

Layer 3 · Indices and model outputs

  • Any output logic is cross-checked against the canonical definition layer before public claim.
  • All prohibited transformations from the negative-definition layer are actively avoided.
  • Proxy benchmark outputs are not mislabeled as Sal-Meter outputs.

Layer 4 · Governance

  • The team has an internal rule against clinical, therapeutic, certification, and commercial-readiness overclaiming.
  • Core members have read the compliance boundary and communication rules before public communication.
  • GitHub helper material is treated as public implementation support, not canonical authority.
Navigation

Read the stack, then decide the next move

Use this page when the question is architecture. Move next to Status if current opening and boundary are the question, to For PIs if participation is the question, to System Overview if the question is what Sal-Meter measures, 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 compliance, naming, or interpretive authority is the question.

Status For PIs PI Quick Decision Pack System Overview CAIS Topic Sal-Meter Topic Sal-Meter Kernel GitHub Human-State AI Proxy Benchmark GitHub Publications
Final boundary: this page is a non-canonical technical helper and structural snapshot. It does not grant CAIS compliance, Sal-Meter designation, certification 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.