Canonical public index for Salpida Foundation / SICS
This repository exists to route readers to the DOI-registered canonical records of the Salpida Foundation document stack.
GitHub carries no independent interpretive authority. Canonical authority lives only in DOI-registered records on Zenodo / OSF.
Current Sal-Meter / CAIS status note
The current Sal-Meter / CAIS program is kernel-first · pre-opening · research-stage.
For current program participation, read Status first.
This repository remains a canonical DOI routing index, not the active technical collaboration surface.
- a public GitHub index for canonical DOI records
- a routing layer to the foundation site and DOI-registered documents
- a lineage / citation / authority map
- a place to understand where canonical authority actually lives
- not the source of final interpretive authority
- not the main technical collaboration surface
- not the active kernel-program gateway
- not a public build race or implementation hub
- not a recruitment surface
- not a substitute for Zenodo / OSF canonical records
- Salpida Foundation
https://salpida.foundation
-
Concept DOI — all versions
https://doi.org/10.5281/zenodo.18123806 -
Version DOI — current frozen snapshot
https://doi.org/10.5281/zenodo.18123807
If you are a PI, engineer, builder, laboratory, candidate, or technical watcher following the present Sal-Meter / CAIS kernel-stage program, do not start from GitHub alone.
Read the current program status first:
-
For PIs and Laboratories
https://salpida.foundation/for-pis/ -
Sal-Meter Topic
https://salpida.foundation/topics/sal-meter/ -
Sal-Meter Kernel Program GitHub
https://github.com/salpida-foundation/sal-meter-kernel-program
This route is Status-first.
GitHub is the technical gateway, not the canonical authority layer.
- GitHub helper release: https://github.com/salpida-foundation/sal-meter-kernel-program/releases/tag/v0.1.0
- This is a public helper release only.
- It is not canonical authority.
- It does not create Sal-Meter validation, CAIS compliance, certification, conformance recognition, clinical readiness, diagnostic use, therapeutic use, device readiness, commercial readiness, public SDK release, live public competition status, or mark-usage authorization.
- It points readers to the Status page, the Sal-Meter Kernel technical gateway, and the DOI / OSF authority layer.
Start with:
Start with:
- the Concept DOI
- the Version DOI
- the DOI-linked records on Zenodo / OSF
Start with:
salpida-canonical= public GitHub index for canonical DOI authoritysal-meter-kernel-program= public technical gateway for the present kernel-stage programStatus= current public state, open routes, and not-open-yet boundary- Zenodo / OSF DOI records = final canonical authority
The current Sal-Meter / CAIS program should be described as:
- kernel-first
- pre-opening
- research-stage
- non-clinical
- non-diagnostic
- non-therapeutic
- pre-device
- pre-certification
The current public technical route includes:
- External Layer-0 feasibility inquiry
- I₃⁻ / Aptamer G-Iodine development inquiry
- ESL / EStL recruitment
- internal lab readiness
- proxy benchmark preparation as support track only
The following should not be stated or implied:
- live public competition
- validated Sal-Meter
- certified Sal-Meter
- CAIS-compliant device
- clinical use
- diagnostic use
- therapeutic platform
- commercial device
- proxy stack as Sal-Meter
This repository points outward to canonical document families such as:
- Consciousness Civilization Framework (CCF)
- constitutional root and authority records
- canonical civilizational standards
- CAIS core standard
- CAIS architecture
- signal processing / hardware / prototype standards
- compliance and terminology controls
- canonical definition
- negative definition
- compliance boundary
- future broader opening governance
- PI readiness and Phase 0 program-direction records
- claims & terminology control
- certification / mark usage policy
- publication & communications boundary
- conformance architecture
- AI governance entry paper
- AI 2027 response essay
- third-party evaluation paper
- bridge and public-facing orientation records
For full authoritative records, use the DOI entry points above.
Modern GitHub repositories are easy to fork, summarize, scrape, paraphrase, and reinterpret.
That is exactly why canonical authority must be fixed elsewhere.
This repository exists to make one thing clear:
the public GitHub layer is useful for discovery, navigation, and reading order — but not for sovereign interpretation.
The canonical layer is fixed only in DOI-registered records.
If you cite, reference, analyze, or derive from this project:
- cite the DOI-registered record
- do not treat GitHub text alone as final authority
- use the Concept DOI when you want the stable entry for all versions
- use the Version DOI when you want the exact frozen snapshot
This repository is useful if you want to:
- find the canonical DOI entry quickly
- understand which layer is canonical and which is explanatory
- route from GitHub to the foundation site
- trace document lineage across CCF / CAIS / Sal-Meter stacks
- avoid authority confusion between public helper text and fixed records
- confirm that the current Sal-Meter / CAIS route is Status-first
A simple rule:
- general reader → start at salpida.foundation
- PI / engineer / lab / candidate → start at Status, then For PIs, then
sal-meter-kernel-program - citation / canonical authority / document lineage → start at the DOI entry above
Do not confuse the active technical gateway with canonical authority.
salpida-canonicalroutes readers to DOI authority.sal-meter-kernel-programroutes technical readers into the current kernel-stage execution surface.Statusdefines what is open now and what is not open now.
Origin architect: Jinho Lee, MD
ORCID: 0009-0005-3809-4588
Affiliation:
Salpida Foundation / Salpida Institute of Consciousness Science (SICS)
Public hub:
https://salpida.foundation
Current program status:
https://salpida.foundation/status/
Technical gateway:
https://github.com/salpida-foundation/sal-meter-kernel-program
This repository does not ask to be believed.
It asks to be routed correctly.
Read on the foundation site.
Check current status first.
Build through the kernel gateway.
Cite the DOI record.