CAIS Architecture & Sal-Meter Technical Snapshot
A fast technical view of the buildable CAIS stack for the Sal-Meter: layer separation, minimal implementation flow, required canonical DOI map, and the engineering checklist needed to scope a research-stage prototype without confusing helper language with canonical authority.
What this page is for
This page answers one concrete builder question: How can we actually scope a CAIS-compliant Sal-Meter prototype without crossing the canonical boundary?
It is a compressed technical landing page for the current CAIS / Sal-Meter build path. It does not create new naming authority, statistical authority, or compliance authority.
Layer stack at a glance
Molecular Interface
Consciousness–material interface at the cartridge / chamber level, realized as a signal-producing non-therapeutic interface under controlled conditions.
Acquisition & Preprocessing
Hardware-level signal capture, baseline correction, averaging, and low-noise acquisition readiness.
Signal Processing
Noise suppression, feature extraction, normalization, and state separation across controlled conditions.
Index Computation
Algorithmic conversion of OE / RE / EE features into canonical VCE / CRI / CFI outputs.
Interpretation & Governance
Application domain boundaries, research-only claims discipline, compliance limits, and governance rules for allowed public language and downstream usage.
Five-step builder path
Interface design
Choose aptamer or alternative molecular interface, specify OE / RE / EE hypotheses, and lock base conditions such as buffer, potential, temperature, and timing.
Hardware prototype
Build a 1–3 channel measurement bench, confirm acquisition stability, and establish shielding / wiring / bench repeatability.
Signal pipeline
Implement filtering, baseline correction, repeat averaging, OE / RE / EE feature extraction, and basic statistics / clustering across states.
Index computation & UI
Implement VCE / CRI / CFI exactly as fixed in the canonical layer, and expose them through a loggable dashboard or app surface.
Validation experiments
Run repeated measurements across controlled states such as sleep, rest, meditation, or acute stress, and quantify reproducibility before any broader claim surface.
What a serious team should have checked
Layer 0 · Interface
- Molecular hypotheses for OE, RE, and EE are explicitly documented.
- The chosen interface has been checked against CAIS requirements.
Layer 1 · Hardware
- At least one channel shows stable, repeatable signals across repeated measurements.
- Basic stress tests for noise, temperature, and contact resistance have been performed.
Layer 2 · Signal Processing
- A fixed preprocessing pipeline is implemented and versioned.
- Signal-pattern differences are confirmed for controlled states rather than anecdotal sessions.
Layer 3 · Indices
- VCE / CRI / CFI computation logic is cross-checked against the canonical definition layer.
- All prohibited transformations from the negative-definition layer are actively avoided.
Layer 4 · Governance
- The team has an internal rule not to make clinical or commercial efficacy claims beyond research scope.
- Core members have read the compliance boundary and the relevant competition / implementation documents before public communication.