For PIs — Sal-Meter / CAIS Research Entry
A status-first decision page for laboratories, principal investigators, engineers, and technical candidates assessing where they can responsibly contribute now. 연구실, PI, 엔지니어, 기술 후보자가 현재 단계에서 어떤 경로로 들어올 수 있는지 판단하는 공개 진입 페이지입니다.
This page is not a live broad public competition announcement. Current Sal-Meter / CAIS work remains kernel-first, pre-opening, research-stage, non-clinical, non-diagnostic, non-therapeutic, pre-device, and pre-certification.
Sal-Meter Kernel Pre-SRA Helper Package v0.1.0
Sal-Meter Kernel Pre-SRA Helper Package v0.1.0 has been released as a GitHub public helper pre-release. It supports External Layer-0 feasibility inquiry, Layer-0 data deliverables, public/private data boundary, aptamer inquiry boundary, ESL/EStL role separation, Layer-0 task routing, and 90-day pre-SRA execution gates.
This release does not create Sal-Meter validation, CAIS compliance, certification, device readiness, clinical status, public SDK release, or public competition opening.
Primary routes for PIs
The first decision is not whether to join everything. The first decision is which route fits your capability without claims drift. PI의 첫 판단은 전체 프로젝트 참여 여부가 아니라, 자신의 연구실이 어느 제한된 층을 책임질 수 있는지입니다.
Sal-Meter Core
Core signal route for CAIS-aligned Sal-Meter research: iodine redox, thiol / disulfide logic, aptamer-interface inquiry, electrochemical measurement, and kernel lock.
Best for electrochemistry, biosensor, redox, aptamer, molecular-interface, and device-oriented laboratories.
Pre-SRA Helper v0.1.0
GitHub public helper release for External Layer-0, Layer-0 deliverables, public/private boundary, aptamer inquiry, ESL/EStL role separation, issue routing, and 90-day execution gates.
Best first route for PIs, labs, counsel, advisors, and candidates who need the execution boundary before discussion.
Proxy Track
Human-State Proxy Benchmark Track for synchronized proxy signals, metadata discipline, baseline modeling, leakage-safe evaluation, and future comparison with Sal-Meter inputs.
Best for biosignal, ML, dashboard, session protocol, human-state packet, and AI interaction benchmark builders.
Human-State Energy Efficiency
HSEE connects AI performance, human-state cost, recovery burden, relational friction, and civilizational efficiency into a measurable research direction.
Best for governance, AI evaluation, human factors, organizational systems, energy-efficiency, and policy-oriented researchers.
One-line decision
Can your lab own one bounded layer without overclaiming?
A useful PI or laboratory does not need to own the whole stack. It must be able to strengthen one bounded layer with clean data, clear metadata, raw-data handover, audit trail, reproducibility discipline, and careful public language.
Do not present this page or v0.1.0 as proof of consciousness measurement, diagnostic device readiness, therapeutic use, clinical validation, CAIS compliance, certified Sal-Meter status, public SDK release, or public competition opening.
Choose your entry mode
This page separates current research entry, GitHub helper release, support-track work, and later application routes. Do not merge them.
External Layer-0 feasibility
Best for electrochemistry, biosensor, redox, or biomolecular-interface labs that can evaluate iodine redox / thiol-linked perturbation behavior under non-therapeutic conditions.
- Iodine redox baseline behavior
- Gold electrode interface discipline
- Drift and repeatability
- Controlled perturbation direction
- Raw data and metadata handover
I₃⁻ aptamer inquiry
Best for aptamer, molecular recognition, biosensor, and chemical-biology groups that can discuss I₃⁻ target feasibility without claiming final Sal-Meter validation.
- I₃⁻ primary target feasibility
- Binding characterization boundary
- Selectivity and cross-reactivity logic
- Immobilization suitability thinking
- Sequence, data, IP, and publication discipline
Human-State AI proxy benchmark
Best for teams that can build synchronized benchmark infrastructure using existing proxy signals while keeping Sal-Meter and Proxy Track clearly separated.
- ECG / HRV / EDA / PPG / optional EEG
- Eye, gaze, voice, timing, and interaction metadata
- Human-State Packet structure
- Leakage-safe evaluation
- Baseline models and dashboards
Human-State Energy Efficiency
Best for researchers who want to evaluate the hidden cost of AI outputs through human-state burden, recovery load, attention fragmentation, and relational friction.
- Human-state cost framing
- AI output consequence evaluation
- Recovery burden and relational cost
- Efficiency beyond speed and task performance
- Policy, governance, and enterprise-readiness bridge
What v0.1.0 gives a PI or lab
The v0.1.0 release is not a scientific crown. It is a doorframe. It tells a lab what can be discussed, what must be delivered, and what must remain outside public GitHub.
Layer-0 SOW
External Layer-0 mini pilot scope and feasibility question.
Data deliverables
Raw traces, metadata, QC, run map, failed-run and anomaly expectations.
Public / private boundary
What may be public, what must remain controlled, and what belongs in legal/SRA channels.
Aptamer boundary
Public I₃⁻ / Aptamer G-Iodine inquiry without sequence-sensitive leakage.
ESL / EStL split
Physical measurement review separated from evidence and standardization review.
Issue template
Public-safe Layer-0 task routing, data boundary checks, claims boundary checks, and review routing.
Release snapshot
First public helper package frozen as v0.1.0.
What it does not grant
No validation, compliance, certification, device readiness, clinical status, public SDK, or public competition opening.
Current program order
The entry decision must follow the actual sequence. External Layer-0 is not SICS Internal Phase 0. Proxy Track is not Sal-Meter. HSEE is not a certification route.
External Layer-0
Chemistry-first feasibility support for iodine redox / thiol interface behavior.
SICS Internal Phase 0
Internal G-only state gate, baseline discipline, and evidence structure.
Phase 1
I-only reproducibility and I₃⁻ / I⁻ interface discipline.
Phase 2a / 2b
Twin Mini-Cell, G+I pilot, leakage control, and kernel review.
LOCK 1 / LOCK 2
Broader opening and SDK logic belong downstream of lock review.
Current boundary
Broad opening is not currently live. Any future broader-opening material must be read downstream of LOCK 1 / LOCK 2 review.
What kind of lab fits now?
The useful question is not “Can we explain consciousness?” The useful question is “Can we produce one disciplined, auditable contribution without claims drift?”
Electrochemistry / Biosensor
Gold electrode workflows, redox characterization, baseline stability, drift analysis, controlled perturbation, and repeatability.
Aptamer / Chemical Biology
Aptamer target feasibility, selectivity logic, immobilization constraints, and measurement-interface thinking without therapeutic claim inflation.
Signal / ML / Statistics
Feature extraction, leakage prevention, holdout design, metadata discipline, reproducibility logic, and replayable analysis.
Human Factors / Governance
Human-state cost, recovery burden, AI output consequence, non-surveillance policy, and careful public communication.
Research roles and candidate routes
Core-track candidates and proxy-track candidates should not be merged. Different layers require different people.
| Route | Role | Owns | Primary output |
|---|---|---|---|
| Core | ESL Electrochemical Systems Lead |
Physical consistency: measurement workflow, chamber logic, electrode behavior, drift handling, cleaning discipline, and SOP lock. | Stable measurement protocol, electrode / chamber SOP, drift report, reproducibility notes. |
| Core | EStL Evidence & Standardization Lead |
Evidence consistency: metadata schema, QC, holdout, leakage prevention, audit trail, version control, and reproducibility package. | Data schema, QC checklist, leakage firewall, audit package, reproducibility pack. |
| Helper | Layer-0 task routing GitHub issue template |
Public-safe task creation, data boundary check, claims boundary check, ESL/EStL routing, completion criteria. | Bounded issue structure for External Layer-0 helper tasks. |
| Proxy | PBEE / MDE Proxy Benchmark Builders |
Synchronized biosignal capture, edge inference, dataset schema, labels, baseline models, dashboard, and leakage-safe evaluation. | Synthetic sample package, schema helpers, evaluator, dashboard draft, benchmark report. |
| Session | HSOPM Human-Session Operations |
Consent pathway, participant flow, session timing, metadata completion, data handling, and human-session documentation. | Session protocol, consent-bound packet flow, operator log, public boundary checklist. |
Data and evidence expectations
A serious lab conversation requires evidence discipline before interpretation.
Raw data
Summary-only results are not enough. Raw files and condition mapping must be transferable for independent review.
Metadata
Run ID, condition, replicate, operator, device, electrode, timing, QC flag, anomaly notes, and version should be traceable.
Controls
Repeatability, baseline drift, negative controls, and perturbation direction must be separated from narrative interpretation.
Claims
A useful result may be positive, negative, partial, or boundary-defining. None of these create certification.
GitHub routes for technical readers
GitHub helps builders. It does not define canonical authority.
Sal-Meter Kernel v0.1.0
Public helper pre-release for pre-SRA execution readiness. It freezes the first helper package for External Layer-0, data deliverables, public/private boundary, aptamer inquiry, ESL/EStL role separation, issue routing, and 90-day execution gates.
- GitHub helper pre-release
- Not canonical authority
- Not Sal-Meter validation
- Not CAIS compliance
- Not public competition opening
sal-meter-kernel-program
Public technical gateway for the current kernel-first Sal-Meter / CAIS program.
- Core Sal-Meter / CAIS orientation
- Status-first route
- ESL / EStL recruitment boundary
- Layer-0 and kernel program routing
- Technical helper surface only
proxy-benchmark-track
Builder-facing helper repository for synchronized multimodal proxy benchmark infrastructure.
- Schemas
- Synthetic / sample data
- Baseline evaluators
- Dashboard drafts
- No raw human data
Authority rule
Do not treat GitHub README wording or GitHub release notes as canonical authority. DOI / OSF records govern definitions, naming boundaries, compliance boundaries, certification rules, conformance rules, publication boundaries, and claims boundaries.
Application / pilot route
Application routes belong after the research routes. They should not be placed before Sal-Meter Core, Pre-SRA helper release, Proxy Track, or HSEE for a PI-facing page.
AI Waste Audit
AI Waste Audit is an application or pilot route for evaluating hidden human-state cost, recovery burden, attention loss, relational friction, and operational waste created by AI-assisted workflows.
- Not a core Sal-Meter validation route
- Not CAIS compliance
- Not clinical interpretation
- Not employee surveillance
- Suitable as a later enterprise / governance pilot route
From research to pilots
A PI-facing page should first protect the scientific entry routes. Application routes become useful only after the boundary, data structure, and claims discipline are clear.
- Research route first
- Evidence package before product language
- Pre-SRA helper boundary before lab conversation
- Proxy benchmark before enterprise claims
- HSEE before AI Waste Audit framing
- Application pilots only within bounded, consent-based, non-surveillance language
Decision checklist
A scoped conversation is reasonable when three or more answers are yes.
Good fit signals
- We can contribute one clearly scoped layer.
- We can work inside non-diagnostic, non-therapeutic language.
- We can produce raw data, metadata, and a replayable evidence package.
- We can accept positive, negative, partial, or boundary results.
- We can read the v0.1.0 helper release without treating it as validation.
- We can avoid claiming ownership of the whole stack.
Poor fit signals
- You need a validated product claim before contributing.
- You want exclusive control over the whole standard.
- You intend to frame the work as diagnosis or therapy now.
- You cannot provide raw data or metadata discipline.
- You want to present proxy signals as Sal-Meter.
- You treat GitHub v0.1.0 as CAIS compliance or certification.
What to send if you want to talk
Send one scoped note. Do not send a vague expression of interest.
Layer-0 lab
“We can evaluate Layer-0 electrochemical feasibility under a bounded setup and provide raw data, metadata, controls, repeatability notes, and deviation logs.”
Aptamer group
“We can discuss I₃⁻-targeted aptamer feasibility, binding characterization, selectivity, cross-reactivity, and sensor-oriented suitability.”
Proxy benchmark builder
“We can contribute to synchronized biosignal capture, metadata schema, baseline modeling, dashboarding, or leakage-safe evaluation.”
HSEE / application pilot advisor
“We can advise on human-state cost, AI output consequence, recovery burden, or application pilot design under non-surveillance boundaries.”
Recommended reading order
Read in this order. It prevents route confusion.
| Order | Page | Use it for | Open |
|---|---|---|---|
| 1 | Status | Understand what is open now, what is readiness only, and what remains future-facing. | Open Status |
| 2 | Sal-Meter Kernel v0.1.0 | Understand the pre-SRA helper package, Layer-0 data deliverables, public/private boundary, aptamer inquiry boundary, and ESL/EStL role separation. | Open Release |
| 3 | Sal-Meter Core | Understand the research-stage core signal route and CAIS boundary. | Open Sal-Meter |
| 4 | Proxy Track | Understand synchronized multimodal proxy benchmark infrastructure. | Open Proxy Track |
| 5 | HSEE | Understand human-state cost, AI consequence, recovery burden, and efficiency framing. | Open Publications |
| 6 | GitHub helper routes | Use GitHub only after the public boundary and current status are understood. | Open GitHub |
| 7 | Application / pilot route | Discuss bounded pilots such as AI Waste Audit only after research route alignment. | Open route |
Public claims boundary
These phrases protect the project from premature inflation.
Live public competition
Broad public participation belongs after internal locks hold.
Validated Sal-Meter
Current systems are research-stage modules, prototypes, helper releases, or readiness structures.
Clinical / diagnostic / therapeutic use
Current work is non-clinical, non-diagnostic, and non-therapeutic.
v0.1.0 as compliance
v0.1.0 is a GitHub public helper pre-release. It is not CAIS compliance, certification, conformance recognition, or mark authorization.
Final boundary
Canonical authority remains fixed in DOI / OSF records. This page is a public routing and decision surface for PIs, laboratories, engineers, builders, and technical candidates.
Direct links
Core route
Proxy, HSEE, and application route
Contact for scoped participation
Send one bounded contribution proposal. Name the route, the layer, the evidence package you can produce, and the claims boundary you will respect.