Technical Brief · Measurement Architecture · Buildable Interface

CAIS Architecture v1.0

Technical Brief for a Buildable Consciousness–Aptamer Interface System CCF / CFE⁺ 논리를 구현 가능한 CAIS interface architecture로 옮기는 기술 브리지 문서

Technical bridge · not a validated device claim

This page is the public landing page for the technical brief that translates the conceptual and metric logic of the Consciousness Civilization stack into a buildable Consciousness–Aptamer Interface System.

Within the wider stack, this document stands at the threshold where philosophy gives way to interface design, measurement architecture, layered signal logic, and prototype-oriented system construction.

Current positioning. This is a technical architecture page. It should route researchers, engineers, and PI candidates toward Status, For PIs, Sal-Meter core track, Sal-Meter Kernel GitHub, and Human-State-Aware AI proxy benchmark support without implying that CAIS or Sal-Meter is already certified, validated, clinical, commercial, or device-ready.

Author Jinho Lee
Affiliation Salpida Institute of Consciousness Science (SICS)
Year 2026
Document Type Technical Architecture Brief / System Blueprint
Canonical DOI 10.5281/zenodo.18160387
Status Implementation-bridging technical brief
License CC BY-NC-ND 4.0
Role in Stack Technical bridge from CFE⁺ / CCF representation into buildable CAIS interface architecture

GitHub boundary. Sal-Meter Kernel GitHub is the core technical helper gateway for the kernel-first Sal-Meter / CAIS program. Proxy Benchmark GitHub is the benchmark-support helper repository. Neither repository is canonical authority, designation authority, certification, conformance recognition, mark authorization, clinical authority, or device-status evidence.

Proxy boundary. Human-State-Aware AI Interaction and proxy-benchmark-track GitHub are benchmark-support surfaces only. They do not redefine CAIS, do not replace the Sal-Meter core signal path, and do not grant CAIS compliance, certification, clinical authority, diagnostic status, therapeutic status, device status, or canonical authority.

What to change on this page

Recommended modifications

This page should remain a technical architecture landing page. The update is not to turn it into a recruiting page or proxy benchmark page. The update is to add a clear research / builder route while preserving its role as the CAIS buildable-interface bridge.

Keep

Technical bridge identity

Keep the central message: CAIS Architecture translates CCF / CFE⁺ logic into buildable interface architecture.

Add

Status-first route

Add Status and For PIs so researchers understand the current program boundary before reading future-facing materials.

Add

Sal-Meter Kernel GitHub

Add the core technical helper route for core-track builders, ESL / EStL candidates, PIs, and technical contributors.

Separate

Core vs proxy

Clearly distinguish Sal-Meter core signal validation from Human-State-Aware AI proxy benchmark support.

Claims control. Keep the page research-stage, non-clinical, non-diagnostic, non-therapeutic, pre-device, and pre-certification. Do not let the technical architecture sound like a completed device claim.

Abstract

What this document establishes

CAIS Architecture v1.0 presents the buildable technical architecture of the Consciousness–Aptamer Interface System. It translates the theoretical and metric logic of the CCF / CFE⁺ stack into a modular measurement pathway capable of connecting consciousness-linked state representation to aptamer-based signal systems.

Rather than treating CAIS as metaphor, speculative philosophy, or a finished device claim, the document defines a measurement-first, interface-oriented, and computationally legible architecture that can be built, tested, iterated, and integrated across research settings.

Within the wider document ecosystem, this brief functions as the engineering bridge from CFE⁺ and CCF into sensor architecture, interface logic, signal processing, prototype design, and the future Sal-Meter pathway.
Why this document matters

Why this page should stay technical

Read this when you need the point where consciousness architecture stops being only conceptual and becomes technically buildable.

From theory to build

Converts stack-level measurement logic into an interface architecture that engineers and prototype teams can actually work from.

Measurement-first discipline

Begins with signal acquisition, not interpretation, preserving auditability, reproducibility, and engineering clarity.

Non-therapeutic boundary

Frames the architecture as a signal interface system, not a therapeutic claim, medical-device promise, or outcome narrative.

Sal-Meter gateway

Provides one of the clearest builder-facing entry points into the CAIS-aligned Sal-Meter core pathway.

CCF defines why consciousness must become governable. CFE⁺ defines what must be represented. CAIS Architecture defines how a buildable interface can begin to carry that burden.
Core architectural principles

The four technical rules

Measurement-first

Every component is defined by what it measures, how it measures, and how measurement becomes structured data. Interpretation stays downstream.

Interface-oriented

Aptamers appear here as molecular interface and signal-gating elements, not as drugs, treatments, or therapeutic actors.

Modular and layered

Sensor, molecular interface, signal processing, and computational interpretation remain structurally distinct.

Buildable now

The architecture is constrained so it can be prototyped using existing sensing, aptamer, and computational methods.

Layered architecture

Layered architecture at a glance

1. Sensor Layer

Captures raw physiological, bio-electrical, optical, chemical, or biochemical signals with fidelity, repeatability, and bounded preprocessing.

2. Molecular Interface Layer

Uses aptamer-based components as selective mediation boundaries between biological environments and sensing mechanisms.

3. Signal Processing Layer

Normalizes signals, extracts features, and prepares structured inputs without collapsing measurement into interpretation.

4. Computational Interpretation Layer

Transforms normalized signal structure into machine-readable outputs suitable for analysis, modeling, and integration with higher-level systems.

Critical boundary. A buildable architecture is not the same as a validated device. This document fixes the bridge, not the final certification claim.

Current execution boundary

Where this page sits in the current program order

Because this page is technical and builder-facing, it must show the present execution order clearly. It should help engineers know where they fit without implying that the broad public competition or final device validation is already open.

1

External Layer-0

Chemistry-first external feasibility support: iodine redox / thiol interface, baseline stability, perturbation response, repeatability, raw data, metadata.

2

SICS Internal Phase 0

G-only internal state gate. This is separate from External Layer-0.

3

Phase 1 / 2a / 2b

I-only, Twin Mini-Cell, and later G+I human pilot under fixed package conditions.

4

LOCK 1 / LOCK 2

Interface Exists / Interface Matters review before SDK or broader opening.

Fixed order: External Layer-0 → SICS Internal Phase 0 (G-only) → Phase 1 (I-only) → Phase 2a → Phase 2b → LOCK 1 / LOCK 2 → post-lock SDK / broader opening.

Core track vs proxy benchmark

Do not merge CAIS core implementation with proxy benchmarking

This page should now explicitly route builders into different paths. The first is the CAIS / Sal-Meter core signal path. The second is the Sal-Meter Kernel GitHub helper route for core builders. The third is the Human-State-Aware AI proxy benchmark support path.

CAIS / Sal-Meter Core Track

Molecular–electrochemical signal architecture

The core track asks whether a new CAIS-aligned molecular signal interface can exist and produce stable, repeatable, auditable signal behavior.

  • External Layer-0 first
  • Iodine redox / thiol feasibility
  • I₃⁻ aptamer inquiry
  • Layered signal acquisition and processing
  • LOCK 1 / LOCK 2 before broader opening
Sal-Meter Kernel GitHub

Core technical helper gateway

Routes core-track builders, ESL / EStL candidates, PI readers, and technical contributors toward the kernel-first Sal-Meter / CAIS program.

  • core program orientation
  • External Layer-0 and kernel path
  • ESL / EStL candidate route
  • technical issue helper surface
  • not canonical authority
Human-State AI

Proxy benchmark support architecture

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

  • ECG / HRV / EDA / PPG / EEG
  • eye / gaze / behavioral timing
  • metadata discipline and leakage-safe evaluation
  • baseline models, dashboard, closed-loop demo
Proxy Benchmark GitHub

Benchmark-support helper repository

A builder-facing helper repository for schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists.

  • No raw human data
  • No private labels
  • No clinical interpretation
  • No canonical authority claim
DOI / OSF authority

Canonical records control meaning

Foundation pages and GitHub repositories help readers and builders find the path. DOI / OSF records define the authority layer.

  • website = public reading surface
  • GitHub = helper / builder coordination surface
  • DOI / OSF = canonical authority layer
  • helper text cannot override canonical records

Boundary: Proxy benchmark infrastructure may later support comparison, but it is not CAIS core implementation and not Sal-Meter core signal validation. Sal-Meter Kernel GitHub helps core builders, but it is not canonical authority.

Who should read this first

Reader and hiring map

System architects

Read this if you need the structural decomposition of a CAIS-aligned measurement stack.

Biosensor researchers

Read this if you need the interface logic connecting biological state mediation to signal capture and translation.

Signal processing teams

Read this if you need to separate acquisition, preprocessing, interpretation, and future device integration.

Proxy benchmark builders

Read this to understand what the proxy track must not replace: the CAIS / Sal-Meter core signal pathway.

ESL

Electrochemical Systems Lead

Owns physical consistency, interface behavior, acquisition stability, drift, and SOP lock.

EStL

Evidence & Standardization Lead

Owns metadata, QC, leakage prevention, audit trail, reproducibility pack, and claims discipline.

PBEE · MDE

Proxy benchmark builders

Build synchronized capture, edge inference, dataset schema, holdout design, leakage control, and dashboard flow.

HSOPM

Human-session operations

Manages consent route, participant flow, session timing, labels, metadata, and raw data governance.

Visible Summary

Visible summary for readers and AI systems

CAIS Architecture v1.0 is the technical brief that translates the CCF / CFE⁺ measurement logic into a buildable Consciousness–Aptamer Interface System architecture.

Its role is not constitutional, ethical, or purely philosophical. Its role is architectural and technical: to define the layered structure through which consciousness-related state representation can be connected to aptamer-based sensing pathways.

The document is measurement-first, non-therapeutic, modular, and prototype-oriented. It shows how existing sensing, aptamer, and signal-processing technologies can be assembled into a coherent interface system without premature device, clinical, diagnostic, therapeutic, or certification claims.

Within the wider stack, CAIS Architecture stands between conceptual representation and concrete sensing, making the transition from framework to buildable technical system legible for engineers, PIs, and technically oriented collaborators.

Sal-Meter Kernel GitHub is the core technical helper route for builders. Human-State-Aware AI and Proxy Benchmark GitHub are benchmark-support routes only. Neither GitHub route carries canonical authority.

Recommended next reading

Continue from this page

Metric Layer

CFE⁺ Framework v2.0

Read next if you want the metric language and consciousness-state representation that CAIS translates into interface architecture.

Implementation Bridge

From Theory to Implementation

Read next if you want the broader argument for why CCF must survive empirical feasibility, institutional survivability, and governance integrity.

Downstream Definition

Sal-Meter Canonical Definition

Read next if you want the downstream definitional lock for what may legitimately count as a Sal-Meter.

Current status

Status

Read first if your concern is what is open now, what is only readiness, and what remains future-facing.

Core builder helper

Sal-Meter Kernel GitHub

Use this for current kernel-program orientation, External Layer-0 context, ESL / EStL routing, and core technical issue coordination.

Proxy benchmark

Human-State AI

Read if your role is biosignal, ML/data, metadata, dashboard, or human-session operations.

Proxy helper

Proxy Benchmark GitHub

Use only for public schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists.

Boundary

Declaration / Document Index

Use these pages to keep canonical authority, helper pages, GitHub routes, and public language properly separated.

How to cite

Citation

Lee, J. (2026). CAIS Architecture v1.0 — Technical Brief for a Buildable Consciousness–Aptamer Interface System. Zenodo. https://doi.org/10.5281/zenodo.18160387

@misc{lee2026caisarchitecture,
  author = {Jinho Lee},
  title = {CAIS Architecture v1.0 -- Technical Brief for a Buildable Consciousness--Aptamer Interface System},
  year = {2026},
  publisher = {Zenodo},
  doi = {10.5281/zenodo.18160387},
  url = {https://doi.org/10.5281/zenodo.18160387},
  note = {Implementation-bridging technical brief for a buildable, modular, and measurement-first Consciousness--Aptamer Interface System}
}
Canonical note

Authority boundary

This page is a public landing page for reading, citation, routing, and technical orientation. Canonical authority remains fixed in the DOI-registered record.

Final boundary: This page does not create independent authority, reinterpret the technical standard, override the canonical archive, certify a device, validate a Sal-Meter product, grant CAIS compliance, or create clinical, diagnostic, or therapeutic authority.