Salpida Foundation Declaration
Public declaration and canonical registry gateway for the Consciousness Civilization Framework (CCF), CAIS, Sal-Meter, Human-State-Aware AI, and related helper surfaces. CCF, CAIS, Sal-Meter, Human-State AI, Proxy Benchmark 자료, GitHub helper route의 권위 경계를 고정하는 공개 선언 페이지
This page does not create authority. It identifies where authority is fixed, how it should be verified, and which public materials are only helper surfaces.
All constitutional, scientific, ethical, terminology, compliance, certification, conformance, publication, and governance authority remains fixed only in DOI-registered canonical records and designated OSF records.
If a definition, framework, rule, compliance status, certification rule, claim boundary, or Sal-Meter designation is not fixed in the DOI / OSF canonical registry, it has no canonical authority here — regardless of circulation, commentary, GitHub presence, landing-page visibility, or external citation.
Declaration is not the main research page, not the PI recruitment page, not the technical build page, and not the proxy benchmark page. It is the boundary stone: it tells readers where authority lives.
Core Principle
The Salpida Foundation functions as a public canonical archive and declaration surface for the CCF / CAIS / Sal-Meter document system.
It summarizes, points, routes, and links. It does not supersede, reinterpret, expand, or override canonical records.
This declaration page is for authority boundaries and registry navigation. The broader explanatory reading hub belongs on Home, Read, Topics, Publications, Status, For PIs, Human-State AI, and related landing pages.
Authority hierarchy / 권위 체계
The following hierarchy must control public language, research routing, GitHub usage, helper document interpretation, and candidate-facing communication.
Canonical DOI / OSF records
Binding authority layer. Definitions, boundaries, compliance, certification, conformance, publication rules, and root standards live here.
Foundation pages
Public reading and routing layer. These pages explain and guide, but cannot create new authority.
GitHub repositories
Implementation index and helper surface. GitHub can host code, examples, schemas, and README routes, but is not canonical authority.
Program / builder materials
Operational helper layer. Useful for recruitment, coordination, and implementation, but always downstream of canonical boundary records.
If GitHub, a landing page, helper text, LinkedIn text, SEO copy, public image, or recruitment material conflicts with a canonical DOI / OSF record, the canonical record controls.
Canonical Registry — Primary Clusters
The registry below is a short-route map into the canonical stack. For the full registry, use the master repository.
Constitutional Root
Definition & Measurement
CAIS & Material Interface
Sal-Meter / CAIS boundary records
These records govern public naming, compliance, certification, conformance, publication, and technical interpretation.
Sal-Meter Canonical Definition
Defines what may be called Sal-Meter.
Sal-Meter Negative Definition
Defines what must not be called Sal-Meter.
CAIS Compliance Boundary
Defines the boundary for CAIS compliance and designation language.
Claims & Terminology Control
Controls public terms, claims, designation language, and overclaim prevention.
Certification & Mark Usage Policy
Controls certification and mark usage. No helper page can grant these.
Publication & Communications Boundary
Controls public communication, publication, and external description boundaries.
Program-layer routes / 프로그램 실행 경로
These pages help readers, PIs, engineers, candidates, and builders navigate the program. They are important, but they are not authority sources.
Status
Current operating posture: kernel-first, pre-opening, research-stage, and claims-controlled.
For PIs
Scoped readiness entry for PIs, laboratories, engineers, and technical contributors.
Human-State-Aware AI Interaction
Proxy benchmark support track for synchronized multimodal human-state sensing and future comparison.
Sal-Meter Kernel GitHub
Core technical gateway for the kernel-first Sal-Meter / CAIS program. It routes PIs, ESL / EStL candidates, and technical readers.
Proxy Benchmark GitHub
Public helper repository for schemas, synthetic examples, notebooks, dashboard drafts, and issue coordination.
Document Index
Broader map of document families, helper pages, and linked DOI records.
Status, For PIs, Human-State AI, GitHub repositories, landing pages, and public helper documents are routing and coordination surfaces. They do not create canonical authority, CAIS compliance, Sal-Meter designation, certification status, mark usage rights, clinical authority, or device status.
Core track vs Proxy benchmark / 코어 트랙과 프록시 트랙
Molecular–electrochemical signal path
The core track asks whether a new signal interface exists and whether it matters after lock review.
- External Layer-0
- SICS Internal Phase 0 / Phase 1
- Phase 2a / Phase 2b
- LOCK 1 / LOCK 2 before broader opening
- ESL / EStL core leadership route
Synchronized benchmark support
The proxy route builds a multimodal comparison platform using existing human-state proxy signals.
- ECG / HRV / EDA / PPG / EEG
- eye / gaze / behavioral timing
- metadata discipline and leakage-safe evaluation
- future comparison layer for Sal-Meter inputs
- PBEE / MDE / HSOPM builder route
Proxy is not Sal-Meter
Proxy benchmark signals do not become Sal-Meter by being synchronized. GitHub helper materials are not canonical authority.
- No raw human data in public GitHub
- No CAIS compliance claim
- No certified or validated Sal-Meter claim
- No clinical, diagnostic, or therapeutic claim
- No GitHub-only authority claim
Role map / 역할별 경로
Declaration does not recruit. It only points candidates to the correct downstream surfaces without granting authority.
Electrochemical Systems Lead
Physical consistency: electrode behavior, chamber discipline, drift handling, acquisition reliability, and SOP lock.
Evidence & Standardization Lead
Evidence consistency: metadata, QC, leakage prevention, audit trail, reproducibility pack, and claims discipline.
Proxy benchmark builders
Synchronized biosignals, edge inference, dataset schema, holdout design, baseline models, and dashboard flow.
Human-session operations
Consent pathway, participant flow, session timing, metadata completion, and raw-data governance.
These roles are program-layer working interfaces. They do not create constitutional authority, CAIS compliance, Sal-Meter recognition, certification, device status, clinical authority, or public designation rights.
Frequently Asked Questions
Is this website a governing body?
No. It does not govern, regulate, or exercise authority by itself. It serves as a declaration surface and reference gateway to DOI / OSF canonical records.
Can this page override DOI documents?
No. All binding authority remains fixed only in the original DOI / OSF canonical documents. This page cannot reinterpret, extend, or modify them.
Can GitHub become canonical authority?
No. GitHub can host implementation notes, code, schemas, examples, and README routes. It is a helper surface unless explicitly fixed by DOI registration.
Is the Sal-Meter Kernel GitHub a canonical definition?
No. The Sal-Meter Kernel GitHub is a core technical gateway for builder orientation. It does not define Sal-Meter, CAIS compliance, certification, or conformance standing.
Is the proxy benchmark repository part of Sal-Meter certification?
No. The proxy-benchmark-track repository is a technical helper surface for benchmark infrastructure. It does not grant CAIS compliance, Sal-Meter designation, certification, or mark usage rights.
Where does constitutional authority reside?
Authority resides solely in DOI / OSF canonical records. If there is any ambiguity, always return to the DOI / OSF source before any derivative text.