01
Origin condition
Why it exists
People often receive fragmented signals from body, attention, emotion, memory, environment, and relationships. Carbon Loop is the Human Experience OS beneath LumenBridge, a consent-based public face for noticing those relationships without turning reflection into diagnosis or surveillance.
Can a local-first reflection system help someone notice patterns while leaving interpretation and authority with the person?
02
Working system
What it does
- ◎Supports self-observation
Helps record and revisit experiences across body, attention, emotion, memory, meaning, and context.
- ⌁Connects patterns carefully
Surfaces possible relationships as prompts rather than declaring causes or diagnoses.
- ⎋Protects consent and exit
Local-first custody, revocable mandates, quiet defaults, and export/delete paths remain architectural requirements.
03
System anatomy
Architecture
Carbon Loop provides the private reflection runtime; LumenBridge is the softer public entry; Authority Capsules, local storage, prompts, and receipts protect the relationship.
Experience record
User-authored observations and context, stored locally by default.
Reflection engine
Questions, pattern prompts, summaries, and uncertainty labels.
Authority capsule
Consent scope, prohibited actions, renewal, export, and deletion rules.
LumenBridge surface
Quiet public-facing experience and language.
04
Present tense
Current state
Carbon Loop / LumenBridge is recorded as Stewarded at the Canopy stage. The inventory currently marks 4 artifact lanes Ready, 4 Partial, and 0 Missing.
B3 Tier 1 room draft · Core canon · Exploratory evidence · public candidate
05
Honest edges
Known limitations
- No diagnostic, therapeutic, predictive, or clinical effectiveness has been established.
- Self-reported records can be incomplete, biased, or emotionally difficult to interpret.
- Pattern suggestions may create false narratives unless uncertainty and alternative explanations stay visible.
- Sensitive data custody requires robust local security, export, deletion, and recovery design.
06
Claim boundary · v1.1.0
What we are—and are not—saying
A mature canon defines Carbon Loop as a consent-based local-first Human Experience OS with LumenBridge as its public face and explicit sovereignty requirements.
The system is not a medical device, therapist, diagnostic service, crisis service, truth detector, or proof that correlations in a personal record are causal.
07
Development memory
Ledger
B3-CL-001-01Carbon Loop and LumenBridge roles frozen as runtime and public face.
✓ AcceptedB3-CL-001-02Consent, local-first custody, reflection boundaries, and exit rights established as core requirements.
✓ AcceptedB3-CL-001-03Tier 1 Human Experience OS room drafted with non-diagnostic boundaries.
✓ DraftCurated project receipts · source-file binding and human review remain pending
08
Directional, revisable
Roadmap
Freeze the minimum private loop
Define capture, reflection, uncertainty, export, deletion, and mandate renewal.
Build a local prototype
Test usefulness and burden without cloud accounts or clinical positioning.
Conduct independent safety review
Invite privacy, accessibility, mental-health, and lived-experience critique before broader use.
10
B10 evidence trail
Featured evidence
Registry-grounded trail
No primary source package is bound yet. The public trail is limited to the verified field card and public Genome snapshot.
Carbon Loop / LumenBridge — Project Field Card
B4-generated visual identity card built directly from the reviewed constellation registry.
Open bound artifactCarbon Loop / LumenBridge — Public Genome Snapshot
Public-safe JSON snapshot of the current project registry or expanded Project Genome.
Open bound artifact11
Publication intake
Artifacts & sources
Carbon Loop canon
Human Experience OS architecture and sovereignty boundaries.
View archive recordarchive:intake/carbon-loop-canonLumenBridge public experience design
Public language and surface require one approved release candidate.
View archive recordarchive:intake/lumenbridge-public-faceLocal reflection prototype
No accepted end-to-end public prototype is represented.
View archive recordarchive:intake/carbon-loop-local-prototypeSource basis
archive:intake/carbon-loop/source-basisarchive-canonportal:project/carbon-loop@v0.4-b3planning-inventoryReview: Canon, claims, privacy, accessibility, and publication review · pending
12
Move with evidence
Next actions
Usefulness depends on keeping reflection distinct from diagnosis and control.
reviewReview the artifact registerSee which source packages, visuals, demonstrations, and public links are actually ready.
secondaryTrace related projectsFollow documented dependencies and neighboring systems without inventing connections.