Back to corpus
architecturetechnical paper candidatescore 40

N'Ko Inscription System Architecture

| Component | Configuration | Status | |-----------|---------------|--------| | iPhone Sensor Logger | HTTP Push to cloud | **WORKING** | | cc-mcs-headless | Cloud: `[ip]:8765` | **DEPLOYED** | | Data path | Phone → Cloud Daemon → Supabase | **ESTABLISHED** |

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

| Component | Configuration | Status | |-----------|---------------|--------| | iPhone Sensor Logger | HTTP Push to cloud | **WORKING** | | cc-mcs-headless | Cloud: `[ip]:8765` | **DEPLOYED** | | Data path | Phone → Cloud Daemon → Supabase | **ESTABLISHED** | | # | Sigil | Name | Detection Trigger | |---|-------|------|-------------------| | 0 | ߛ | Stabilize | Variance decreasing > threshold | | 1 | ߜ | Disperse | Variance increasing > threshold | | 2 | ߕ | Transition | Curvature peak > 1.5 | | 3 | ߙ | Return | Distance to known basin < 6.0 | | 4 | ߡ | Dwell | Time in basin > 1.5s | | 5 | ߚ | Oscillate | 3+ transitions between 2 basins at ≥0.2Hz | | 6 | ߞ | Recover | Return to basin 0.5-10s after transition | | 7 | ߣ | Novel | Distance from all basins > 10.0 | | 8 | ߠ | PlaceShift | Place class changes (requires place data) | | 9 | ߥ | Echo | Cosine similarity > 85% to historical z-vector | | Purpose | Path | |---------|------| | Claim Detector | `core/cc-inscription/src/detector/mod.rs` | | Claim Types | `core/cc-inscription/src/claims/` | | Sensor→Skeleton | `backend/cc-mcs/src-tauri/src/inscription_bridge.rs` | | Inscription Runner | `backend/cc-mcs/src-tauri/src/inscription_runner.rs` | | Main Daemon | `backend/cc-mcs/src-tauri/src/main_headless.rs` | **PHONE SENSOR TUNING (2026-01-05)**: Phone accelerometer produces noisier 63D z-vectors than mocopi skeleton. These thresholds prevent spam while enabling claim variety. ### Issue: Only Novel/Transition claims detected **Root cause**: Thresholds not calibrated for sensor data scale **Solution**: Adjust thresholds in `detector/mod.rs`, rebuild, redeploy

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.