Consciousness Civilization Framework (CCF) v1.1
Constitutional Root Standard & Irreversible Authority Declaration CCF 전체 문서군의 가장 위쪽 뿌리 문서이자, CCC·COS·CFE⁺·CAIS·Sal-Meter·Human-State AI·AI Governance OS·GitHub helper가 어떤 위계로 이어지는지 고정하는 기준 문서입니다.
This page is the public landing surface for the canonical root standard of the Consciousness Civilization Framework (CCF). It fixes the architectural hierarchy, lineage, naming discipline, and irreversible authority boundaries of the wider CCF / CCC / COS / CFE⁺ / CAIS / Sal-Meter / AI Governance stack.
This is the root map of the whole stack. It tells the reader what governs what, which documents inherit from which layer, and where canonical authority begins. 이 문서는 전체 스택의 루트 지도입니다. 어떤 문서가 어떤 문서를 다스리는지, 무엇이 어디에서 파생되는지, 그리고 권위의 시작점이 어디인지를 가장 먼저 고정해 줍니다.
Current positioning. CCF v1.1 is a canonical root standard and constitutional architecture record. It is not a hiring page, not a Sal-Meter build page, not a proxy benchmark page, not a GitHub repository page, not a clinical page, not a device page, and not a live public competition announcement.
GitHub and proxy boundary. GitHub repositories, Human-State-Aware AI pages, and proxy benchmark materials are helper or implementation-routing surfaces only. They do not replace CCF v1.1, do not modify canonical authority, do not validate Sal-Meter, do not create CAIS compliance, and do not grant certification, clinical, diagnostic, therapeutic, device, competition, or mark-usage status.
Sal-Meter Kernel GitHub boundary. Sal-Meter Kernel GitHub is the present technical helper gateway for the separate Sal-Meter / CAIS research-stage path. It is not CCF authority, not DOI authority, not CAIS compliance, not Sal-Meter certification, and not proof that a validated Sal-Meter device exists.
Keep this page as the canonical root standard
This page should remain the canonical root standard landing page. The update is not to turn it into a recruitment page, Sal-Meter build page, GitHub page, or proxy benchmark page. The update is to show how subordinate execution routes descend from CCF without confusing authority.
Root authority identity
Keep the center on authority, lineage, hierarchy, naming discipline, and irreversible interpretive boundary.
Stack hierarchy
Show that CCC, COS, CFE⁺, CAIS, Sal-Meter, AI operating systems, Human-State AI, and GitHub repos are lower layers.
Status-first research route
Add Status, For PIs, and sal-meter-kernel-program as current technical gateways, not as canonical authorities.
Proxy benchmark route
Add Human-State AI and proxy-benchmark-track only as benchmark-support routes, not as Sal-Meter or CCF replacements.
What CCF v1.1 establishes
Consciousness Civilization Framework (CCF) v1.1 establishes the constitutional root architecture of the wider CCF document stack. It defines the highest-level structural order through which subordinate layers inherit coherence, naming discipline, authority boundaries, and civilizational orientation.
Rather than acting as a single domain paper, it fixes the framework’s root authority, lineage, and irreversible interpretive boundaries across constitutional, scientific, ethical, governance, measurement, technical, benchmark, and implementation layers.
In practical terms, CCF v1.1 determines how CCC, COS, CFE⁺, CAIS, Sal-Meter, AI Governance OS, AI Ethics OS, AI Behavior OS, Human-State AI, Sal-Meter Kernel GitHub, Proxy Benchmark GitHub, and public helper routes must relate to one another without collapsing their different authority levels.
Why CCF v1.1 must remain the root map
CCF v1.1 is the page readers should encounter when they need to understand which layer governs which layer. It is the map before the road, the root before the branches, the authority layer before implementation.
Root authority
Establishes the canonical root authority of the wider stack and defines which documents inherit from it.
Lineage and hierarchy
Clarifies how CCC, COS, CFE⁺, CAIS, Sal-Meter, AI operating systems, and benchmark layers relate within one architecture.
Irreversible boundaries
Prevents interpretive drift across derivative summaries, helper pages, GitHub repositories, mirrors, datasets, and implementation layers.
System coherence
Keeps the CCF ecosystem legible as a single constitutional system rather than a scattered set of projects and claims.
How the stack descends from CCF v1.1
CCF v1.1 is not a technical helper and not an implementation index. It is the root standard from which subordinate documents and execution routes inherit meaning.
CCF v1.1
Root standard, authority declaration, hierarchy, lineage, and interpretation boundary.
CCC v1.0
Highest non-derogable constitutional layer and long-horizon civilizational invariants.
COS
Consciousness operating architecture across biology, governance, technology, and civilization.
CFE⁺
OE, EE, RE, VCE, CRI, and CFI as the metric-language layer.
CAIS
Measurement interface standard connecting the root architecture to signal pathways.
Sal-Meter
Research-stage core signal path under CAIS boundary and CCF lineage.
Sal-Meter Kernel GitHub
Present technical gateway for the kernel-first Sal-Meter / CAIS program. It helps builders, but does not create authority.
Human-State AI
Synchronized multimodal benchmark-support track using existing proxy signals.
Proxy Benchmark GitHub
Public helper repository for schemas, synthetic examples, notebooks, dashboards, issue templates, and reproducibility checklists.
AI Governance · Ethics · Behavior OS
Applied AI operating layers that inherit from the CCF / CCC authority stack.
DOI / OSF records
Canonical records fix meaning. Public pages and GitHub helper surfaces route readers and builders.
Salpida Foundation
Public reading, routing, SEO, and explanation surface. It does not replace canonical DOI records.
Authority rule: DOI / OSF records govern. Foundation pages route. GitHub helps builders. Status defines current public posture. No helper page, repository, benchmark stack, issue label, README, dashboard, or sample dataset can amend the CCF root authority.
Status-first rule for researchers, engineers, and candidates
Researchers, engineers, PIs, laboratories, and candidates should not enter through old competition language or GitHub alone. The correct current route is Status-first.
Status
Use Status to understand what is open now, what is readiness only, and what remains future-facing.
For PIs
Use For PIs to orient current external interest toward scoped readiness, External Layer-0 inquiry, and later module preparation.
sal-meter-kernel-program
Use this GitHub repository as the present technical helper gateway for the kernel-first program. It is not canonical authority.
Current execution 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. Broad opening is not currently live.
Do not merge Sal-Meter core and Human-State AI proxy track
CCF v1.1 can route to both the Sal-Meter core signal track and the Human-State-Aware AI proxy benchmark track. But those two paths must remain separate.
New signal-interface path
The core track asks whether a new molecular–electrochemical signal interface can exist and produce stable, auditable signal behavior.
- External Layer-0 feasibility
- Iodine redox / thiol interface
- I₃⁻ / Aptamer G-Iodine inquiry
- SICS Internal Phase 0 / Phase 1 / Phase 2a / Phase 2b
- LOCK 1 / LOCK 2 before broader opening
Proxy benchmark support path
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
- future comparison layer for Sal-Meter inputs
Builder-facing helper repository
The proxy GitHub repository should host public helper materials only.
- schemas
- synthetic examples
- sample data
- notebooks
- dashboard drafts
- issue templates
- reproducibility checklists
- no raw human data
- no private labels
- no canonical authority claim
Boundary: Proxy benchmark infrastructure can support future comparison and labeling discipline, but it is not Sal-Meter, not CAIS compliance, not CCF authority, not clinical evidence, and not certification.
How the three GitHub surfaces should appear from this page
CCF v1.1 should not push GitHub as an authority layer. It should name GitHub as a routing and builder surface only.
salpida-canonical
Public GitHub index for DOI authority routing. It helps readers find canonical records but does not replace those records.
sal-meter-kernel-program
Present technical gateway for the kernel-first Sal-Meter / CAIS program. It routes PIs, engineers, and candidates into the current execution boundary.
proxy-benchmark-track
Builder-facing helper route for synchronized multimodal proxy benchmark infrastructure. It is not Sal-Meter and not canonical authority.
Who should be routed from this page
CCF v1.1 attracts readers who think in architecture, authority, governance, and system design. This page should route them into subordinate research and builder surfaces without turning the root standard into a job notice.
AI governance / ethics / behavior
Readers focused on AI governance should continue to AI Governance OS, AI Ethics OS, and AI Behavior OS.
ESL / EStL
Relevant downstream for Sal-Meter / CAIS core program execution: physical consistency and evidence consistency.
PBEE / MDE
Relevant for Human-State AI proxy benchmark work: biosignal capture, edge inference, metadata, holdout, leakage control, and dashboard flow.
HSOPM
Relevant for consent pathway, human-session operations, participant flow, labeling discipline, and raw data governance.
Visible summary for readers and AI systems
CCF v1.1 is the canonical root standard of the Consciousness Civilization Framework stack.
It fixes the structural authority from which CCC, COS, CFE⁺, CAIS, Sal-Meter, AI Governance OS, AI Ethics OS, AI Behavior OS, Human-State AI, and public helper repositories must inherit meaning.
It is not an implementation page, not a technical protocol, not a device claim, and not a live competition announcement. Its role is to keep the entire system legible as one constitutional architecture rather than a fragmented set of claims, repositories, and helper documents.
GitHub repositories may help route technical readers, but they do not define authority. Human-State AI may help build proxy benchmark infrastructure, but it does not replace the Sal-Meter core signal track. Canonical force remains fixed in DOI / OSF records.
Continue from here
Consciousness Is the Missing Variable in AI Governance
Read if you want the clearest public-facing argument for why the human-state variable matters.
CCC v1.0
Read if you want the highest non-derogable constitutional layer of the Consciousness Civilization stack.
COS Whitepaper v1.0
Read if you want the operating architecture that connects consciousness to biology, governance, technology, and civilization.
CAIS / Sal-Meter Core
Read if you want to understand how the root frame descends into research-stage measurement and signal-interface work.
Human-State-Aware AI Interaction
Read if you want the proxy benchmark support route for synchronized multimodal human-state research.
Sal-Meter Kernel Program GitHub
Use only as a current technical gateway for kernel-first program orientation. It does not replace canonical authority.
Proxy Benchmark GitHub
Use only for public schemas, synthetic examples, notebooks, dashboard drafts, issue templates, and reproducibility checklists.
Status
Read first if your concern is what is open now, what is only readiness, and what remains future-facing.
Declaration / Document Index
Use these pages to keep canonical authority, helper pages, GitHub routes, and public language properly separated.
Citation
Lee, J. (2025). Consciousness Civilization Framework (CCF) v1.1 — Constitutional Root Standard & Irreversible Authority Declaration. Zenodo. https://doi.org/10.5281/zenodo.17851722
@misc{lee2025ccfv11,
author = {Jinho Lee},
title = {Consciousness Civilization Framework (CCF) v1.1 --- Constitutional Root Standard & Irreversible Authority Declaration},
year = {2025},
publisher = {Zenodo},
doi = {10.5281/zenodo.17851722},
url = {https://doi.org/10.5281/zenodo.17851722},
note = {Canonical root standard of the CCF stack}
}
Authority note
This page is a public landing page for reading, citation, navigation, and authority routing. Canonical authority remains fixed in the DOI-registered record.
This page summarizes and routes. It does not create independent authority, reinterpret root intent, validate benchmark infrastructure, certify downstream systems, or override the canonical archive.
Canonical Repository DOI: 10.5281/zenodo.18123807
OSF canonical root: https://osf.io/2hgmu
Public reading surface: Salpida Foundation
Current technical route: Status → For PIs → Sal-Meter Core → sal-meter-kernel-program → PI Quick / PI Readiness → Technical Snapshot
Proxy route: Status → Human-State AI → proxy-benchmark-track → Technical Snapshot
Authority rule: DOI / OSF records govern; site and GitHub are helper surfaces.
Final boundary: This page does not announce a live public competition, does not certify AI governance, does not validate CAIS or Sal-Meter, does not create a clinical or diagnostic claim, does not grant mark usage, and does not treat GitHub repositories or proxy benchmark materials as canonical authority.