Back to corpus
architecturetechnical paper candidatescore 44

Serenity Soother — Affinity Graph Architecture

**Document ID:** SS-ARCH-002 **Version:** 1.0.0 **Last Updated:** 2026-01-15 **Source:** `Desktop/SS/SerenitySoother/SerenitySoother/Core/Infrastructure/AffinityGraph.swift`

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document ID:** SS-ARCH-002 **Version:** 1.0.0 **Last Updated:** 2026-01-15 **Source:** `Desktop/SS/SerenitySoother/SerenitySoother/Core/Infrastructure/AffinityGraph.swift` A living graph of user relationships that evolves as users create and interact. Uses Locality-Sensitive Hashing (LSH) for O(1) matching at scale. | Type | Affinity | Behavior | |------|----------|----------| | Soul Mirror | 95-100% | Instant auto-share | | Kindred Spirit | 85-95% | Auto-accept on return | | Resonant Traveler | 75-85% | Preview before accept | | Parallel Path | 70-75% | Notify only | | Distant Echo | <70% | No connection | ### Problem Naive O(n²) comparison doesn't scale: - 1M users = 500 billion comparisons ### Configuration - `bucketThreshold`: 1000 users per bucket - `edgeCacheDuration`: 1 hour

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.