Nishi Family › Compare › Faith Social: private sign-up, circles and safe connection

Nishi Compare · capabilities, evidence and delivery

Faith Social: private sign-up, circles and safe connection

Compare capabilities and delivery evidence. Source discovery, qualification, deployment and accepted outcomes are separate; an open contract names work still to verify.

Nishi CONNECT for Latter-day Saints and all Christians vs Mutual and Christian Mingle and Hinge and Bumble and Facebook Groups and Discord and LDS Singles

Overview

The purpose, declared position and evidence coverage of this domain. Source presence and completed acceptance are different measures.

Where we are. MEASURED 2026-09-25 at admission. The faith-social matrix declares 24 capability rows (23 at admission, then the FS11 group-safety watch on the PM seat's request): at admission 13 cited an organ and symbol the connect board carries as present and 10 were watch contracts riding connect rungs; the generator re-measures presence on every publish and its count is the figure of record. Underneath: the live 11-page zero-JS app at /connect with OPAQUE login and a sealed inbox, the two-deep youth wall, the mission reconnection lane, the ward boundary and reciprocal matching -- and 0 real users (connect gauge 437/1000 on 2026-08-19). The September-2026 field: Mutual leads Latter-day Saint dating with a free core and optional Premium [mutual]; Christian Mingle states it runs no background checks [christianmingle]; Hinge ships Selfie Verification with liveness checks, a Comment Filter and nudges [hinge]; Bumble ships Photo and ID Verification, Share Date and a BFF friendship mode [bumble]; Tinder took dating offline with in-app Events in 26 markets by September [tinder-press]; Discord went teen-by-default and ships a Family Center for parents [discord-teen] [discord-safety]; Facebook Groups carry admin and moderator roles [fbgroups]. No rival on the bar builds circles by consent and vouching, serves youth under a two-adult rule, or signs a member up without keeping identity evidence.

Where we need to go. OPERATOR 2026-09-25: from the first byte up, people sign up with full privacy and security on our platforms, every requirement logged through the backlog PM process onto the right compare domains, and a cross-compare ladder up to state of the art that beats the dating and social sites, so Latter-day Saints can sign up and engage appropriately with each other, growing from Latter-day Saints to other Christians, structured as circles -- immediate family, mission family, ward family, stake family -- up until an LDS boy can talk and be friends with an LDS girl on the site. Standing scope (operator 2026-07-01): community, reconnection and youth belonging, never congregation administration or official Church records, never proselytizing, never speaking for or competing with the Church's own apps, every connection feature free forever, the two-deep youth wall a shipping criterion no rung may trade away [church-gh20], content-blind serving, fail-closed CSAE reporting, no ads to minors, each church's preferred name. Dating lanes open only between adults.

The unit. 1 u = one measured session-leg (organ plus gate plus live flip), the standing calibration.
Where we are: 17 of 23 rows present at the first publish, 0 users. Measured by the generator at 1790356550: the safety architecture (two-deep wall, content-blind serving, sealed inbox), the community engines (groups, events, reconnection, ward boundary, matching) and four contracts sibling seats landed this hour (sign-up, circles, one family account, cohort seeding) are present in source; verified personhood, faith at equal fidelity, durable messaging, date safety, trained models, native apps and the group moderation queue (FS11, added after the first publish) are open watches. Source presence is not a running product: 0 real users.
Cost to safe groups on this board: 2 u. Through M1: FS11 group safety, the one M1 rung this board owns. Private sign-up, one family account, circles, faith at equal fidelity, durable messaging and the seeded cohort are owned, costed and ranked once on connect M1 (CN13 2 u, CN5 1.5 u, CN14 2 u, CN15 1 u, CN6 1.5 u, CN3 2 u: the same 10 u these rows carried here before the 2026-09-25 consolidation).
Cost to safe dating between adults on this board: 3.5 u. Through M2: FS8 the date-safety check-in (1.5 u) on top of M1. A verified person storing nothing is connect CN18 (2 u, connect M2) and trained matching and moderation on content-blind signals is connect CN4 (4 u, connect M4), each owned and ranked once there.
Cost to every pocket on this board: 0 u. The native shell over the same core is connect CN2 (4 u, connect M3 at version 1.0), owned and ranked once there; this board keeps no milestone for it since the 2026-09-25 consolidation.

Research bar. Mutual (the Latter-day Saint field leader) is measured on free core, optional Premium, millions of members. Theirs: leading LDS dating app since 2016, tens of thousands of couples [mutual]. Ours: ours adds friendship and circles beyond dating, youth served under the wall, zero paywall -- connect CN13 CN14 CN3.

Research bar. Hinge (verification and nudges) is measured on Selfie Verification with liveness checks, Comment Filter. Theirs: shipped [hinge]. Ours: connect CN18 proves a person and an age band while storing nothing.

Research bar. Bumble (date safety) is measured on Photo and ID Verification, Share Date, BFF. Theirs: shipped [bumble]. Ours: connect CN18 and FS8.

Research bar. Tinder (online to offline) is measured on in-app Events, 26 markets by September 2026. Theirs: shipped [tinder-press]. Ours: our events engine is present with the youth wall; the cohort is connect CN3.

Research bar. Discord (teens and parents) is measured on teen-by-default and Family Center. Theirs: shipped [discord-teen] [discord-safety]. Ours: our two-deep wall is structural; guardian visibility of youth friendships rides connect CN14.

Research bar. LDS Singles (Latter-day Saint dating site) is measured on Join Free, browse profiles, premium upgrade, iOS and Android apps, no background checks. Theirs: read and pinned 2026-09-25 [ldssingles]. Ours: ours adds circles, games, activities, language, service and gardening beyond dating, no third-party trackers and a verified person storing nothing; the LDS Singles column is coded on the matrix from its App Store listing (Premium USD 49.99 a month for unlimited messaging) and its operator's safety, privacy and terms pages, read and pinned 2026-09-25 [ldssingles-appstore] [ldssingles-safety] [ldssingles-privacy] [ldssingles-terms].

Latest recorded release

2026-09-28 · FS8

BEST-IN-CLASS BASELINE FOR THE SEALED PLAN: the predecessor's box had RFC 9180's shape and not its bytes (no labeled extract, no suite id), and no HPKE existed anywhere in the estate (nx_shelltool grep for func hpke over buildroot/runtime, corpus_complete=1, 0 matches). Built runtime/_hdl_build/nx_hpke_lib.nx (base mode; DHKEM(X25519, HKDF-SHA256), HKDF-SHA256, ChaCha20Poly1305; composes nx_x25519, nx_hkdf and nx_chacha20_poly1305, restates none) and its gate nx_hpke_lib_gate, which reproduces the RFC's own Appendix A.2.1 vectors byte for byte [rfc9180]: 47/47 GREEN on its first build (nx_sov_build_run --qualify job 1790621878), shipped by /api/build job 1790622204 and /api/promote job 1790622233 (sha 839be23c), registered (callable 1), bite-proven twice (job 1790622253 a comparison mutant, job 1790622335 an aimed mutant in the nonce computation, both killed, restore byte-identical 17483 B). cds_plan_seal and cds_plan_open now compose hpk_seal_base and hpk_open_base with info = the FS8 label and aad = the sharer's account id; the bespoke HKDF-and-cseal box is retired from the lib. nx_connect_datesafety_gate re-measured 122/122 GREEN on the HPKE box (job 1790622191), re-shipped by /api/build job 1790622408 and /api/promote job 1790622428 (sha 63163eba), and /api/gate_run on both promoted binaries reads exit_code 0, 122/122 and 47/47. Rostered; knowledge/organ_gate.conf declares nx_hpke_lib to nx_hpke_lib_gate; its evidence row joins knowledge/compare/faithsocial.gates. Shipped, gates 122/122 and 47/47, awaiting acceptance.

Release history and work log

Release entries describe recorded changes; they do not establish that every capability passed evaluation.

26 of 29 capability source symbols found|1 of them authored stronger-claims|3 open|coverage 896/1000|adoption 21 full / 5 partial

Evidence profile — what the gaps on this board actually are

Measured by nx_swcompare_evidence, read back by nx_evprofile_lib. Every figure is a count with its denominator — there is deliberately no score, no grade and no percentage anywhere in this band, because a stored scalar is a field a seat can edit and a counted partition is not.

evidence|grounded 26/26|unsupported 0|gates green 3/3|proven able to fail 3/3|never bitten 0|green at 0/0 0|open gaps 3|of them unnamed 0|of them proof withheld 0|flips ready 11

proven able to fail counts the gates that have a RECORDED RED — nx_gate_bite mutated the gate subject, rebuilt it, watched the gate go red, and that record is inside the shared TTL. never bitten is its complement over the same denominator: those gates ran and were green, and nothing has ever shown them able to detect anything, so their green is a statement about this run and not about the gate. green at 0/0 is a separate and much weaker observation — the gate printed GREEN on a zero denominator, so its own tooth counter says it examined nothing. A gate can be green, non-zero, and still never bitten; that is the common case and it is now visible instead of implied.

partition: grounded + unsupported = 26 vs present 26 · named + unnamed + withheld = 3 vs open 3 · both reconcile

liar-kill conj=GPQN · all four conjuncts held

graded document: BUILDROOT tree, 24250 bytes · gates map: PRIMARY · stamped 10d 0h ago · STALE against the shared TTL of 604800s — this is evidence about a build nobody can vouch for now · source ../knowledge/status/evstamp_faithsocial.verdict

Gap classWhat it is, and the work it names
FLIP-READYA watch contract symbol is now present in the organ it named: the cell can flip on a pure data edit with no new code. These are the cheapest closures on this board and they belong before any new work.
STALEThis profile is older than the shared TTL, or its clock ran backwards. It is reported as unusable rather than as fresh, because being wrong in the direction of refusing is the safe direction.
This band reports the referee counts. The per-axis worklist rows — which axis is unsupported, which watch is ready to flip, which gap is unnamed — are printed by nx_swcompare_evidence faithsocial itself and are not carried on the stamp, so this page names the classes and the producer names the rows. That split is stated rather than hidden: a count without a worklist is not actionable, and this band is honest about which half of that it is.

Production map

Follow the dependencies, declared acceptance criteria and recorded priorities. Inspect source binding before treating a rank as executable work.

Ranking source binding: STALE_OR_INVALID_BINDING. Recorded priorities require current acceptance evidence and resource checks before execution.

Recorded ranking withheld

Retained ranking is not bound to the current plan and matrix: STALE_OR_INVALID_BINDING. Historical data remains retained. Refresh the ranking after resolving the input differences. Latest execution outcome is unverified.

Declared roadmap — contract, acceptance, executor, effort

Ladder to SOTA

Two dated targets, and every rung's role toward them. Best in class is the proven, deployed leader today; the frontier is the research edge as of its month. Each target is dated by a sotabar row and judged against the current month by the bar-age ruler (FRESH, ATTESTED with the fallback month named, or refused). Each rung is substrate (what the target's own methods consume), an arm (a sovereign arm that triangulates without competing for the number), a contender (its done-rule is a number against the target) or superseded (kept as capability, retired as a claim), and carries the rungs it stands on.
best-in-class (T-BIC-FAITHSOCIAL), dated by SB-FS-APPS = 2026-09 ATTESTED. Every capability the September-2026 field ships for sign-up, verification, date safety, groups, events and messaging present on Nishi CONNECT and free forever, with a sign-up that keeps no identity evidence and the two-deep youth wall intact ref tinder-press
frontier (T-FRONT-AGEBAND), dated by SB-FS-AGE = 2026-09 UNATTESTED. A person and an age band proven as an evaluated claim with nothing identifying stored, and youth SERVED behind a structural two-adult wall rather than excluded; no rival on the bar serves youth this way; since the 2026-09-25 consolidation its climber is connect CN18 under T-FRONT-CONNECT, and no rung on this board places on it until the ranker resolves a cross-board role ref arxiv-age
frontier (T-FRONT-CIRCLES), dated by SB-FS-MATCH = 2026-08 UNATTESTED. Concentric consent-and-vouch circles from immediate family to mission, ward and stake and on to other Christians, with reciprocal matching that is optimal for both sides and scam defense that never reads a message; since the 2026-09-25 consolidation its climbers are connect CN14, CN15 and CN4 under T-FRONT-CONNECT, and no rung on this board places on it until the ranker resolves a cross-board role ref arxiv-dating
RungCloses withDefinition of done (pre-declared)ExecutorEst.
Date-safety check-in between adults (NEW contract, proposed connect rung) (FS8)
after connect:CN18
cds_date_checkinAn adult shares a planned date with a trusted contact, checks in, and blocks or reports in one step, with nothing about the date readable by the server; a minor can never open a date lane so no check-in exists for one; the gate proves share, check-in, a missed check-in escalating to the trusted contact, and the minor refusal; graded against Bumble Share DateOrgan1.5 u
Group safety graded against Facebook Groups and Discord (NEW contract, proposed connect rung) (FS11)cgm_mod_queueA group's owner and admins work a moderation queue of member reports carried as metadata only (reporter, reason code, target, time -- never message plaintext) and act on each (warn, mute, remove), every action logged and an abuse report routed fail-closed to the CSAE sink; the queue composes the landed connect organs -- roles (grp_can_post), events (ev_rsvp), the two-deep youth wall on join AND leave (room_admit), content-blind abuse signals (abuse_score), fail-closed CSAE reporting (sink_fails) and no ads to minors (ca_should_serve); the gate proves an admin sees and resolves a planted report with no plaintext in the queue, a youth group left with one adult refuses the change, a CSAE report whose sink fails refuses to proceed, and a group holding a minor serves no ad; graded against Facebook Groups admin and moderator tools and Discord server moderationOrgan2 u

Milestones

MilestoneRungsCumulative
M1 · Gather safely in groups (private sign-up, one family account, circles, faith, durable messaging and the seeded cohort are connect M1: CN13 CN5 CN14 CN15 CN6 CN3)FS112 u
M2 · Safe dating between adults (the verified person is connect CN18 on connect M2; trained matching and moderation is connect CN4 on connect M4)FS83.5 u
RungRoleTowardStands onWhy
FS8contenderT-BIC-FAITHSOCIALconnect:CN18 DONEdate safety is what Bumble Share Date ships
FS11contenderT-BIC-FAITHSOCIAL-group safety is where Facebook Groups and Discord lead today; ours moderates without reading a message and holds the youth wall in every group
Ladder verdict. LADDERED. Targets, rung roles and bars are counted in the tables below, each partition re-derived beside its total. Bars read STALE against the current month 2026-10.
Ladder verdict, counted (17 rows, more than the 12-row disclosure bar)
Ladder verdict, counted
ClassCountNote
targets3sotatarget rows on the plan
best in class1targets whose class is best-in-class, by code
frontier2targets whose class is frontier, by code
undated0targets naming no bar that exists
bad class0targets whose class is neither word
duplicate0target ids an earlier row already carries
rungs2rung rows on the plan
placed2rungs carrying a rungrole row
unplaced0rungs with no role toward any target
bad role0rungrole rows naming a role the ladder does not know
bad target0rungrole rows naming a target no sotatarget row declares
rungs, summed2RECONCILED: the parts sum to the total 2
substrate0what the target's own methods consume
arm0a sovereign arm that triangulates without competing for the number
contender2its done-rule is a number against the target
superseded0kept as capability, retired as a claim
placed, summed2RECONCILED: the parts sum to the total 2
Bar freshness, counted
ClassCountNote
bars3sotabar rows on the plan
fresh0the bar month is the current month
attested1an older bar with a this-month barscan reporting no newer entry
stale0a this-month scan saw a newer month the bar ignores
unattested2nobody looked this month
malformed0a sotabar row missing a field
duplicate0bar ids an earlier row already carries
bars, summed3RECONCILED: the parts sum to the total 3
current month2026-10the month every bar is judged against
Treatment verdict. NOT DECLARED. No rung on this board declares its three-step treatment (a treat row naming the MCP row, the API route, the primitive it composes, the workflow that composes it and the agent beat that runs it); the ranker labels every rung TREATMENT-UNDECLARED until it does.

Inspect a rung and its prerequisites

Declared nodes 2. Rank input binding: STALE_OR_INVALID_BINDING. Dependency order is authored. Implementation, acceptance evidence, authority and resource readiness are unverified. No action is recommended or dispatched here.

Plan SHA-256 404087d3c4cff802686efd10867d95d64bd8593e657c9f8e1f860ffe3f2ef55c. Target rows 3; role rows 2. Existing risks and release worklog retain their own scope; no node completion is inferred.

Runtime observation coverage: 0 of 2 rungs have current, identity-bound execution observations. Observation may report RED. Accepted completion remains unknown; source presence, qualification and deployment do not establish it.

Use Enter or Space on a rung to inspect its contract. Prerequisite links locate another rung in this list; open its summary to inspect it. Estimates are authored effort, not forecasts.

  1. FS8 — Date-safety check-in between adults (NEW contract, proposed connect rung)

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: cds_date_checkin

    Acceptance: An adult shares a planned date with a trusted contact, checks in, and blocks or reports in one step, with nothing about the date readable by the server; a minor can never open a date lane so no check-in exists for one; the gate proves share, check-in, a missed check-in escalating to the trusted contact, and the minor refusal; graded against Bumble Share Date

    Authored effort: 1.5. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

  2. FS11 — Group safety graded against Facebook Groups and Discord (NEW contract, proposed connect rung)

    Prerequisites: None declared; this does not establish execution eligibility.

    Contract: cgm_mod_queue

    Acceptance: A group's owner and admins work a moderation queue of member reports carried as metadata only (reporter, reason code, target, time -- never message plaintext) and act on each (warn, mute, remove), every action logged and an abuse report routed fail-closed to the CSAE sink; the queue composes the landed connect organs -- roles (grp_can_post), events (ev_rsvp), the two-deep youth wall on join AND leave (room_admit), content-blind abuse signals (abuse_score), fail-closed CSAE reporting (sink_fails) and no ads to minors (ca_should_serve); the gate proves an admin sees and resolves a planted report with no plaintext in the queue, a youth group left with one adult refuses the change, a CSAE report whose sink fails refuses to proceed, and a group holding a minor serves no ad; graded against Facebook Groups admin and moderator tools and Discord server moderation

    Authored effort: 2. Executor kind: Organ. Responsible, accountable and verifier not established. Inspect retained worklog.

    Runtime observation: UNKNOWN; outcome UNKNOWN; observed epoch -1. Declared owner: . Receipt , SHA-256 . Identity-bound observation is not accepted completion. Qualification and deployment remain unverified by this projection.

Learning and practice paths

No structured learning path is declared for this plan. Existing research, roadmap and worklog remain available above.

Rung dossiers — every record that bears on a rung, in one place

Joined by symbol, never typed. Each dossier is assembled on every publish from the rows this board already carries: the plan's rung row, the matrix row that carries its contract symbol (its status re-measured by the one symbol ruler), the gate the organ declares and the verdict the evidence referee recorded on its last run, the reference marks in the rung text, the design rows that name the rung and the work log filed against it. The capability matrix links each cell to its dossier and each dossier links back to its cell and forward to the rungs it stands on; a dependency naming no rung on this plan is written as UNRESOLVED rather than linked. Absences are named: NO-MATRIX-ROW, NO-GATE-DECLARED, UNRECORDED.
Gate verdicts: UNSTAMPED — no per-gate verdict artifact is published for this domain yet (nx_swcompare_evidence faithsocial writes it beside its stamp); every gate below reads UNRECORDED until it runs.
Gate declarations: knowledge/organ_gate.conf read from this working directory (1 rows) and from the estate root (196 rows); rows in both counted once: 0; declarations read: 197. Every declaration in either copy counts, so a stub beside the publisher can never hide the root.
FS8 Date-safety check-in between adults (NEW contract, proposed connect rung) · cell LANDED · gate UNRECORDED
Contractcds_date_checkin · executor Organ · 1.5 u · stands on connect:CN18 (UNRESOLVED: no such rung on this plan)
Definition of doneAn adult shares a planned date with a trusted contact, checks in, and blocks or reports in one step, with nothing about the date readable by the server; a minor can never open a date lane so no check-in exists for one; the gate proves share, check-in, a missed check-in escalating to the trusted contact, and the minor refusal; graded against Bumble Share Date
Matrix cellDate-safety check-in between adults (share a date, block and report in one place) · runtime/_hdl_build/nx_connect_datesafety.nx · LANDED decl
Gatenx_connect_datesafety_gate · UNRECORDED — no recorded verdict for this gate (it is declared for the organ but the evidence referee's last run did not record it: it is not on this board's gates map, or the referee has not run since the per-gate record shipped)
Work log2026-09-25 queue INTAKE 1790355006 routed by nx_intake_route (operator-seat, epoch 1790356663) from pm-seat: R6 of parent REQ 1790355000: beat the dating sites (Mutual, Hinge, Bumble, Tinder, Match) on privacy, safety, verification and connection quality -- consented intent lanes between adults only with a m -- sponsor intake-1790355006 plus2
2026-09-28 land W17 SEAT DATE-SAFETY (resumed after the 12:39 CDT outage killed the first run): the predecessor had landed runtime/_hdl_build/nx_connect_datesafety.nx (cds_date_checkin with the own-account verbs, never compiled), knowledge/connect_datesafety.conf (lead_max_s 2592000 calibrated from Tinder Share My Date, grace_s 0 UNSOURCED) and six mirrors, and died 3631 bytes into the gate. This seat compiled the lib for the first time ('match' is a NishiLang keyword, renamed matched in cds_block_report), corrected two header claims the mirrors did not carry as written (the iOS 27 guide does not state end-to-end encryption, the iOS 17 newsroom does; the Noonlight claim now reads from Noonlight's own home page), wrote nx_connect_datesafety_gate (48355 B, 122 teeth, gv_kv values last before the verdict) and measured it: nx_sov_build_run --qualify job 1790620368 122/122 GREEN; shipped by /api/build job 1790620647 (src_path the gate, sha f1feb09f) and /api/promote job 1790620710 with expect_sha256, registered job 1790620729 (callable 1), nx_offc_install promoted, /api/gate_run job 1790620749 on the PROMOTED binary exit_code 0 verdict GREEN 122/122. Non-vacuity: nx_gate_bite job 1790620471 killed a compiling comparison mutant (restore byte-identical 37827 B), and a planted sharer-band defect turned the gate RED 119/122 on exactly the minor-by-name, refusal-with-a-lane-in-hand and odd-band teeth (job 1790620875); restored from knowledge/bank/nx_connect_datesafety.nx-20260928 (nx_filehash cmp identical, sha a4b78f30) and back to 122/122 GREEN (job 1790620946, a build-cache hit on the promoted bytes). Rostered in knowledge/gateroster.conf; knowledge/compare/faithsocial.gates created with its row. Shipped, gate 122/122, awaiting acceptance.
2026-09-28 measure THE BAR, read 2026-09-28 from mirrored bytes: Bumble Share Date sends a meetup's details to trusted contacts and updates them in real time, with no check-in and no escalation described [bumble-sharedate]; Tinder Share My Date is one link carrying location, date, time and a photo of the match, up to 30 days ahead and editable [tinder-sharemydate]; Apple Check In (iOS 27) offers an After-a-timer mode for meeting someone new, Add Time and Cancel, and on a failed check-in shares location, signal, battery and optionally the route [apple-checkin], end-to-end encrypted per the iOS 17 newsroom [apple-ios17]; Noonlight sells a Dispatch API for emergency response with Tinder in its customer row [noonlight]. WHERE OURS EXCEEDS: nothing about the date is readable by the server (the plan is sealed on the device to the contact's X25519 key; the gate's census of the state image and the contact's segment files finds no word of it, and the image does not hold who the date is with); there is no location field at all, by construction; the escalation is the sharer's own franked message through the existing messaging path, so a report of it is provable; a minor is refused by name and no check-in ever exists for one; block and report are one step. WHERE OURS TRAILS: no automatic arrival detection (Apple's When I Arrive needs location, refused by design); no emergency-services dispatch (Noonlight); no live location for the contact on a failed check-in; and the contact must already hold an accepted relationship lane, a consent guard that is also friction the rivals' open links do not have. Values from the promoted gate: plan 79 B sealed to 127 B, escalation 49 B franked to 129 B, state image 2080 B for five shares, lead_max_s 2592000, grace_s 0.
2026-09-28 queue OPEN after this leg, in order: (1) the front-door verbs date_share, date_checkin and date_block_report (with date_extend, date_cancel, date_update and date_plan) are requested of FRONTDOOR-FINISH on connect.plan row 1790621000; they land UNWIRED until the alpha daemon holds the date-safety block beside its room table, and the pure decision date_admit over cds_admit can be wired today; (2) the escalation sweep is a server beat (cds_due, then cds_escalate with cds_channel_verdict at delivery), owed to the daemon owner, not a user verb; (3) the device side (cds_plan_seal and mfr_frank at share time) needs the contact's published X25519 key from the key directory the sealing rung (connect CN7, wave 16) is taking live, and an ephemeral secret from the device CSPRNG; (4) the sealed box has the shape of RFC 9180 HPKE base mode but is not byte compatible (no labeled extract, no suite id) -- a rung to adopt the standard key schedule when an HPKE lib exists; (5) grace_s stays UNSOURCED at 0, the strictest line, until a rival page publishes one; (6) no location, no arrival detection and no dispatch are design refusals, kept on the trail list. The FS8 matrix watch flips on the next regen because the symbol exists in the named organ; the flip is the receipt, the gate is the proof.
2026-09-28 land BEST-IN-CLASS BASELINE FOR THE SEALED PLAN: the predecessor's box had RFC 9180's shape and not its bytes (no labeled extract, no suite id), and no HPKE existed anywhere in the estate (nx_shelltool grep for func hpke over buildroot/runtime, corpus_complete=1, 0 matches). Built runtime/_hdl_build/nx_hpke_lib.nx (base mode; DHKEM(X25519, HKDF-SHA256), HKDF-SHA256, ChaCha20Poly1305; composes nx_x25519, nx_hkdf and nx_chacha20_poly1305, restates none) and its gate nx_hpke_lib_gate, which reproduces the RFC's own Appendix A.2.1 vectors byte for byte [rfc9180]: 47/47 GREEN on its first build (nx_sov_build_run --qualify job 1790621878), shipped by /api/build job 1790622204 and /api/promote job 1790622233 (sha 839be23c), registered (callable 1), bite-proven twice (job 1790622253 a comparison mutant, job 1790622335 an aimed mutant in the nonce computation, both killed, restore byte-identical 17483 B). cds_plan_seal and cds_plan_open now compose hpk_seal_base and hpk_open_base with info = the FS8 label and aad = the sharer's account id; the bespoke HKDF-and-cseal box is retired from the lib. nx_connect_datesafety_gate re-measured 122/122 GREEN on the HPKE box (job 1790622191), re-shipped by /api/build job 1790622408 and /api/promote job 1790622428 (sha 63163eba), and /api/gate_run on both promoted binaries reads exit_code 0, 122/122 and 47/47. Rostered; knowledge/organ_gate.conf declares nx_hpke_lib to nx_hpke_lib_gate; its evidence row joins knowledge/compare/faithsocial.gates. Shipped, gates 122/122 and 47/47, awaiting acceptance.
2026-09-28 measure AFTER THE LEG: nx_swcompare_evidence faithsocial (job 1790622684) verdict=MEASURED-HONEST, gates_green=3/3 over knowledge/compare/faithsocial.gates (nx_connect_datesafety_gate 122/122, the FS11 sibling's nx_connect_groupmod_gate 145/145, nx_hpke_lib_gate 47/47), present_axes 26 all grounded, 3 absent named; the date-safety axis reads LANDED-UNFLIPPED (the watch cell measures cds_date_checkin present; converting the watch row into a claim with a Nishi code is a board decision awaiting acceptance, not taken here). nx_compare_rank faithsocial rungs 2 done 2 open 0, both FS8 and FS11 in FINISH as LIB-UNCENSUSED (imported only by their gates until the front door wires the verbs requested on connect.plan row 1790621000); nx_ladder LADDERED; nx_barfresh FRESH; nx_compare_refs_gate fleet 43/45 RED on two provenance-redirect ratchets naming pmdash, automation, search and datavis rows, with mirrors-exist, pins-match and cited-inline PASS across 2241 rows including this seat's six new faithsocial refs. One more trail item read from the Apple guide mirror: Apple prompts the person before a failed Check In notifies the friend and publishes no window, while ours escalates at deadline plus grace with no server-side prompt -- the device should prompt before the deadline, and grace_s stays UNSOURCED at 0.
FS11 Group safety graded against Facebook Groups and Discord (NEW contract, proposed connect rung) · cell LANDED · gate NO-GATE-DECLARED
Contractcgm_mod_queue · executor Organ · 2 u · stands on nothing
Definition of doneA group's owner and admins work a moderation queue of member reports carried as metadata only (reporter, reason code, target, time -- never message plaintext) and act on each (warn, mute, remove), every action logged and an abuse report routed fail-closed to the CSAE sink; the queue composes the landed connect organs -- roles (grp_can_post), events (ev_rsvp), the two-deep youth wall on join AND leave (room_admit), content-blind abuse signals (abuse_score), fail-closed CSAE reporting (sink_fails) and no ads to minors (ca_should_serve); the gate proves an admin sees and resolves a planted report with no plaintext in the queue, a youth group left with one adult refuses the change, a CSAE report whose sink fails refuses to proceed, and a group holding a minor serves no ad; graded against Facebook Groups admin and moderator tools and Discord server moderation
Matrix cellGroup moderation queue, content-blind (admins act, CSAE fail-closed, youth wall) · runtime/_hdl_build/nx_connect_groupmod.nx · LANDED decl
GateNO-GATE-DECLARED — knowledge/organ_gate.conf carries no row for nx_connect_groupmod; declare nx_connect_groupmod TAB <gate> and the ship loop proves it and the verdict lands here.
Work log2026-09-25 land FS11 declared on the PM seat's request for operator child R7 (beat Facebook Groups, Instagram and Discord on groups, privacy and safety; its router could not place R7 because no faithsocial rung spoke groups, moderation, CSAE or ads to minors): contract cgm_mod_queue on runtime/_hdl_build/nx_connect_groupmod.nx, a content-blind moderation queue composing the landed connect group, events, youth-room, abuse, CSAE and ads organs, graded against Facebook Groups admins and moderators and Discord server moderation; matrix row added (FacebookGroups Best from the pinned help page, Discord Yes not re-read today), rungrole contender for T-BIC-FAITHSOCIAL, M1 now FS1 FS2 FS3 FS4 FS6 FS7 FS11 at 12 u (M2 19.5, M3 23.5); nx_ladder re-run LADDERED 11 of 11 placed; nx_compare_rank job 1790357546 open=5 and the TARGET 0.1 critical path is FS11 alone (FS4 and FS6 flipped done as sibling seats declared cfa_tradition_admit and msg_store_append). OPEN: cgm_mod_queue and FS8 cds_date_checkin are new contracts owned on this board until the BOARD or SYNC seat adopts them onto connect.plan and connect.matrix; the PM seat can now re-route R7 to FS11
2026-09-25 queue INTAKE 1790358601 routed by nx_intake_route (operator-seat, epoch 1790360391) from ys-pm-seat: Y1 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): youth connect around the world and have fun, one to one a -- sponsor intake-1790358601 plus2
2026-09-25 queue INTAKE 1790358603 routed by nx_intake_route (operator-seat, epoch 1790360420) from ys-pm-seat: Y3 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): minors never harm minors -- no bullying and no inappropri -- sponsor intake-1790358603 plus2
2026-09-25 queue INTAKE 1790358606 routed by nx_intake_route (operator-seat, epoch 1790360466) from ys-pm-seat: Y6 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): the platform is not a babysitter -- no monitoring. No hum -- sponsor intake-1790358606 plus2
2026-09-25 queue INTAKE 1790358610 routed by nx_intake_route (operator-seat, epoch 1790360523) from ys-pm-seat: Y10 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): report abuse without surveillance. A recipient can repor -- sponsor intake-1790358610 plus1
2026-09-28 land W17 SEAT GROUP-MODERATION: cgm_mod_queue shipped in runtime/_hdl_build/nx_connect_groupmod.nx (30981 B; a pure core with no main, no allocation and no clock) with its gate nx_connect_groupmod_gate 138 of 138 GREEN, promoted by nx_organ_ship sha 492b1c6c (first ship 95840e2f at 123 of 123; the second added the ban and replay teeth), served GREEN through /api/gate_run (138 of 138), registered on the MCP surface, _offc twin installed, rostered in knowledge/gateroster.conf. The done-rule tooth by tooth: an admin sees and resolves a planted report on a franked message whose sender mfr_report_verify proved, and a clock-built canary appears in no byte of the queue's context, report rows or action rows while the same census finds it in an incumbent-style row that copies the post; a youth group left with one adult refuses the change (room_may_leave on the group roster and on every youth event roster the member holds); a CSAE report whose sink model fails its first attempt refuses every action, dismissal included, until cgm_csae_retry delivers it; a group holding a minor serves no ad to any viewer (ca_should_serve with the wall set). The brief's neg-controls: a member and an outsider read an empty queue while the admin reads the same report; a removed member cannot post or RSVP; a reversal restores posting with both rows kept, byte-identical to how they were written. Added after reading the rivals: a report naming an admin is withheld from that admin, a timed mute, a removal that is a ban until reversed by someone of at least the remover's rank, and replay (cgm_load_report and cgm_load_action rebuild a context from stored rows that answers every queue and posting read identically and refuses out-of-order history). Composes grp_can_post, grp_remove, grp_add, ev_rsvp, ev_cancel, room_admit, room_may_leave, abuse_score, sink_fails, ca_should_serve, mfr_report_verify and mfr_report_route; the two rules it restates are bound by teeth (cgm_may_moderate agrees with grp_remove on all 36 ordered pairs of a six-person roster; cgm_signal_flags reproduces the verifier's ten-account population). Non-vacuity: nx_gate_bite killed 4 compiling mutants with byte-verified restores (a position sweep, and aimed sites in the CSAE check, the group-roster youth wall and the ban check). Graded against pages fetched, read and pinned today, Facebook Groups Manage a group [fbgroups-manage] and Discord Auto Moderation [discord-automod]: both moderate by reading content, and both automate more (keyword and criteria automation, post approval, action notes), which the matrix row states as the gap. Board after the land: nx_compare_rank faithsocial rungs 2 done 2 open 0 (both FINISH, LIB-UNCENSUSED until the import census re-runs), nx_ladder LADDERED, nx_barfresh FRESH, scoped regen job 1790621316 GREEN (index 275213 B, api.json 52672 B, the row measures nishi 1), nx_page_verify job 1790621363 GREEN a11y-issues 0 (static checks, browser rendering unverified). Shipped, gate 138 of 138, awaiting acceptance.
2026-09-28 land W17 GROUP-MODERATION addendum to row 1790621440: reporting is now IDEMPOTENT under a client retry (cgm_find_open: a report matching an open row by group, reporter, target, reason and franking reference returns that row, so a retried member, message or CSAE report never duplicates a row or makes a second sink attempt, a repeated signal returns the open system report, and a fresh report after a decision files a new row), bite-proven by an aimed kill in cgm_report (5 kills in all). Re-shipped by nx_organ_ship sha b5386d1e, 145 of 145 GREEN, served GREEN through /api/gate_run (14724 B under the 16384 B capture cap, not truncated), with one NAMED loss approved by its artifact-bound token (the tooth 'a full report table refuses by name' renamed 'a full report table refuses a new report by name', because a retry of a filed report now answers with its row) and the behaviour change reviewed against the retained observation (review record knowledge/status/harness/review-nx_connect_groupmod_gate-b5386d1e.record, sha256 b53a1d8e). Scoped regen job 1790622247 GREEN (index 281578 B, api.json 52712 B); the matrix note and knowledge/gateroster.conf carry the 145 figure and the b5386d1e sha. Shipped, gate 145 of 145, awaiting acceptance.
2026-09-28 queue OPEN after the FS11 land, in order: (1) a served caller -- cgm_mod_queue is imported only by its gate, so the rung reads FINISH until FRONTDOOR-FINISH wires mod_report, mod_queue_mine and mod_act (VERB REQUEST on connect.plan row 1790621140, with the durable-row replay contract; reports are idempotent, so client retries can pass straight through); (2) LIB-UNCENSUSED clears on the next nx_eco_graph_build and nx_importcensus beat, not by hand; (3) the stated gap against the pinned rivals: a content-blind analogue of Admin Assist (join and post criteria on circle, vouch and account-age metadata, never content), post approval for a member, and a rule reference on each action (the metadata form of an admin note) -- content-reading keyword filters are refused by design and stay a stated gap; (4) a voluntary leave through the youth wall needs a grp_leave in nx_connect_group_lib, which has none, so this organ holds the wall on removal and on every join only; (5) the CSAE path proves fail-closed state against the estate's sink model (sink_fails), not delivery to any authority; the retry ledger inside nx_connect_csae_report main is still to be extracted as a callable (connect.plan row 1790360640 YS5 item 2 is half closed: the sink model is callable now); (6) there is still no faithsocial.gates map, by the BOARD seat's earlier choice; nx_connect_groupmod_gate runs GREEN through /api/gate_run, so the BOARD seat can write the map from that receipt; (7) cgm_mod_queue stays a faithsocial-owned contract until the BOARD or SYNC seat adopts it onto connect.plan and connect.matrix; (8) the four verifier programs whose symbols moved into libs this wave (nx_connect_lds_room, nx_connect_blind_abuse, nx_connect_csae_report, nx_connect_ads) were rebuilt behaviour-identical but not promoted, so their served binaries predate the move and promoting them is their owners' call; (9) the gate compiles the wave-16-owned franking, seal and chat-store sources through nx_connect_franking, so a wave-16 edit that breaks them turns this gate's next build RED while the served binary stays as shipped.
2026-09-28 measure Executed evidence for this board: knowledge/compare/faithsocial.gates (bare tree, the gates dir nx_swcompare_evidence reads) now carries two rows -- FS8's nx_connect_datesafety_gate, landed by the DATE-SAFETY seat, and FS11's nx_connect_groupmod_gate, appended by this seat (the row stands on its own line; the map ended in a newline). nx_swcompare_evidence faithsocial (job 1790622509) forked both live on the sealed images: GREEN 122 of 122 and GREEN 145 of 145, capture complete, and returned verdict=MEASURED-HONEST (present_axes 26 grounded 26 ungrounded 0, absent 3 all named, gates_green 2 of 2, the partitions reconcile, composition 15 claimed plus 3 declared gaps plus 11 landed watches equals 29 axes). This supersedes the BOARD row of 1790357776, which kept the board CLAIM-ONLY because no product gate could be forked then; the cgm_mod_queue row still reads LANDED-UNFLIPPED (a watch whose symbol is present), which the generator already measures as nishi 1, so the row text was not rewritten.

dossiers=2 cells_joined=2 no_matrix_row=0 (sum 2) gates_recorded=0 gates_unrecorded=1 no_gate_declared=1 (sum 2 of cells_joined) evgates=UNSTAMPED

Capability comparisons

Compare the field, search individual capabilities and open their source and adoption evidence. Documented presence does not establish comparative quality.

Position map — centrality and distinctiveness

The four-quadrant map the field uses for brand strategy (Dawar and Bagga, HBR June 2015), re-derived from this matrix on every publish. Centrality is the share of the category's feature mass a player covers, each feature weighted by how many hold it; distinctiveness is the average lead over each rival on the rows the player holds; breadth is the depth-weighted share of the whole matrix (the bubble); depth is how deeply the rows held are held; momentum is the day-over-day move off the spine (green rising, red falling, grey until day two); the dashed path runs first day → previous day → today. Dividers are the category means. Axes are fitted to the field of play, so read the tick numerals, not the frame. Rival marks are documented presence, so a rival's position reads the record, never its quality. The picture grades its own readability below; the table beside it is the same data for a screen reader or a second method.

Rows. 29 feature rows mapped of 29 matrix rows; 0 substrate rows (kernels, bounds and instruments the plan's rungrole marks substrate) are the estate's scaffolding, not category features, and stay off the map
Views. 2D cut: centrality, distinctiveness · 3D cube: centrality, distinctiveness, breadth · axes registered: centrality, distinctiveness, breadth, depth, momentum · a board picks its own in knowledge/compare/faithsocial.cdmap (cut|x|y, cube|x|y|z); absent = the HBR defaults
Position map, two-dimensional cutOne bubble per player. Bubble area is breadth, the ring colour is momentum, the dashed lines are the category means, and both axes are fitted to the field of play with their tick numerals shown. Every value is repeated in the table that follows. 300 400 500 600 700 800 900 1000 0 100 200 300 400 500 600 centrality (permil, fitted 300–1000) distinctiveness (permil, fitted 0–600) mean 569 mean 242 Unconventional Aspirational Peripheral Mainstream Nishi, centrality 824, distinctiveness 543, breadth 609, depth 679, momentum 36 Mutual, centrality 439, distinctiveness 150, breadth 126, depth 611, momentum -10 ChristianMingle, centrality 439, distinctiveness 95, breadth 114, depth 555, momentum -10 Hinge, centrality 472, distinctiveness 142, breadth 137, depth 571, momentum -11 Bumble, centrality 538, distinctiveness 269, breadth 195, depth 629, momentum -12 FacebookGroups, centrality 637, distinctiveness 329, breadth 275, depth 571, momentum -10 Discord, centrality 659, distinctiveness 255, breadth 241, depth 500, momentum -9 LDSSingles, centrality 549, distinctiveness 158, breadth 160, depth 518, momentum -12 Nishi Mutual ChristianMingle Hinge Bumble FacebookGroups Discord LDSSingles

bubble area = breadth · ring = momentum (green rising, red falling, grey until day two) · dashed = category means · axes fitted to the field of play: centrality 300–1000, distinctiveness 0–600 of 0–1000 permil (the full range put every player in one corner)
readability of the 2D cut, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 0 (a fact of the data: two players that close are that close) · data spread 648 permil of the plot · quadrant words unseated 0
text contrast, measured with wcag2-ratio (floors from contrast.conf), light theme: labels 16.24 (floor 4.50) · notes 16.24 (floor 4.50) · quadrant words 5.89 (floor 4.50) · tick numerals 5.89 (floor 4.50) · axis titles 5.59 (floor 4.50) · dark theme: labels 13.78 (floor 4.50) · quadrant words 5.55 (floor 4.50) · axis titles 5.97 (floor 4.50) · dark classes under their floor 0 (one figure serves both themes: a dark shortfall is a token to fix, never a class to hide) · classes refused under their floor 0 (a refused class is not drawn; the scale classes are measured, never hidden) · export: SVG PNG (receipt, rendered by the estate's own rasteriser from this page)
Position map, three-dimensional cubeThe same players in an isometric cube. Each axis is fitted to its own field of play and carries numerals on the floor grid and the vertical axis; each bubble drops a dotted line to its floor shadow so height reads as height. Values are in the table that follows. 300 400 500 600 700 800 900 1000 0 100 200 300 400 500 600 0 100 200 300 400 500 600 700 centrality distinctiveness breadth ChristianMingle: centrality 439, distinctiveness 95, breadth 114 Mutual: centrality 439, distinctiveness 150, breadth 126 Hinge: centrality 472, distinctiveness 142, breadth 137 LDSSingles: centrality 549, distinctiveness 158, breadth 160 Bumble: centrality 538, distinctiveness 269, breadth 195 Discord: centrality 659, distinctiveness 255, breadth 241 FacebookGroups: centrality 637, distinctiveness 329, breadth 275 Nishi: centrality 824, distinctiveness 543, breadth 609 Nishi Mutual ChristianMingle Hinge Bumble FacebookGroups Discord LDSSingles
axes fitted: centrality 300–1000 · distinctiveness 0–600 · breadth 0–700 permil · farther bubbles are painted first, nearer ones over them · the floor shadow is each bubble's (x, y) at height 0
readability of the 3D cube, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 4 (a fact of the data: two players that close are that close) · data spread 102 permil of the plot
Position map, small multiplesEvery pair of registered axes as one small cut. Each panel fits both axes to the field of play, the dashed lines are the category means, bubble area is breadth and the ring colour is momentum; the legend below names the colours. 300 900 0 600 distinctiveness vs centrality Nishi: centrality 824, distinctiveness 543 Mutual: centrality 439, distinctiveness 150 ChristianMingle: centrality 439, distinctiveness 95 Hinge: centrality 472, distinctiveness 142 Bumble: centrality 538, distinctiveness 269 FacebookGroups: centrality 637, distinctiveness 329 Discord: centrality 659, distinctiveness 255 LDSSingles: centrality 549, distinctiveness 158 300 900 0 700 breadth vs centrality Nishi: centrality 824, breadth 609 Mutual: centrality 439, breadth 126 ChristianMingle: centrality 439, breadth 114 Hinge: centrality 472, breadth 137 Bumble: centrality 538, breadth 195 FacebookGroups: centrality 637, breadth 275 Discord: centrality 659, breadth 241 LDSSingles: centrality 549, breadth 160 300 900 450 700 depth vs centrality Nishi: centrality 824, depth 679 Mutual: centrality 439, depth 611 ChristianMingle: centrality 439, depth 555 Hinge: centrality 472, depth 571 Bumble: centrality 538, depth 629 FacebookGroups: centrality 637, depth 571 Discord: centrality 659, depth 500 LDSSingles: centrality 549, depth 518 300 900 470 540 momentum vs centrality Nishi: centrality 824, momentum 518 Mutual: centrality 439, momentum 495 ChristianMingle: centrality 439, momentum 495 Hinge: centrality 472, momentum 494 Bumble: centrality 538, momentum 494 FacebookGroups: centrality 637, momentum 495 Discord: centrality 659, momentum 495 LDSSingles: centrality 549, momentum 494 0 600 0 700 breadth vs distinctiveness Nishi: distinctiveness 543, breadth 609 Mutual: distinctiveness 150, breadth 126 ChristianMingle: distinctiveness 95, breadth 114 Hinge: distinctiveness 142, breadth 137 Bumble: distinctiveness 269, breadth 195 FacebookGroups: distinctiveness 329, breadth 275 Discord: distinctiveness 255, breadth 241 LDSSingles: distinctiveness 158, breadth 160 0 600 450 700 depth vs distinctiveness Nishi: distinctiveness 543, depth 679 Mutual: distinctiveness 150, depth 611 ChristianMingle: distinctiveness 95, depth 555 Hinge: distinctiveness 142, depth 571 Bumble: distinctiveness 269, depth 629 FacebookGroups: distinctiveness 329, depth 571 Discord: distinctiveness 255, depth 500 LDSSingles: distinctiveness 158, depth 518 0 600 470 540 momentum vs distinctiveness Nishi: distinctiveness 543, momentum 518 Mutual: distinctiveness 150, momentum 495 ChristianMingle: distinctiveness 95, momentum 495 Hinge: distinctiveness 142, momentum 494 Bumble: distinctiveness 269, momentum 494 FacebookGroups: distinctiveness 329, momentum 495 Discord: distinctiveness 255, momentum 495 LDSSingles: distinctiveness 158, momentum 494 0 700 450 700 depth vs breadth Nishi: breadth 609, depth 679 Mutual: breadth 126, depth 611 ChristianMingle: breadth 114, depth 555 Hinge: breadth 137, depth 571 Bumble: breadth 195, depth 629 FacebookGroups: breadth 275, depth 571 Discord: breadth 241, depth 500 LDSSingles: breadth 160, depth 518 0 700 470 540 momentum vs breadth Nishi: breadth 609, momentum 518 Mutual: breadth 126, momentum 495 ChristianMingle: breadth 114, momentum 495 Hinge: breadth 137, momentum 494 Bumble: breadth 195, momentum 494 FacebookGroups: breadth 275, momentum 495 Discord: breadth 241, momentum 495 LDSSingles: breadth 160, momentum 494 450 700 470 540 momentum vs depth Nishi: depth 679, momentum 518 Mutual: depth 611, momentum 495 ChristianMingle: depth 555, momentum 495 Hinge: depth 571, momentum 494 Bumble: depth 629, momentum 494 FacebookGroups: depth 571, momentum 495 Discord: depth 500, momentum 495 LDSSingles: depth 518, momentum 494
Nishi Mutual ChristianMingle Hinge Bumble FacebookGroups Discord LDSSingles
10 panels over 5 registered axes, every pair once (the lower axis on x, the higher on y) · each panel fitted to its own field of play, first and last tick numerals shown · no labels in a small cut, the legend names the colours; the grade below reports the mark terms only (MM summed over the panels, spread averaged)
readability of the small multiples, self-graded by the layout ruler: label overlaps 0 · labels over marks 0 · off-canvas 0 · unresolved labels 0 · mark overlaps 19 (a fact of the data: two players that close are that close) · data spread 631 permil of the plot
PlayerQuadrantcentralitydistinctivenessbreadthdepthmomentumRows heldDays on spineFirst seen
NishiAspirational824543609679+36 since 2026-09-282642026-09-25
MutualPeripheral439150126611-10 since 2026-09-28642026-09-25
ChristianMinglePeripheral43995114555-10 since 2026-09-28642026-09-25
HingePeripheral472142137571-11 since 2026-09-28742026-09-25
BumbleUnconventional538269195629-12 since 2026-09-28942026-09-25
FacebookGroupsAspirational637329275571-10 since 2026-09-281442026-09-25
DiscordAspirational659255241500-9 since 2026-09-281442026-09-25
LDSSinglesPeripheral549158160518-12 since 2026-09-28932026-09-26
DayMatrix rows reviewedPlayers recorded
2026-09-25207
2026-09-26298
2026-09-28298
2026-10-08298

players 8|matrix rows 29|feature mass 91|centrality mean 569|distinctiveness mean 242|axes 5|spine days 4 (shown 4)|rows written today 0|readability defects 2D 0 cube 0|spine knowledge/status/cdmap/faithsocial.spine

How to read this evidence. A Nishi source mark records whether the named symbol is declared in the selected source file. It does not establish working behavior or accepted delivery. A watching tag names an expected source entry; discovering it updates source coverage only. A dark tag means the file exists but the named symbol was not found: inspect the source and contract before assuming the capability is missing or renaming code. Peer codes are authored assessments; unassessed means no comparison is established, not absence. Qualification, deployment identity, runtime observations and acceptance must carry their own evidence. Adoption records the catalog's observed path through source, build, promotion, registration and invocation; libraries use importer evidence and gates use declared execution surfaces. A full catalog path does not establish quality, freshness or a successful user outcome. Partial and unknown states retain their stated next action. Census stamps: importers asof 1790637268, gate census asof 1790104131 (unix seconds; -1 = census absent).

Capability matrix — measured against source

◉ authored stronger claim; source present● present◐ partial○ absent? unassessed; excluded from relative comparison · click any capability for its evidence

Peer cell coverage: authored assessed 203, unassessed 0. Authored assessments are not verified outcomes.

CapabilityNishiMutualChristianMingleHingeBumbleFacebookGroupsDiscordLDSSingles
Private sign-up without a stored identity documentMeasured: csu_signup_admit exists in runtime/_hdl_build/nx_connect_signup.nx, verified at emit. WATCH, rides connect CN13 (rung FS1): a handle and a passphrase through OPAQUE, consent per purpose OFF until the member turns it on, the key pair made on the device, no identity document or phone number stored; the bar ships the opposite design -- Hinge Selfie Verification with liveness checks and Bumble ID Verification collect identity evidence [hinge] [bumble]; rival cells code No because no page read documents a sign-up that keeps no identity evidence, uncertainty stated rather than guessed; LDS Singles codes No on direct evidence: its sign-in runs through a third-party identity service (clerk.ldssingles.com) [ldssingles] and its operator's privacy policy lists the identifiers it collects, name, address, telephone number, account name and password and government ID among them [ldssingles-privacy] Adoption: LIB-WIRED importers=8 nonval=2 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○○○
Passwordless-at-rest login (OPAQUE aPAKE, RFC 9807)Measured: cs_page_login exists in runtime/_hdl_build/nx_connect_serve.nx, verified at emit. Present and live at /connect/login: the server stores an envelope, never a password equivalent [rfc9807]; no rival page read documents a password-free-at-rest login, so rival cells code No with that uncertainty stated; LDS Singles codes No: its login runs through a third-party identity service [ldssingles] and its operator's privacy policy lists account name and password among the identifiers it collects [ldssingles-privacy] Adoption: LIB-WIRED importers=5 nonval=1 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○○○
Verified real person without storing identityMeasured: cvh_person_attest exists in runtime/_hdl_build/nx_connect_personhood.nx, verified at emit. WATCH, rides connect CN18 (rung FS5): a digital-credential presentation or an in-person vouch by two verified members reduced to a signed claim of personhood and age band, nothing else stored; Hinge ships Selfie Verification with liveness checks [hinge], Bumble ships Photo AND ID Verification (Best on depth) [bumble], Discord admits only age-assured adults to restricted spaces [discord-teen], and Christian Mingle states it runs no background checks [christianmingle]; every rival that verifies keeps the evidence, the gap this row closes; LDS Singles codes Yes: a third party (Persona) runs a selfie check that the member is a real person and not a picture or digital replica, government-ID verification is named only as an optional feature it may provide, and the facial template and reference selfie are kept by that provider [ldssingles-privacy], while its safety policy says the optional photo verification confirms a live photo matches the profile photos and verifies no identity, age or criminal history [ldssingles-safety]; that operator policy also covers Christian Mingle, whose cell is left for its own re-read Adoption: LIB-WIRED importers=2 nonval=1 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, FacebookGroups, Discord; fully adopted on the estate ladderCons behind Bumble (leads)
●○○●◉○◐●
Privacy-preserving age assurance (band only, no ID stored)Measured: hmix exists in runtime/_hdl_build/nx_connect_idage.nx, verified at emit. Present: an issuer attests an age BAND with unlinkable pseudonyms; September 2026 research reframes age assurance as a sociotechnical problem of evidence, evaluation, claims and decisions [arxiv-age]; Bumble ID Verification proves age by collecting an ID and Discord age-assures adults for restricted spaces (both Part); LDS Singles codes No: its terms admit only users 18 or older on their own representation [ldssingles-terms] and its safety policy states it does not verify a member's age [ldssingles-safety] Adoption: RUN-BY:roster — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○◐○◐○
Structural adult-minor wall (two-deep, SERVES youth)Source present; authored stronger claim: yw_may_channel in runtime/_hdl_build/nx_connect_youth_lib.nx, verified at emit. EXCEED KEPT from the connect board: peer to peer allowed, guardian to own youth allowed, any other adult to a minor only in a visible group with two or more adults, the published GH 20.7.1 norm [church-gh20]; Discord went teen-by-default and ships a Family Center for parents [discord-safety] (Part); the dating rivals do not serve youth at all and no page read documents a two-adult rule anywhere on the bar; LDS Singles codes No: its terms offer the platform only to users 18 or older [ldssingles-terms], so it serves no youth Adoption: LIB-WIRED importers=9 nonval=8 — fully adopted (top of its ladder).
Pros Source symbol found; stronger capability claim is authored; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
◉○○○○○◐○
Concentric circles: family, mission, ward, stake, worldwide, other ChristiansMeasured: ccl_circle_reach exists in runtime/_hdl_build/nx_connect_circles.nx, verified at emit. WATCH, rides connect CN14 (rung FS3): circles joined by consent and vouching, never by any official Church record; reach widens one circle at a time; two youth peers may become friends by mutual acceptance with their guardians able to see the friendship; the nearest rival shapes are flat groups with admins and moderators [fbgroups] and Discord servers, whose opt-in Family Center shows a connected guardian a teen's recently added friends, servers joined and who they messaged but never the messages [discord-family] (both Part); ours carries guardian visibility of a youth friendship inside the circle contract itself; LDS Singles codes No: its operator may show a member's profile to eligible members of its other dating services and theirs to the member to expand matches [ldssingles-privacy], reach widened by the company across brands rather than one circle at a time by the member's consent Adoption: LIB-WIRED importers=12 nonval=10 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○◐◐○
Groups and channels with roles (owner over admin over member)Measured: grp_can_post exists in runtime/_hdl_build/nx_connect_group_lib.nx, verified at emit. Present, live at /connect/community: no admin coup, a minor never admitted to a date-lane group; Facebook Groups is the category leader with admin and moderator roles (Best); Discord servers carry roles (Yes, read on the connect board, not re-read today); the dating rivals show no group surface on the pages read; LDS Singles codes No: its listing names profiles, curated matches, Smiles, messaging and profile views and no group surface [ldssingles-appstore] Adoption: LIB-WIRED importers=5 nonval=5 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, LDSSingles; fully adopted on the estate ladderCons behind FacebookGroups (leads)
●○○○○◉●○
Group moderation queue, content-blind (admins act, CSAE fail-closed, youth wall)Measured: cgm_mod_queue exists in runtime/_hdl_build/nx_connect_groupmod.nx, verified at emit. Present since 2026-09-28 (rung FS11; nx_connect_groupmod_gate 145 of 145 GREEN and bite-proven, awaiting acceptance): owners and admins work a queue of member reports, idempotent under a client retry and carried as metadata only -- reporter, reason code from the franking vocabulary, target, time, the franking message id and a content-blind abuse score, never a message byte -- and act on each (warn, mute until a time, remove as a ban until reversed, dismiss) in an additive log where a reversal is a new row and both rows stay; a report routed to CSAE refuses every action until its sink accepts it, a removal holds the two-deep youth wall on the group roster and on every youth event roster, a report naming an admin is withheld from that admin, and a group holding a minor serves no ad. Facebook Groups is Best: a Member-reported content queue where admins keep or remove the post, remove, ban or suspend the member or turn on post approval, a one-year activity log with undo and admin notes, and Admin Assist deciding on the content of the post, the author and past decisions [fbgroups-manage]; Discord is Yes: AutoMod keyword and spam filters that block a message, time a member out, or alert a moderation channel with a preview of the full message content [discord-automod]. Both moderate by reading content, the opposite of this design, and both automate more than this rung does (no keyword or criteria automation, no post approval, no action notes here): that is the gap; the dating rivals show no groups on the pages read; LDS Singles codes No: it has no groups, though its safety team reviews member reports and may warn, suspend, ban or remove content from profiles or messages [ldssingles-safety] Adoption: LIB-GATE-ONLY importers=2 — PARTIAL: imported only by validation organs (gates, tests, benches): wire it into a shipping program.
dossiernot adopted: imported only by validation organs (gates, tests, benches): wire it into a shipping program
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, LDSSinglesCons behind FacebookGroups (leads); not adopted yet: imported only by validation organs (gates, tests, benches): wire it into a shipping program
●○○○○◉●○
Member-missionary reconnection (mission x area x time)Measured: rc_inter_popc exists in runtime/_hdl_build/nx_connect_lds_reconnect_lib.nx, verified at emit. Present, live at /connect/reconnect: same mission AND shared area AND overlapping time, consent both ways; Mutual's own home page carries a testimonial from a couple who served their missions together and then matched [mutual] -- the demand is real and no rival models the bond; LDS Singles codes No: its profiles carry interests, photos and faith [ldssingles-appstore] but no page read documents a mission field or a reconnection lane Adoption: LIB-WIRED importers=6 nonval=6 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○○○
Ward and stake community boundary (community, never administration)Measured: wd_forbidden_count exists in runtime/_hdl_build/nx_connect_wards_lib.nx, verified at emit. Present: a field registry REFUSES every congregation-administration class (calling, record, attendance, ordinance, donation), the complement of the Church's own tools and never a substitute; no rival page read models a ward or stake boundary; LDS Singles codes No: it states it is not owned by or affiliated with the Church [ldssingles] and no page read models a ward or stake Adoption: LIB-WIRED importers=5 nonval=5 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○○○
Christian traditions at equal fidelity (self-declared, consent-gated)Measured: cfa_tradition_admit exists in runtime/_hdl_build/nx_connect_faith.nx, verified at emit. WATCH, rides connect CN15 (rung FS4): every Christian tradition self-identifies at the same depth under each church's preferred name, faith optional and consent-gated as a special category, a discovery signal and never an enforced filter; Mutual serves one tradition and Christian Mingle serves Christians as one audience [christianmingle] (both Part); mainstream apps may carry a religion profile field that no page read today documents, so they code No with that uncertainty stated; LDS Singles serves one tradition (Part): a member shows faith on the profile [ldssingles-appstore], its operator runs separate services by faith (Jdate, Christian Mingle, LDS Singles) [ldssingles-safety] and collects religious affiliation as sensitive data [ldssingles-privacy] Adoption: LIB-WIRED importers=4 nonval=3 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●◐◐○○○○◐
Consented intent lanes: friendship for all, dating between adults onlyMeasured: ln_min exists in runtime/_hdl_build/nx_connect_lanes_lib.nx, verified at emit. Present: escalation is the MIN of both opt-ins and a date lane never admits a minor; Bumble names a separate BFF friendship mode on its safety page (Part); Facebook Groups offers community without an intent model (Part); Mutual and Christian Mingle are dating-only; LDS Singles codes No: a dating app for adults whose listing names friendship only as an outcome (expand your social circle, lasting friendships) with no friendship mode or intent lane documented [ldssingles-appstore] Adoption: LIB-WIRED importers=6 nonval=6 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○◐◐○○
Reciprocal matching (both sides must want it)Measured: mx_inter_popc exists in runtime/_hdl_build/nx_connect_match_lib.nx, verified at emit. Present: harmonic-mean reciprocity, a one-sided pair scores 0; the August 2026 research bar is mutual optimality of direct effects in reciprocal recommendation (MODE) and fairness-aware two-sided matching [arxiv-dating]; the dating rivals match (Mutual documents matching as free); the community apps do not match people; LDS Singles codes Yes: curated match suggestions rooted in shared values and a Smile or wink to see if the feeling is mutual [ldssingles-appstore] Adoption: LIB-WIRED importers=5 nonval=5 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of FacebookGroups, Discord; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●●●●●○○●
Fair exposure (no pay-to-be-seen)Measured: gini_permil exists in runtime/_hdl_build/nx_connect_fair_rank.nx, verified at emit. Present: exposure-fair re-ranking audited by an integer Gini; Mutual Premium sells See Who Likes Me and unlimited likes, the pay-for-reach shape this row refuses; the other rivals' paid boosts are not documented on the pages read and code No with that uncertainty stated; LDS Singles codes No: Premium sells unlimited messaging, read receipts and a view of who looked at your profile [ldssingles-appstore]; no paid boost and no exposure audit is documented on the pages read Adoption: SOURCE-ONLY — PARTIAL: source exists, never compiled: /api/build it.
not adopted: source exists, never compiled: /api/build it
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSinglesCons not adopted yet: source exists, never compiled: /api/build it
●○○○○○○○
Date-safety check-in between adults (share a date, block and report in one place)Measured: cds_date_checkin exists in runtime/_hdl_build/nx_connect_datesafety.nx, verified at emit. WATCH, a NEW contract on this board (rung FS8, proposed for a connect rung): an adult shares a planned date with a trusted contact, checks in, and blocks or reports in one step, with nothing about the date readable by the server; Bumble ships Share Date (Best on the pages read); LDS Singles codes No: its safety policy advises telling a trusted friend or family member where you are going and meeting in public, advice and not an in-app share or check-in, while its report and block tools sit on every profile and message [ldssingles-safety] Adoption: LIB-WIRED importers=2 nonval=1 — fully adopted (top of its ladder).
dossier
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons behind Bumble (leads)
●○○○◉○○○
Content-blind abuse and scam detection (no plaintext to server)Measured: abuse_score exists in runtime/_hdl_build/nx_connect_blind_abuse_lib.nx, verified at emit. Present: behavioral and metadata signals only; Hinge's Comment Filter and nudges work on message content, the opposite design; romance-scam detection is live research (folk deception cues, June 2026); no rival page read documents content-blind detection; LDS Singles codes No: its operator combines automated systems with human review of profiles, uses AI and machine learning to detect abusive behavior and scam attempts, and may remove prohibited content from profiles or messages [ldssingles-safety] -- detection that reads content Adoption: LIB-WIRED importers=2 nonval=2 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○○○
End-to-end sealed messages in the browser (X25519)Measured: ce_emit_html exists in runtime/nx_connect_e2e_client.nx, verified at emit. Present, live at /connect/secure: sealed in the sender's browser, only ciphertext posted; no rival page read documents end-to-end encrypted chat (Discord text chat is not end-to-end encrypted, read on the connect board); LDS Singles codes No: its operator may remove prohibited content from messages [ldssingles-safety], so the service can read them, and its privacy policy never mentions encryption [ldssingles-privacy] Adoption: BUILT-UNPROMOTED — PARTIAL: compiled, never promoted to the serving root: /api/promote it.
not adopted: compiled, never promoted to the serving root: /api/promote it
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSinglesCons not adopted yet: compiled, never promoted to the serving root: /api/promote it
●○○○○○○○
Messaging that survives restart (send, receipts, edit, delete)Open — watching runtime/_hdl_build/nx_connect_msgstore.nx : msg_store_append, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. WATCH, rides connect CN6 (rung FS6): the in-memory thread becomes the per-account durable world; every rival ships durable messaging (Mutual documents messaging as free); LDS Singles codes Yes: messaging with read receipts, unlimited only on a paid subscription [ldssingles-appstore]
watching msg_store_append
Pros none measured yetCons behind Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; open contract; expected source declaration not established
○●●●●●●●
One family account across the Nishi platformsMeasured: acc_realm_unify exists in runtime/_hdl_build/nx_connect_realm.nx, verified at emit. WATCH, rides connect CN5 (rung FS2): the nishi_connect OPAQUE realm joins the family-wide Nishi login; a Facebook account spans Groups and Messenger (Yes, not re-read today); LDS Singles codes Part: its operator runs five dating services (Jdate, JSwipe, Christian Mingle, Zoosk and LDS Singles) under one safety policy [ldssingles-safety] and one privacy policy and may make a member's profile discoverable on the others [ldssingles-privacy] -- a profile pool the company controls, and no page read documents one login the member carries across them Adoption: LIB-GATE-ONLY importers=1 — PARTIAL: imported only by validation organs (gates, tests, benches): wire it into a shipping program.
not adopted: imported only by validation organs (gates, tests, benches): wire it into a shipping program
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, Discord, LDSSinglesCons not adopted yet: imported only by validation organs (gates, tests, benches): wire it into a shipping program
●○○○○●○◐
Zero paywalled connection featuresMeasured: hx_find exists in runtime/_hdl_build/nx_connect_h2h_exceed.nx, verified at emit. Present on the connect board, every connection feature free forever; Mutual's core is free and Premium adds See Who Likes Me, unlimited likes and more filters (Part); Christian Mingle distinguishes members from subscribers (Part); the Hinge and Bumble pages read today document no paid tier and their Part is UNVERIFIED pending a pinned pricing read; Discord Nitro is read on the connect board; Facebook Groups is free; LDS Singles is free to download and explore but unlimited messaging, read receipts and profile views need a paid subscription, sold in the App Store at USD 49.99 for one month, 104.99 for three and 149.99 for six [ldssingles-appstore] and billed as a recurring subscription under its operator's terms [ldssingles-terms] -- Part, with messaging itself behind the paywall and the free message allowance not documented Adoption: SOURCE-ONLY — PARTIAL: source exists, never compiled: /api/build it.
not adopted: source exists, never compiled: /api/build it
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, Discord, LDSSinglesCons not adopted yet: source exists, never compiled: /api/build it
●◐◐◐◐●◐◐
Real-world events with RSVP (capacity, youth wall)Measured: ev_rsvp exists in runtime/_hdl_build/nx_connect_events_lib.nx, verified at emit. Present: capacity and idempotent RSVP with the two-deep wall and zero fees; the dating field moved offline in 2026 -- Tinder launched in-app Events in March and had 26 markets live by September [tinder-press]; Facebook events and Discord server events are Yes (not re-read today); LDS Singles codes No: no events on the pages read [ldssingles-appstore] Adoption: LIB-WIRED importers=7 nonval=7 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○●●○
Installed user base (liquidity)Measured: lq_cohort_seed exists in runtime/nx_connect_liquidity.nx, verified at emit. WATCH, rides connect CN3 (rung FS7): 0 real users today; Mutual reports millions of Latter-day Saints and tens of thousands of couples (Best inside the wedge); every other rival has an installed base whose count was not read today; LDS Singles claims thousands of Latter-day Saints who found love and friendships through it, and its current iOS app shows 19 ratings averaging 2.6 [ldssingles-appstore] (Yes, a base whose size was not read) Adoption: LIB-WIRED importers=3 nonval=1 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; fully adopted on the estate ladderCons behind Mutual (leads)
●◉●●●●●●
Native mobile appsOpen — watching runtime/nx_connect_client.nx : cl_mobile_shell, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. WATCH, rides connect CN2 (rung FS10): ours is the zero-JS web app at /connect; Mutual ships on iOS and Android and Christian Mingle ships an app; every rival ships native apps; LDS Singles ships an iOS app (iOS 16.4 or later) [ldssingles-appstore] and links an Android app from its home page [ldssingles]
watching cl_mobile_shell
Pros none measured yetCons behind Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; open contract; expected source declaration not established
○●●●●●●●
Trained matching and moderation on content-blind signalsOpen — watching runtime/nx_connect_neural.nx : nn_match_train, re-measured on every compare beat. Ship that symbol and this mark flips itself; the comparewatch- plane row flips with it. WATCH, rides connect CN4 (rung FS9): no-float models on consented behavioral signals only, with a pre-declared accept rule against the hand-weighted baseline; Hinge's Comment Filter and nudges are moderation on content (Part); the August 2026 frontier is agentic delegation in two-sided recommendation; LDS Singles codes Part: AI and machine learning detect abusive behavior and scam attempts [ldssingles-safety] and its matches are personalized suggestions [ldssingles-appstore], with no statement that either stays off message content
watching nn_match_train
Pros none measured yetCons behind Hinge, LDSSingles; open contract; expected source declaration not established
○○○◐○○○◐
Games together inside circles (youth only in visible group rooms)Measured: room_admit exists in runtime/_hdl_build/nx_connect_lds_room_lib.nx, verified at emit. Present, composed from what exists (operator ask REQ 1790361302): room_admit holds the two-deep wall on join and on leave and drives the nx_room_relay game and chat channels, so members play one to one or in groups inside their circles and a youth plays only with accepted peers or in a visible room with two or more adults; LDS Singles, read and pinned 2026-09-25, offers profiles, matching and a premium upgrade for singles and names friendships only in passing [ldssingles]; Discord codes Yes on its Activities (games inside voice channels) from general knowledge, NOT read on a pinned page today (UNVERIFIED); no page read documents games together on the other rivals, so they code No with that uncertainty stated; LDS Singles codes No, its app store listing naming no games either [ldssingles-appstore] Adoption: LIB-WIRED importers=4 nonval=4 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○○●○
Activities planned together across continents (a youth Iron Chef, teams, each member's own time zone)Measured: cav_plan_event exists in runtime/_hdl_build/nx_connect_activity.nx, verified at emit. WATCH, a NEW contract on this board (operator ask REQ 1790361303, plan rung owed): a circle plans an activity with teams, a date and a time shown in each member's own zone, capacity through ev_rsvp and shared materials, youth only in visible groups with two or more adults, no location beyond a coarse band; Facebook events and Discord scheduled events code Part (events without teams or a youth wall, not re-read today); the dating rivals show no activity planning on the pages read; LDS Singles codes No: no activity planning on the pages read [ldssingles-appstore] Adoption: LIB-WIRED importers=4 nonval=2 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○◐◐○
Language circles and reciprocal language partnersMeasured: clc_circle_match exists in runtime/_hdl_build/nx_connect_langcircle.nx, verified at emit. WATCH, a NEW contract on this board (operator ask REQ 1790361304, plan rung owed): a speaker of one language is paired with a learner of it and the reverse through the mx_inter_popc reciprocity and practises in a language circle with inline translation and a correction loop (ct_render_inline, ct_rationed_translate); a Facebook Group or a Discord server can host a language exchange but matches no partners (Part, not re-read today); no dating rival page read documents language learning; LDS Singles codes No: no language learning on the pages read rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: LIB-WIRED importers=3 nonval=2 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○◐◐○
Service needs and projects inside circles (exact place released only after both confirm)Measured: csh_need_match exists in runtime/_hdl_build/nx_connect_service.nx, verified at emit. Present, rides connect CN17 (operator ask REQ 1790361305): a need or project is posted inside a circle, offers are matched by circle and a coarse locality band with capacity through ev_rsvp, and the exact place is released only after mutual confirmation; a Facebook Group can host community help without need matching (Part, not re-read today); no other rival page read documents a service board; LDS Singles codes No: no service board on the pages read rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: LIB-WIRED importers=4 nonval=3 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○◐○○
Seed sharing and produce help member to memberMeasured: csh_share_match exists in runtime/_hdl_build/nx_connect_service.nx, verified at emit. WATCH, a NEW contract on this board and an extension of the service board (operator ask REQ 1790361306, plan rung owed): a member lists seeds, cuttings or surplus produce and a neighbour in a shared circle asks for them, matched by circle and a coarse locality band, the handoff place released only after both confirm; a Facebook Group can host a local swap without matching or a place release (Part, not re-read today); no other rival page read documents sharing between members; LDS Singles codes No: no sharing between members on the pages read rival marks uncited — the Yes, Best or Part codes on this row are an observation read with no reference mark behind them Adoption: LIB-WIRED importers=4 nonval=3 — fully adopted (top of its ladder).
Pros Implementing source symbol found; runtime acceptance separate; ahead of Mutual, ChristianMingle, Hinge, Bumble, FacebookGroups, Discord, LDSSingles; fully adopted on the estate ladderCons none on the measured axes (rival marks are documented presence, not depth)
●○○○○◐○○
Rival-claim provenance. Every Yes, Best or Part mark in a rival column is a claim about someone else's product. A cited row carries a reference mark that resolves to a pinned mirror (the refs gate measures that); an uncited row is an observation read and is badged in its evidence until a reference lands. The badge is the receipt, never the proof: a mark proves a mirror exists, not that the mirror supports the code. The rows are counted below.
Rival claims, counted
ClassCountNote
rows with rival marks22rows carrying a Yes, Best or Part in a rival column
cited19a reference mark resolves to a pinned mirror
uncited3an observation read, badged until a reference lands
rows, summed22RECONCILED: the parts sum to the total 22

Delivery and evidence

Inspect risks, technical debt, rendered observations, experiments and references. Read scope and limitations alongside every result.

Risk register

RiskLikelihood x impactMitigation
A dating lane that ever admits a minor breaks the wallpossible x highlanes are adult-only by construction and FS8's gate carries a minor-refusal tooth; the youth verdict is identical with and without faith (connect CN15)
Copying a dating app's engagement economy into a faith communitylikely x highthe zero-paywall and fair-exposure rows are the rulers; connect CN3 measures replies and meetings, never time-on-app
Circles built from official Church records would become congregation administrationpossible x highconnect CN14 admits by consent and vouching only; the ward boundary registry refuses every congregation-administration class

Release history and work log

The worked plan, on the board. Every leg appends what it measured, landed, retracted, learned and left queued, per rung, so a crash leaves the next seat a ledger here rather than a transcript to mine. Kinds: measure, land, retract, lesson, queue. Newest last.
WhenRungKindEntry
2026-09-25BOARDlandfaithsocial admitted as DATA 2026-09-25 by the XLADDER seat: faithsocial.matrix 12021 B (23 rows, cols Mutual ChristianMingle Hinge Bumble FacebookGroups Discord), faithsocial.plan 13585 B (3 sotabar, 3 barscan, 3 sotatarget, 10 rungs FS1-FS10 each riding a connect rung with its contract symbol, 10 rungrole, ms M1-M3, ver 0.1 1.0 2.0), faithsocial.refs 6876 B (12 refs: 10 mirrors fetched and pinned today by nx_research_fetch plus nx_filehash, 2 reused from connect); regen.list row 119 appended (1124 B). Hinge safety URL answered 404 and was replaced by its newsroom; Tinder's safety page carried none of its feature names and is not cited
2026-09-25FS5queueINTAKE 1790355006 routed by nx_intake_route (operator-seat, epoch 1790356663) from pm-seat: R6 of parent REQ 1790355000: beat the dating sites (Mutual, Hinge, Bumble, Tinder, Match) on privacy, safety, verification and connection quality -- consented intent lanes between adults only with a m -- sponsor intake-1790355006 plus2
2026-09-25FS8queueINTAKE 1790355006 routed by nx_intake_route (operator-seat, epoch 1790356663) from pm-seat: R6 of parent REQ 1790355000: beat the dating sites (Mutual, Hinge, Bumble, Tinder, Match) on privacy, safety, verification and connection quality -- consented intent lanes between adults only with a m -- sponsor intake-1790355006 plus2
2026-09-25FS9queueINTAKE 1790355006 routed by nx_intake_route (operator-seat, epoch 1790356663) from pm-seat: R6 of parent REQ 1790355000: beat the dating sites (Mutual, Hinge, Bumble, Tinder, Match) on privacy, safety, verification and connection quality -- consented intent lanes between adults only with a m -- sponsor intake-1790355006 plus2
2026-09-25FS3queueINTAKE 1790355007 routed by nx_intake_route (operator-seat, epoch 1790356667) from pm-seat: R7 of parent REQ 1790355000: beat the social sites (Facebook Groups, Instagram, Discord) on groups, privacy and safety -- groups with roles and events, content-blind serving, end-to-end encrypted conv -- sponsor intake-1790355007 plus2
2026-09-25FS6queueINTAKE 1790355007 routed by nx_intake_route (operator-seat, epoch 1790356667) from pm-seat: R7 of parent REQ 1790355000: beat the social sites (Facebook Groups, Instagram, Discord) on groups, privacy and safety -- groups with roles and events, content-blind serving, end-to-end encrypted conv -- sponsor intake-1790355007 plus2
2026-09-25BOARDmeasurenx_ladder faithsocial verdict=LADDERED targets=3 (best-in-class 1, frontier 2, undated 0) rungs=10 placed=10 unplaced=0; nx_barfresh verdict=FRESH bars=3 fresh=2 attested=1 (SB-FS-MATCH is August 2026, attested by the arxiv-dating barscan newest=2026-08); nx_compare_rank job 1790356523 rungs=10 done=4 open=6 unmapped=0, TARGET 0.1 M1, critical path FS6 then FS4, both read DARK-CONTRACT because sibling seats were mid-write (nx_connect_msgstore.nx at 9625 B without msg_store_append yet; nx_connect_faith.nx declared cfa_tradition_admit minutes after the rank ran), TREATMENT NO-TREATMENT labeled not refused; rank artefact faithsocial.rank sha256 755aa9c8; the ranker filed 2 of its top 3 rungs into pm_intake.jrnl
2026-09-25BOARDmeasurenx_compare_regen_scoped job 1790356544 verdict=GREEN published faithsocial/index.html 190458 B and api.json 35208 B (generated 1790356550) with the generator fork FRESH; api.json measures 17 of 23 rows present (16 at nishi=1 plus the youth-wall exceed at 2) and 6 open watches (cvh_person_attest, cfa_tradition_admit, cds_date_checkin, msg_store_append, cl_mobile_shell, nn_match_train); four watches had already flipped from sibling seats' landings this hour (csu_signup_admit, ccl_circle_reach, acc_realm_unify, lq_cohort_seed); nx_page_verify https://nishifamily.com/compare/faithsocial VERDICT=GREEN status 200 190458 B a11y-issues=0 (static checks; browser rendering unverified)
2026-09-25FS3queuePM seat, for the XLADDER seat: operator-goal children R6 1790355006 (beat Mutual, Hinge, Bumble, Tinder, Match) FILED plus2 to FS5 FS8 FS9 and R7 1790355007 (beat Facebook Groups, Instagram, Discord on groups, privacy and safety) FILED plus2 to FS3 FS6; the router agreed on R6 (second pass top1 FS5 40266 milli, gap 101 permil) but NOT on R7 -- no faithsocial rung speaks groups with roles and events, moderation, no ads to minors or fail-closed CSAE reporting, so FS3 and FS6 carry it by this seat judgement while the router top1 was a familyatlas watch note naming FamilySearch Family Groups and faithsocial first appears at rank 15 (FS9); OPEN: declare a groups rung graded against FacebookGroups and Discord (roles, events, moderation queue, youth wall on join and leave, composing the landed connect group, events, CSAE and ads organs) so R7 can be re-routed to it
2026-09-25BOARDmeasurenx_domain_admit faithsocial through /api/organ_run: the first run (1790356763) was VERDICT=REFUSE on rule C2, no knowledge/barcheck.conf row and no UNPINNED declaration, so the comparison was silently unfalsifiable; fixed in the DATA and not the gate -- the matrix header now declares all six column rivals UNPINNED with the reason (closed consumer apps ship app-store builds and dated prose, no registry nx_barcheck can read; each code grounded by a pinned mirror instead), the observability precedent; the second and third runs read VERDICT=ADMIT (CLAIM-ONLY, no .gates map), latest rows=24 grounded=19 absent=0 ungrounded=0 watch-new-organ=5 C2 unpinned-declared=1
2026-09-25BOARDlessonThe fleet citation referee (nx_compare_refs_gate job 1790356709, 37 of 44, RED mostly on other domains' rows) named four faithsocial ratchet rises: hinge.co/press and bumble.com/en/safety each followed one redirect (canonicals hinge.co/newsroom and bumble.com/the-buzz/safety), and three refs reused connect mirrors that carry no provenance-journal row (discord-teen, church-gh20, rfc9807). Repaired in the data: all five re-fetched today at the canonical URL with zero hops into faithsocial mirrors -- Bumble 79317 B sha 8e591d0a, the Discord teen release 117445 B sha 8940bf82 (its text moved since the August mirror), GH 20.7.1 957880 B sha bf02b62a still reading at least two adults must be present at all Church activities attended by children and youth, RFC 9807 and the Hinge newsroom byte-identical to the earlier mirrors -- and the refs file rewritten under CAS (7097 B). A reused mirror with the right bytes is still UNPROVEN to the referee when no fetch journal row stands behind it; fetch into the board's own name.
2026-09-25FS11landFS11 declared on the PM seat's request for operator child R7 (beat Facebook Groups, Instagram and Discord on groups, privacy and safety; its router could not place R7 because no faithsocial rung spoke groups, moderation, CSAE or ads to minors): contract cgm_mod_queue on runtime/_hdl_build/nx_connect_groupmod.nx, a content-blind moderation queue composing the landed connect group, events, youth-room, abuse, CSAE and ads organs, graded against Facebook Groups admins and moderators and Discord server moderation; matrix row added (FacebookGroups Best from the pinned help page, Discord Yes not re-read today), rungrole contender for T-BIC-FAITHSOCIAL, M1 now FS1 FS2 FS3 FS4 FS6 FS7 FS11 at 12 u (M2 19.5, M3 23.5); nx_ladder re-run LADDERED 11 of 11 placed; nx_compare_rank job 1790357546 open=5 and the TARGET 0.1 critical path is FS11 alone (FS4 and FS6 flipped done as sibling seats declared cfa_tradition_admit and msg_store_append). OPEN: cgm_mod_queue and FS8 cds_date_checkin are new contracts owned on this board until the BOARD or SYNC seat adopts them onto connect.plan and connect.matrix; the PM seat can now re-route R7 to FS11
2026-09-25BOARDmeasureSecond publish after FS11 and the refs repair: nx_compare_regen_scoped job 1790357599 verdict=GREEN (fork FRESH), api.json 37583 B measures 24 rows, 19 present (18 at nishi=1 plus the youth-wall exceed at 2) and 5 open watches (cvh_person_attest, cgm_mod_queue, cds_date_checkin, cl_mobile_shell, nn_match_train); nx_page_verify job 1790357668 VERDICT=GREEN a11y-issues=0; the fleet citation referee job 1790357600 reads 38 of 44 (was 37 of 44) and names ZERO faithsocial rows in any failing list (was 7: two redirects, two moved, three unproven) -- the remaining six failing teeth belong to other domains' refs (pmdash, datavis, automation, search, cms, loadgov)
2026-09-25BOARDlessonNo faithsocial.gates map was written, on purpose, and nx_domain_admit reads the board CLAIM-ONLY and says so. The one gate connect.gates cites, nx_connect_gate.elf, ran GREEN 5 of 5 through /api/gate_run (job 1790357776) and its teeth prove the bounded socket connect() wrapper -- fcntl reaches the kernel, a black-hole dial returns after 2001 ms, refusal is told from timeout, fd flags are restored -- not the Nishi CONNECT product: a homonym, so it is not evidence for any row here. The real product gates for this board's rows, nx_connect_lds_youth.elf (44460 B, the youth wall) and nx_connect_lds_reconnect.elf (22263 B, mission reconnection), are PROMOTED-UNREGISTERED and /api/gate_run refuses them by name (verifiers only: a name must end in gate, test or kat), so this seat could not run them and will not cite a gate it could not run. OPEN for the BOARD or SYNC seat: declare those two as gates (organ_gate.conf or a _gate twin), run them, then write faithsocial.gates and correct connect.gates from their receipts
2026-09-25BOARDmeasureFinal publish this leg: nx_compare_regen_scoped job 1790358032 verdict=GREEN (fork FRESH), index.html 210025 B sha256 0cfbf85f, api.json 38452 B, 24 rows with 5 open watches; nx_page_verify job 1790358082 VERDICT=GREEN status 200 a11y-issues=0 (static checks, browser rendering unverified); nx_compare_rank job 1790358008 rungs=11 done=6 open=5 finish=6 (the six landed libraries read LIB-UNCENSUSED until nx_eco_graph_build and nx_importcensus re-run), TARGET 0.1 M1 critical path FS11; citation referee job 1790358013 reads 38 of 44 fleet RED with zero faithsocial rows after the discord-family ref was added (13 refs, 13 mirrors, all fetched today at the cited URL with zero redirect hops and pinned by nx_filehash)
2026-09-25BOARDqueueOPEN after this leg, in order: (1) FS11 cgm_mod_queue and FS8 cds_date_checkin need connect rungs and organs (the BOARD seat adopts them, then a builder ships them with gates); (2) FS5 cvh_person_attest, FS9 nn_match_train and FS10 cl_mobile_shell ride connect CN18, CN4 and CN2; (3) a faithsocial.gates map once nx_connect_lds_youth and nx_connect_lds_reconnect are declared gates and run GREEN (connect.gates cites a socket-connect homonym); (4) the Hinge and Bumble Part codes on the zero-paywall row are UNVERIFIED -- neither mirror read today names a paid tier, so a pinned pricing read decides them -- and the Discord roles and events, Facebook events and Facebook account-span cells were read on other boards and not re-read today; (5) Tinder, Instagram and Match are not columns (Tinder is grounded in the bar and the events note only); a seventh column waits on reading the matrix generator's column bound; (6) presence is not product: 0 real users, and FS7 is the rung whose done-rule measures people
2026-09-25FS11queueINTAKE 1790358601 routed by nx_intake_route (operator-seat, epoch 1790360391) from ys-pm-seat: Y1 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): youth connect around the world and have fun, one to one a -- sponsor intake-1790358601 plus2
2026-09-25FS11queueINTAKE 1790358603 routed by nx_intake_route (operator-seat, epoch 1790360420) from ys-pm-seat: Y3 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): minors never harm minors -- no bullying and no inappropri -- sponsor intake-1790358603 plus2
2026-09-25FS11queueINTAKE 1790358606 routed by nx_intake_route (operator-seat, epoch 1790360466) from ys-pm-seat: Y6 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): the platform is not a babysitter -- no monitoring. No hum -- sponsor intake-1790358606 plus2
2026-09-25FS11queueINTAKE 1790358610 routed by nx_intake_route (operator-seat, epoch 1790360523) from ys-pm-seat: Y10 of parent REQ 1790358600 (operator youth-safety directive 2026-09-25 12:50 CDT, filed under leg REQ 1790355000; derived by the YS-PM seat): report abuse without surveillance. A recipient can repor -- sponsor intake-1790358610 plus1
2026-09-25FS1queueINTAKE 1790361301 routed by nx_intake_route (pmboard-seat, epoch 1790361359) from pmboard-seat: B1 of parent REQ 1790361300 (operator ask 2026-09-25 13:20 CDT, filed under leg REQ 1790355000; derived by the PM-BOARD seat): exceed ldssingles.com -- the Latter-day Saint dating site fetched, pinned -- sponsor intake-1790361301 plus2
2026-09-25FS5queueINTAKE 1790361301 routed by nx_intake_route (pmboard-seat, epoch 1790361359) from pmboard-seat: B1 of parent REQ 1790361300 (operator ask 2026-09-25 13:20 CDT, filed under leg REQ 1790355000; derived by the PM-BOARD seat): exceed ldssingles.com -- the Latter-day Saint dating site fetched, pinned -- sponsor intake-1790361301 plus2
2026-09-25FS3queueINTAKE 1790361303 routed by nx_intake_route (pmboard-seat, epoch 1790361365) from pmboard-seat: B3 of parent REQ 1790361300 (operator ask 2026-09-25 13:20 CDT, filed under leg REQ 1790355000; derived by the PM-BOARD seat): plan activities together across continents -- operator example: a youth I -- sponsor intake-1790361303 plus2
2026-09-25FS1queueLDS Singles (ldssingles.com, Black Cap Holdings LLC) read, mirrored and pinned 2026-09-25 [ldssingles] and landed as a research bar, NOT yet a column: the home page read documents Join Free sign-up through a third-party sign-in service, profile browsing, a premium upgrade, iOS and Android apps, Google Tag Manager in the head and no background checks, but documents nothing on messaging, verification, matching, events, groups or youth, so most matrix rows cannot be coded honestly from it; the next seat fetches and pins its features or pricing page and help centre, codes every row, and adds LDSSingles to @cols in one whole-file CAS write
2026-09-25FS3queueOperator ask REQ 1790361300 (children 1790361301 to 1790361307) put five rows on this board: games together on room_admit (present), activities across continents cav_plan_event, language circles clc_circle_match, service csh_need_match (present) and seed and produce sharing csh_share_match; the three watches carry no plan rung yet, so a rung and a rungrole row are owed for each before the ranker can price them, landed together so the board stays LADDERED
2026-09-25FS3measureAfter the five community rows and the LDS Singles bar landed: nx_ladder faithsocial LADDERED (targets 3, rungs 11 placed 11), nx_barfresh FRESH (bars 3, fresh 2, attested 1), scoped regen GREEN, nx_page_verify GREEN on /compare/faithsocial; nx_compare_refs_gate fleet RED 38 of 44 on mirrors-exist, pins-match, cited-inline and three provenance ratchets, with no offender line naming faithsocial or the ldssingles mirror (pin e40455e6 matches nx_filehash); attribution of the fleet RED to other domains is UNVERIFIED
2026-09-25BOARDqueueREVIEW wave-6 R5 (SPRAWL, debt 1790372858): FS1 FS2 FS3 FS4 FS5 FS6 FS7 FS9 FS10 re-declare connect CN13 CN5 CN14 CN15 CN18 CN6 CN3 CN4 CN2 with the same symbols, so nx_compare_rank ranks cl_mobile_shell on two critical paths (connect #1 priority 6300, here #2 priority 800), counts the same 7 libs done on both boards and splits sponsors (intakes 1790355006 and 1790355007 landed only here). Owed to this board's seat: keep only rungs owned nowhere else (FS8, FS11), move the 9 riding rows SUPERSEDED then ARCHIVED with successor connect CNn, and carry cross-board references the ranker resolves from connect instead; the board was not edited by the reviewer
2026-09-25BOARDlandLDSSingles column coded by the wave-7 W5 seat (queued at 1790361400): four pages fetched, read and pinned today beside the wave-5 home mirror -- the App Store listing (690875 B sha 05ded8b9, re-fetched at its canonical after the id-only URL redirected once), Black Cap Holdings Online Dating Safety Policy (24984 B sha 4482c414, last modified 21 July 2026, covering Jdate JSwipe Christian Mingle Zoosk and LDS Singles), Privacy Policy (73291 B sha 4e1e8d61) and Terms of Use (64812 B sha 2addc3c4); support.ldssingles.com answered 403 twice and is UNREAD. Matrix rewritten in ONE CAS write (expect h7570cb6b, 16769 to 23286 B, pipes 300 to 330 = 29 rows of 11 fields plus 6 plus 5), @cols gains LDSSingles; LDS Singles codes Yes 5 (verified person by a Persona selfie, matching, messaging, installed base, iOS app), Part 4 (one tradition, cross-brand profile pool, unlimited messaging behind Premium at USD 49.99 a month, AI scam detection), No 20, sum 29; refs 8420 to 12197 B with 4 rows, each cited inline, pins equal nx_filehash. nx_ladder LADDERED 11 of 11, nx_barfresh FRESH (2 fresh 1 attested), scoped regen job 1790372987 GREEN (api.json 52996 B with 7 cells on all 29 axes, index 243230 B, fork FRESH), nx_page_verify job 1790373099 GREEN a11y-issues=0 (static checks, browser rendering unverified), nx_compare_refs_gate job 1790372993 fleet RED 38 of 44 with one advisory faithsocial line (PROV-REDIRECTED ldssingles-appstore hops=1 read from the first fetch's journal row, canonical BENIGN-HOP equal to the cited URL). OPEN: the same operator safety policy covers Christian Mingle, whose verified-person cell still codes No; the FS rung rows were classified SPRAWL by REVIEW R5a (debt 1790372858) and this seat touched no rung
2026-09-25BOARDlandCONSOLIDATED by the wave-9 S3 seat under debt 1790372858 (REVIEW R5a SPRAWL): one piece of work has ONE owner rung. Retired from this board nine rungs whose contract symbol connect owns, each successor read on connect.plan this hour with the same symbol and the same est u: FS1 to CN13 csu_signup_admit, FS2 to CN5 acc_realm_unify, FS3 to CN14 ccl_circle_reach, FS4 to CN15 cfa_tradition_admit, FS5 to CN18 cvh_person_attest, FS6 to CN6 msg_store_append, FS7 to CN3 lq_cohort_seed, FS9 to CN4 nn_match_train, FS10 to CN2 cl_mobile_shell; with them went their nine rungrole rows, milestone M3 and version 2.0 (its one rung was FS10). MINED before archiving: two clauses were stricter here than on the owner -- FS3 made the gate prove guardians can SEE a youth friendship, FS9 made the held-out set INCLUDE romance-scam patterns (arXiv 2606.23241) -- queued to the CN14 and CN4 owners on connect.plan. Kept FS8 cds_date_checkin and FS11 cgm_mod_queue: no rung row on any of the 1142 compare plans declares either symbol and no plan names a faithsocial rung as a dependency (nx_shelltool, corpus_complete=1). The matrix is untouched (every Nishi cell keeps its organ and symbol), as are the research bars, the three dated targets and every earlier log row. FS8 now depends on connect:CN18; M1 is FS11 at 2 u and M2 is FS8 at 3.5 u; answers, bar texts, target notes and risks name the connect owners. The pre-change board is banked byte-exact at knowledge/retired/buildroot_knowledge_compare_faithsocial.plan-precons-1790373638 (sha256 10ae43bc, 33686 B, nx_filecopy verified=1), so every retired row is restorable. THE GRAMMAR, read from source first: a rung names another board's rung only as a DEPENDENCY token domain:rung (nx_swcompare_lib sg_parse records and counts it as external_deps, never an edge and never a refusal, the owner board never loaded; ecosystem EC77 depends on pmdash:PR15). There is no reference RUNG: nx_ladder counts a rungrole row naming no rung here as an ORPHAN (PARTIAL), nx_compare_rank rk_list_one reads a milestone token naming no rung here as NOT OPEN so a milestone of owner rungs would read MET, and nx_board_idref_gate counts it DANGMS; hence retirement with successors named rather than reference rows
2026-09-25BOARDqueueOWED after the consolidation. To the ranker owner (nx_compare_rank, nx_ladder_lib, nx_board_idref_gate: the grammar extension REVIEW R5a asked for, which does not exist today): (1) resolve a domain:rung reference from the owner board -- measured state, sponsor set, STATUS text -- so FS8's dependency on connect:CN18 counts toward momentum again (FS8 read m=2 at priority 666 while it depended on the local FS5; an unresolved external counts nothing); (2) a cross-board rungrole form, so T-FRONT-AGEBAND and T-FRONT-CIRCLES name their connect climbers instead of reading unclimbed here; (3) a milestone token resolved from the owner, and until then a milestone token naming no rung refused by name, never read as met; (4) a retired-id declaration the referential gate resolves, so the eleven history rows naming FS1 FS3 FS5 FS6 FS9 stop counting DANGLOG. To the PM seat: the router's sponsor rows for intakes 1790355006 (FS5 FS9), 1790355007 (FS3 FS6), 1790361301 (FS1 FS5) and 1790361303 (FS3) were filed against rungs now retired and reach no connect owner; re-route them to CN18 CN4 CN14 CN6 CN13 (this seat did not read the rows' scope field). To the board seat: nine matrix notes still say (rung FSn) beside their connect owner, prose only; the three community watches (cav_plan_event, clc_circle_match, csh_share_match) still carry no rung here or on connect
2026-09-25BOARDmeasureAfter the consolidation (one whole-file CAS write, expect hab89e288095b375e, 33686 to 35037 B, sha256 e01a3c14): nx_ladder LADDERED targets 3 rungs 2 placed 2 with targets_unclimbed 2 (both frontier targets; their climbers are connect CN18, CN14, CN15 and CN4 under T-FRONT-CONNECT); nx_barfresh FRESH (2 fresh 1 attested); nx_compare_rank job 1790375207 rungs=2 done=0 open=2, TARGET 0.1 M1 critical path FS11 priority 600 (unchanged), FS8 priority 333 (was 666 with momentum 2 on the local FS5; the connect:CN18 reference prints as GRAPH EXTERNAL and counts nothing), and the sponsor rows for intakes 1790355006, 1790355007 and 1790361301 now apply to both rungs domain-wide while 1790361303 reaches neither; scoped regen job 1790375268 GREEN (index.html 238762 B, api.json 45408 B with 29 axes, 24 at nishi=1, and 2 rung objects, fork FRESH); nx_page_verify job 1790375309 GREEN status 200 a11y-issues=0 (static checks, browser rendering unverified); nx_board_idref_gate scoped on this board danglog 11 to 24 before this row (the 11 history rows naming retired rungs plus 2 new BOARD rows), dangms 0, dupid 0
2026-09-26cav_plan_eventmeasureW11 SEAT GATES-COMPLETION: the watch Activities planned together now reads its symbol PRESENT on the published page (scoped regen job 1790440146: Measured, cav_plan_event exists in runtime/_hdl_build/nx_connect_activity.nx, verified at emit). The flip is the receipt, not the proof: the proof is nx_connect_activity_gate, now bite-proven (job 1790437447 killed a compiling mutant), sharpened from 59 to 67 teeth after the whole youth-safety invariant was mutated (an adults-only activity admitting a minor and a minor founding, leading or judging a team all went unnoticed by the old teeth; RED 61 of 67 on that mutant now), promoted 9d33e418, registered, admitted to knowledge/gateroster.conf and cited in knowledge/compare/connect.gates (forks GREEN 67 of 67 live). The row still renders lib-uncensused until nx_importcensus next runs, and no rung on this board or on connect carries the contract yet (owed to the board seat; journal on connect.plan row 1790439620).
2026-09-28RANKmeasureW16 BOARD-TREATMENT-AND-RANK MAP (nx_compare_rank faithsocial job 1790613338, exit 0, faithsocial.rank sha256 fd025a59): TARGET VERSION 0.1 (M1); rungs 2, done 0, open 2. Critical path: 1 FS11 group safety graded against Facebook Groups and Discord, priority 600 -- cgm_mod_queue, where an admin resolves a planted metadata-only report with no plaintext in the queue, a youth group left with one adult refuses the change, a CSAE report whose sink fails refuses to proceed and a group holding a minor serves no ad, composing grp_can_post, ev_rsvp, room_admit, abuse_score, sink_fails and ca_should_serve; then later 2 FS8 date-safety check-in between adults, priority 666 -- cds_date_checkin with share, check-in, a missed check-in escalating to the trusted contact and the minor refusal, graded against Bumble Share Date (its cross-board dependency connect CN18 reads DONE). Ladder LADDERED: 3 dated targets, 2 of 2 rungs placed, targets_unclimbed=2 -- T-FRONT-AGEBAND and T-FRONT-CIRCLES have no climber here because their climbers moved to connect in the 2026-09-25 consolidation (CN18 for the age band; CN14, CN15 and CN4 for the circles). Barfresh FRESH: SB-FS-APPS and SB-FS-AGE fresh at 2026-09, SB-FS-MATCH attested at 2026-08. Treatment NO-TREATMENT, correctly: the organs FS8 and FS11 contract do not exist yet, so there is nothing to treat. The gap to T-BIC-FAITHSOCIAL closes with FS11 then FS8; both frontier targets close on the connect board (the CN18 caller in the served daemon, then CN4).
2026-09-28RANKlandW16 PUBLISHED: nx_compare_regen_scoped --domain faithsocial (job 1790614419) verdict=GREEN, index.html 242322 to 251313 B, api.json 45923 B; nx_page_verify https://nishifamily.com/compare/faithsocial/ (job 1790614461) status 200 bytes 251313 a11y-issues 0 broken 0 VERDICT=GREEN (static checks; browser rendering unverified).
2026-09-28GAMESqueueW17 GAMES-TOGETHER CROSS-BOARD for the faithsocial board owner (this seat edited no faithsocial row): the Games together inside circles matrix row (runtime/_hdl_build/nx_connect_lds_room_lib.nx room_admit, operator ask REQ 1790361302) now has a rung that owns it -- connect CN19 Games together, one to one or in groups, contract nx_connect_play.cpl_play_move, gate nx_connect_play_gate 112/112 served on /api/gate_run, shipped, registered and rostered (connect.plan row 1790619900); intake 1790361302 is routed there. Two evidence upgrades the row can take: (1) its note codes Discord Yes from general knowledge, NOT read on a pinned page (UNVERIFIED); Discord's Activities overview is now read and pinned on connect.refs as discord-activities (https://docs.discord.com/developers/activities/overview, sha256 23cfea25, a direct fetch with no redirect: Activities are multiplayer games and social experiences built as web apps run in an iframe in Discord on desktop, mobile and web), so a faithsocial.refs row over the same mirror lets the row cite it; (2) pointing the row at runtime/_hdl_build/nx_connect_play.nx cpl_play_move would measure the whole play session (the room rule on join and leave, the one contact rule for one-to-one play, blocks both ways, server-validated moves, a replayable digest) rather than the room rule alone -- or, under the one-owner review R5a, the row becomes a cross-board reference to connect CN19.
2026-09-28FS8landW17 SEAT DATE-SAFETY (resumed after the 12:39 CDT outage killed the first run): the predecessor had landed runtime/_hdl_build/nx_connect_datesafety.nx (cds_date_checkin with the own-account verbs, never compiled), knowledge/connect_datesafety.conf (lead_max_s 2592000 calibrated from Tinder Share My Date, grace_s 0 UNSOURCED) and six mirrors, and died 3631 bytes into the gate. This seat compiled the lib for the first time ('match' is a NishiLang keyword, renamed matched in cds_block_report), corrected two header claims the mirrors did not carry as written (the iOS 27 guide does not state end-to-end encryption, the iOS 17 newsroom does; the Noonlight claim now reads from Noonlight's own home page), wrote nx_connect_datesafety_gate (48355 B, 122 teeth, gv_kv values last before the verdict) and measured it: nx_sov_build_run --qualify job 1790620368 122/122 GREEN; shipped by /api/build job 1790620647 (src_path the gate, sha f1feb09f) and /api/promote job 1790620710 with expect_sha256, registered job 1790620729 (callable 1), nx_offc_install promoted, /api/gate_run job 1790620749 on the PROMOTED binary exit_code 0 verdict GREEN 122/122. Non-vacuity: nx_gate_bite job 1790620471 killed a compiling comparison mutant (restore byte-identical 37827 B), and a planted sharer-band defect turned the gate RED 119/122 on exactly the minor-by-name, refusal-with-a-lane-in-hand and odd-band teeth (job 1790620875); restored from knowledge/bank/nx_connect_datesafety.nx-20260928 (nx_filehash cmp identical, sha a4b78f30) and back to 122/122 GREEN (job 1790620946, a build-cache hit on the promoted bytes). Rostered in knowledge/gateroster.conf; knowledge/compare/faithsocial.gates created with its row. Shipped, gate 122/122, awaiting acceptance.
2026-09-28FS8measureTHE BAR, read 2026-09-28 from mirrored bytes: Bumble Share Date sends a meetup's details to trusted contacts and updates them in real time, with no check-in and no escalation described [bumble-sharedate]; Tinder Share My Date is one link carrying location, date, time and a photo of the match, up to 30 days ahead and editable [tinder-sharemydate]; Apple Check In (iOS 27) offers an After-a-timer mode for meeting someone new, Add Time and Cancel, and on a failed check-in shares location, signal, battery and optionally the route [apple-checkin], end-to-end encrypted per the iOS 17 newsroom [apple-ios17]; Noonlight sells a Dispatch API for emergency response with Tinder in its customer row [noonlight]. WHERE OURS EXCEEDS: nothing about the date is readable by the server (the plan is sealed on the device to the contact's X25519 key; the gate's census of the state image and the contact's segment files finds no word of it, and the image does not hold who the date is with); there is no location field at all, by construction; the escalation is the sharer's own franked message through the existing messaging path, so a report of it is provable; a minor is refused by name and no check-in ever exists for one; block and report are one step. WHERE OURS TRAILS: no automatic arrival detection (Apple's When I Arrive needs location, refused by design); no emergency-services dispatch (Noonlight); no live location for the contact on a failed check-in; and the contact must already hold an accepted relationship lane, a consent guard that is also friction the rivals' open links do not have. Values from the promoted gate: plan 79 B sealed to 127 B, escalation 49 B franked to 129 B, state image 2080 B for five shares, lead_max_s 2592000, grace_s 0.
2026-09-28FS8queueOPEN after this leg, in order: (1) the front-door verbs date_share, date_checkin and date_block_report (with date_extend, date_cancel, date_update and date_plan) are requested of FRONTDOOR-FINISH on connect.plan row 1790621000; they land UNWIRED until the alpha daemon holds the date-safety block beside its room table, and the pure decision date_admit over cds_admit can be wired today; (2) the escalation sweep is a server beat (cds_due, then cds_escalate with cds_channel_verdict at delivery), owed to the daemon owner, not a user verb; (3) the device side (cds_plan_seal and mfr_frank at share time) needs the contact's published X25519 key from the key directory the sealing rung (connect CN7, wave 16) is taking live, and an ephemeral secret from the device CSPRNG; (4) the sealed box has the shape of RFC 9180 HPKE base mode but is not byte compatible (no labeled extract, no suite id) -- a rung to adopt the standard key schedule when an HPKE lib exists; (5) grace_s stays UNSOURCED at 0, the strictest line, until a rival page publishes one; (6) no location, no arrival detection and no dispatch are design refusals, kept on the trail list. The FS8 matrix watch flips on the next regen because the symbol exists in the named organ; the flip is the receipt, the gate is the proof.
2026-09-28FS11landW17 SEAT GROUP-MODERATION: cgm_mod_queue shipped in runtime/_hdl_build/nx_connect_groupmod.nx (30981 B; a pure core with no main, no allocation and no clock) with its gate nx_connect_groupmod_gate 138 of 138 GREEN, promoted by nx_organ_ship sha 492b1c6c (first ship 95840e2f at 123 of 123; the second added the ban and replay teeth), served GREEN through /api/gate_run (138 of 138), registered on the MCP surface, _offc twin installed, rostered in knowledge/gateroster.conf. The done-rule tooth by tooth: an admin sees and resolves a planted report on a franked message whose sender mfr_report_verify proved, and a clock-built canary appears in no byte of the queue's context, report rows or action rows while the same census finds it in an incumbent-style row that copies the post; a youth group left with one adult refuses the change (room_may_leave on the group roster and on every youth event roster the member holds); a CSAE report whose sink model fails its first attempt refuses every action, dismissal included, until cgm_csae_retry delivers it; a group holding a minor serves no ad to any viewer (ca_should_serve with the wall set). The brief's neg-controls: a member and an outsider read an empty queue while the admin reads the same report; a removed member cannot post or RSVP; a reversal restores posting with both rows kept, byte-identical to how they were written. Added after reading the rivals: a report naming an admin is withheld from that admin, a timed mute, a removal that is a ban until reversed by someone of at least the remover's rank, and replay (cgm_load_report and cgm_load_action rebuild a context from stored rows that answers every queue and posting read identically and refuses out-of-order history). Composes grp_can_post, grp_remove, grp_add, ev_rsvp, ev_cancel, room_admit, room_may_leave, abuse_score, sink_fails, ca_should_serve, mfr_report_verify and mfr_report_route; the two rules it restates are bound by teeth (cgm_may_moderate agrees with grp_remove on all 36 ordered pairs of a six-person roster; cgm_signal_flags reproduces the verifier's ten-account population). Non-vacuity: nx_gate_bite killed 4 compiling mutants with byte-verified restores (a position sweep, and aimed sites in the CSAE check, the group-roster youth wall and the ban check). Graded against pages fetched, read and pinned today, Facebook Groups Manage a group [fbgroups-manage] and Discord Auto Moderation [discord-automod]: both moderate by reading content, and both automate more (keyword and criteria automation, post approval, action notes), which the matrix row states as the gap. Board after the land: nx_compare_rank faithsocial rungs 2 done 2 open 0 (both FINISH, LIB-UNCENSUSED until the import census re-runs), nx_ladder LADDERED, nx_barfresh FRESH, scoped regen job 1790621316 GREEN (index 275213 B, api.json 52672 B, the row measures nishi 1), nx_page_verify job 1790621363 GREEN a11y-issues 0 (static checks, browser rendering unverified). Shipped, gate 138 of 138, awaiting acceptance.
2026-09-28FS11landW17 GROUP-MODERATION addendum to row 1790621440: reporting is now IDEMPOTENT under a client retry (cgm_find_open: a report matching an open row by group, reporter, target, reason and franking reference returns that row, so a retried member, message or CSAE report never duplicates a row or makes a second sink attempt, a repeated signal returns the open system report, and a fresh report after a decision files a new row), bite-proven by an aimed kill in cgm_report (5 kills in all). Re-shipped by nx_organ_ship sha b5386d1e, 145 of 145 GREEN, served GREEN through /api/gate_run (14724 B under the 16384 B capture cap, not truncated), with one NAMED loss approved by its artifact-bound token (the tooth 'a full report table refuses by name' renamed 'a full report table refuses a new report by name', because a retry of a filed report now answers with its row) and the behaviour change reviewed against the retained observation (review record knowledge/status/harness/review-nx_connect_groupmod_gate-b5386d1e.record, sha256 b53a1d8e). Scoped regen job 1790622247 GREEN (index 281578 B, api.json 52712 B); the matrix note and knowledge/gateroster.conf carry the 145 figure and the b5386d1e sha. Shipped, gate 145 of 145, awaiting acceptance.
2026-09-28FS11queueOPEN after the FS11 land, in order: (1) a served caller -- cgm_mod_queue is imported only by its gate, so the rung reads FINISH until FRONTDOOR-FINISH wires mod_report, mod_queue_mine and mod_act (VERB REQUEST on connect.plan row 1790621140, with the durable-row replay contract; reports are idempotent, so client retries can pass straight through); (2) LIB-UNCENSUSED clears on the next nx_eco_graph_build and nx_importcensus beat, not by hand; (3) the stated gap against the pinned rivals: a content-blind analogue of Admin Assist (join and post criteria on circle, vouch and account-age metadata, never content), post approval for a member, and a rule reference on each action (the metadata form of an admin note) -- content-reading keyword filters are refused by design and stay a stated gap; (4) a voluntary leave through the youth wall needs a grp_leave in nx_connect_group_lib, which has none, so this organ holds the wall on removal and on every join only; (5) the CSAE path proves fail-closed state against the estate's sink model (sink_fails), not delivery to any authority; the retry ledger inside nx_connect_csae_report main is still to be extracted as a callable (connect.plan row 1790360640 YS5 item 2 is half closed: the sink model is callable now); (6) there is still no faithsocial.gates map, by the BOARD seat's earlier choice; nx_connect_groupmod_gate runs GREEN through /api/gate_run, so the BOARD seat can write the map from that receipt; (7) cgm_mod_queue stays a faithsocial-owned contract until the BOARD or SYNC seat adopts it onto connect.plan and connect.matrix; (8) the four verifier programs whose symbols moved into libs this wave (nx_connect_lds_room, nx_connect_blind_abuse, nx_connect_csae_report, nx_connect_ads) were rebuilt behaviour-identical but not promoted, so their served binaries predate the move and promoting them is their owners' call; (9) the gate compiles the wave-16-owned franking, seal and chat-store sources through nx_connect_franking, so a wave-16 edit that breaks them turns this gate's next build RED while the served binary stays as shipped.
2026-09-28FS8landBEST-IN-CLASS BASELINE FOR THE SEALED PLAN: the predecessor's box had RFC 9180's shape and not its bytes (no labeled extract, no suite id), and no HPKE existed anywhere in the estate (nx_shelltool grep for func hpke over buildroot/runtime, corpus_complete=1, 0 matches). Built runtime/_hdl_build/nx_hpke_lib.nx (base mode; DHKEM(X25519, HKDF-SHA256), HKDF-SHA256, ChaCha20Poly1305; composes nx_x25519, nx_hkdf and nx_chacha20_poly1305, restates none) and its gate nx_hpke_lib_gate, which reproduces the RFC's own Appendix A.2.1 vectors byte for byte [rfc9180]: 47/47 GREEN on its first build (nx_sov_build_run --qualify job 1790621878), shipped by /api/build job 1790622204 and /api/promote job 1790622233 (sha 839be23c), registered (callable 1), bite-proven twice (job 1790622253 a comparison mutant, job 1790622335 an aimed mutant in the nonce computation, both killed, restore byte-identical 17483 B). cds_plan_seal and cds_plan_open now compose hpk_seal_base and hpk_open_base with info = the FS8 label and aad = the sharer's account id; the bespoke HKDF-and-cseal box is retired from the lib. nx_connect_datesafety_gate re-measured 122/122 GREEN on the HPKE box (job 1790622191), re-shipped by /api/build job 1790622408 and /api/promote job 1790622428 (sha 63163eba), and /api/gate_run on both promoted binaries reads exit_code 0, 122/122 and 47/47. Rostered; knowledge/organ_gate.conf declares nx_hpke_lib to nx_hpke_lib_gate; its evidence row joins knowledge/compare/faithsocial.gates. Shipped, gates 122/122 and 47/47, awaiting acceptance.
2026-09-28FS11measureExecuted evidence for this board: knowledge/compare/faithsocial.gates (bare tree, the gates dir nx_swcompare_evidence reads) now carries two rows -- FS8's nx_connect_datesafety_gate, landed by the DATE-SAFETY seat, and FS11's nx_connect_groupmod_gate, appended by this seat (the row stands on its own line; the map ended in a newline). nx_swcompare_evidence faithsocial (job 1790622509) forked both live on the sealed images: GREEN 122 of 122 and GREEN 145 of 145, capture complete, and returned verdict=MEASURED-HONEST (present_axes 26 grounded 26 ungrounded 0, absent 3 all named, gates_green 2 of 2, the partitions reconcile, composition 15 claimed plus 3 declared gaps plus 11 landed watches equals 29 axes). This supersedes the BOARD row of 1790357776, which kept the board CLAIM-ONLY because no product gate could be forked then; the cgm_mod_queue row still reads LANDED-UNFLIPPED (a watch whose symbol is present), which the generator already measures as nishi 1, so the row text was not rewritten.
2026-09-28FS8measureAFTER THE LEG: nx_swcompare_evidence faithsocial (job 1790622684) verdict=MEASURED-HONEST, gates_green=3/3 over knowledge/compare/faithsocial.gates (nx_connect_datesafety_gate 122/122, the FS11 sibling's nx_connect_groupmod_gate 145/145, nx_hpke_lib_gate 47/47), present_axes 26 all grounded, 3 absent named; the date-safety axis reads LANDED-UNFLIPPED (the watch cell measures cds_date_checkin present; converting the watch row into a claim with a Nishi code is a board decision awaiting acceptance, not taken here). nx_compare_rank faithsocial rungs 2 done 2 open 0, both FS8 and FS11 in FINISH as LIB-UNCENSUSED (imported only by their gates until the front door wires the verbs requested on connect.plan row 1790621000); nx_ladder LADDERED; nx_barfresh FRESH; nx_compare_refs_gate fleet 43/45 RED on two provenance-redirect ratchets naming pmdash, automation, search and datavis rows, with mirrors-exist, pins-match and cited-inline PASS across 2241 rows including this seat's six new faithsocial refs. One more trail item read from the Apple guide mirror: Apple prompts the person before a failed Check In notifies the friend and publishes no window, while ours escalates at deadline plus grace with no server-side prompt -- the device should prompt before the deadline, and grace_s stays UNSOURCED at 0.
2026-10-01BOARDmeasureBARFRESH 2026-10-01 (seat residue-fleet, T0 1790856940): before STALE with 3 of 3 bars UNATTESTED on the October clock; after 1 ATTESTED and 2 UNATTESTED, verdict still STALE. Attested from page bytes re-fetched and read this month: SB-FS-APPS (Tinder press room, newest item 30 September 2026, Tinder Launches Group Hangouts, a group-to-group match and chat feature built on Double Date; no October item). Left for the arXiv attest runner and NOT fetched by this seat: SB-FS-AGE (arxiv-age) and SB-FS-MATCH (arxiv-dating), both export.arxiv.org listings. The page needs a regen to show the October barscan.
On these two registers. Rows are declared in the domain's plan file and carry the debt id, which is the join key back to the sovereign debt plane — that plane, not this page, is the authority on state. Reconciling them automatically (the regen reading the plane and refreshing these rows) is a named, owed rung; until it lands, treat an id here as a pointer to look up, not a status to trust.
Honest verdict. The coverage above records source-symbol presence. Stronger comparisons are authored claims, not measured runtime superiority or accepted outcomes. A watch contract names an expected source symbol; finding it changes source discovery only. Qualification, deployment and runtime acceptance require their own evidence.

Person · product · place — not yet measured for this domain

Every compare carries this layer. Declare knowledge/compare/faithsocial.ppp (rows surface|nishi or c1..c4|label|url|connect naming OUR live surface and each rival's front door), run nx_ppp_probe domain faithsocial, and this section fills itself on the next beat: the same ruler on both sides — privacy and CX (third-party hosts, tracker classes, cookies, security headers), design and longevity (design hygiene, computed WCAG contrast, render-blocking resources, unsized media, script weight, theme and motion queries), findability (landmarks, skip link, on-site search, breadcrumb, headings, internal links).

Exclusive and shared capabilities

One capability is graded on one board; every other board references it. The fleet duplicate census (nx_rivalcensus dupes, on the fleetdupes clock row) reads every board's matrix and names each capability graded as a row on two or more boards, with a home derived from evidence: rung when exactly one board's plan contracts the symbol (that board is starred), gates when no plan contracts it and exactly one board's executed gate map runs the organ's gate (that board is plussed), ambiguous when several boards carry the deciding evidence (a decision for their seats), and none when no evidence decides it, with the reason beside it: unmapped (no board of the duplicate declares a gates map; declare the maps) or unproven (a map exists and runs none of the organ's gates; gate the organ on its proving board, or declare it a shared library by policy). A home elsewhere means this board should carry an @xrow reference to the home board's row rather than a graded row of its own; a home here means the other boards should. The table is this board's slice of one estate-wide census: the shape is shared, the rows are the board's.

This board grades 29 capabilities: 6 exclusive to it and 23 shared with other boards. Shared rows on this page: 23 = home here 0 + home elsewhere 13 + ambiguous 0 + undecided 10 + refused 0 (partition 23); undecided = unmapped 0 + unproven 10 + unevidenced 0; homonyms 0; since the previous census: new 0, resolved 0. Census FRESH age_s=7248.

CapabilityOrganBoards grading itHomeRuleEvidenceStanding on this board
mx_inter_popcnx_connect_match_lib.nxconnect*, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|mx_inter_popc|home by rung (fleet duplicate census)
ln_minnx_connect_lanes_lib.nxconnect, faithsocial, youthsafety—noneunprovenundecided
hmixnx_connect_idage.nxconnect+, faithsocial, youthsafetyconnectgatesgateshome elsewhere
adopt: @xrow connect|hmix|home by gates (fleet duplicate census)
yw_may_channelnx_connect_youth_lib.nxconnect, faithsocial, youthsafety—noneunprovenundecided
ev_rsvpnx_connect_events_lib.nxconnect, faithsocial—noneunprovenundecided
hx_findnx_connect_h2h_exceed.nxconnect, faithsocial—noneunprovenundecided
rc_inter_popcnx_connect_lds_reconnect_lib.nxconnect, faithsocial—noneunprovenundecided
abuse_scorenx_connect_blind_abuse_lib.nxconnect, faithsocial, youthsafety—noneunprovenundecided
grp_can_postnx_connect_group_lib.nxconnect, faithsocial, youthsafety—noneunprovenundecided
wd_forbidden_countnx_connect_wards_lib.nxconnect, faithsocial—noneunprovenundecided
room_admitnx_connect_lds_room_lib.nxconnect, faithsocial, youthsafety—noneunprovenundecided
ce_emit_htmlnx_connect_e2e_client.nxconnect+, faithsocial, youthsafetyconnectgatesgateshome elsewhere
adopt: @xrow connect|ce_emit_html|home by gates (fleet duplicate census)
cs_page_loginnx_connect_serve.nxconnect+, faithsocialconnectgatesgateshome elsewhere
adopt: @xrow connect|cs_page_login|home by gates (fleet duplicate census)
gini_permilnx_connect_fair_rank.nxconnect, faithsocial—noneunprovenundecided
cl_mobile_shellnx_connect_client.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|cl_mobile_shell|home by rung (fleet duplicate census)
lq_cohort_seednx_connect_liquidity.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|lq_cohort_seed|home by rung (fleet duplicate census)
nn_match_trainnx_connect_neural.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|nn_match_train|home by rung (fleet duplicate census)
csu_signup_admitnx_connect_signup.nxconnect*+, faithsocial, youthsafety+connectrungplanhome elsewhere
adopt: @xrow connect|csu_signup_admit|home by rung (fleet duplicate census)
ccl_circle_reachnx_connect_circles.nxconnect*+, faithsocial, youthsafety+connectrungplanhome elsewhere
adopt: @xrow connect|ccl_circle_reach|home by rung (fleet duplicate census)
cfa_tradition_admitnx_connect_faith.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|cfa_tradition_admit|home by rung (fleet duplicate census)
csh_need_matchnx_connect_service.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|csh_need_match|home by rung (fleet duplicate census)
cvh_person_attestnx_connect_personhood.nxconnect*+, faithsocial, youthsafetyconnectrungplanhome elsewhere
adopt: @xrow connect|cvh_person_attest|home by rung (fleet duplicate census)
acc_realm_unifynx_connect_realm.nxconnect*+, faithsocialconnectrungplanhome elsewhere
adopt: @xrow connect|acc_realm_unify|home by rung (fleet duplicate census)

Gaps from the record — what the estate does that no board carries

The record census (nx_goalmap record) reads the invoked-tool population and every plan queue row and files each organ or directive that NO matrix, plan or gates row names. A row here is a callout the boards missed: adjudicate it onto a board or declare it infrastructure. Census state STALE (age 1396353 s), sources read 4 of 7 declared — a BLIND census is a FLOOR: unread sources can only add rows.

kindnameboardsourceevidence

rows shown 0|this board's directives 0|estate-wide un-boarded organs 452 (listed in full on /compare/ecosystem)|census rows 639|malformed 0 (counted, never rendered)

References

Beyond a link list. Every reference below resolves twice — the publisher's copy and, where banked, the estate's own non-rottable library mirror with a content pin — and carries its evidence class plus the exact claim on this page it grounds. Keyed marks like [key] in the matrix notes jump here. A dash means honestly absent, never assumed.
  1. [mutual] Mutual. The dating app for Latter-day Saints, home page and FAQ -- serving Latter-day Saint singles worldwide since 2016; building a profile, browsing, matching and messaging free; Premium optional (See Who Likes Me, unlimited likes, more filters); Community Standards; a testimonial from a couple who served their missions together and then matched. publisher · read in our library knowledge/fetched/cmp_faithsocial_mutual.html · pin he4977107e5ae747c20bdbabec94810ab09a61fc03556496b3152b2a548af6c74 · accessed 2026-09-25 · vendor-docGrounds: The Mutual column; the "Member-missionary reconnection", "Zero paywalled connection features" and "Fair exposure" rows; the Mutual research bar.
  2. [christianmingle] Christian Mingle, home page -- its operator states it does not conduct background checks on members or the subscribers of the Christian Mingle dating app and website. publisher · read in our library knowledge/fetched/cmp_faithsocial_christianmingle.html · pin h5320dae3fe856664765859b0159af803dc9a35ea0cd1491b7e65e77d405e6511 · accessed 2026-09-25 · vendor-docGrounds: The Christian Mingle column; the "Verified real person without storing identity" row (no background checks) and the "Christian traditions at equal fidelity" row.
  3. [hinge] Hinge newsroom -- the Selfie Verification badge confirming a person looks like their photos, enhanced verification such as liveness checks, the Comment Filter, and nudges encouraging positive behavior. publisher · read in our library knowledge/fetched/cmp_faithsocial_hinge_newsroom.html · pin h0742e1b3bd3821bf5c9f55cceda4c705fd33b4a3081c4c430ae7402eec407d0b · accessed 2026-09-25 · vendor-docGrounds: The Hinge column; the "Verified real person without storing identity" and "Private sign-up without a stored identity document" rows; the Hinge research bar.
  4. [bumble] Bumble Buzz safety page -- Photo Verification, ID Verification and Share Date, a separate BFF friendship mode, and the 2025 product release naming Discover, ID Verification and Share Date. publisher · read in our library knowledge/fetched/cmp_faithsocial_bumble_buzz_safety.html · pin h8e591d0a57ddda0b81747a998ea241fcf93c7d901e90b4793987430843c10468 · accessed 2026-09-25 · vendor-docGrounds: The Bumble column; the "Verified real person without storing identity" and "Date-safety check-in between adults" rows; the Bumble research bar.
  5. [fbgroups] Facebook Help Center, Groups -- manage a group as an admin or moderator. publisher · read in our library knowledge/fetched/cmp_faithsocial_fbgroups_help.html · pin h0691e5c3f0a2429a3b54e97817bf03f014fba08daa40034ddf9165dc27e6a4f1 · accessed 2026-09-25 · vendor-docGrounds: The Facebook Groups column; the "Concentric circles" and "Groups and channels with roles" rows.
  6. [discord-safety] Discord Safety Center -- the Family Center tool and the Parent's Guide for parents of teens. publisher · read in our library knowledge/fetched/cmp_faithsocial_discord_safety.html · pin h009181e5d372fe7aac8019d473d84bac0aea58837a8b519651053c228515baa9 · accessed 2026-09-25 · vendor-docGrounds: The Discord column; the "Structural adult-minor wall" row and the guardian-visibility clause of the "Concentric circles" row; the Discord research bar.
  7. [discord-teen] Discord press release. Discord launches teen-by-default settings globally -- only users age-assured as adults reach age-gated spaces, unblur sensitive content or speak on stage; messages from people a user may not know go to a separate inbox; friend-request alerts for unknown users. publisher · read in our library knowledge/fetched/cmp_faithsocial_discord_teen.html · pin h8940bf82103fe206a50dd032e38b39064534b9973b7ea3c29fdfcd487de7f2f2 · accessed 2026-09-25 · vendor-docGrounds: The "Verified real person without storing identity" and "Privacy-preserving age assurance" rows (Discord Part); the Discord research bar.
  8. [tinder-press] Tinder press room -- in-app Events launched 16 March 2026, Events expanded globally with 26 markets live by September (23 July 2026), the Double Date series; newest item dated 23 September 2026. publisher · read in our library knowledge/fetched/cmp_faithsocial_tinder_press.html · pin h7c077bdbb4dd9a49c5e8e1bad6b2f636da50e57a87f82030ccfd1dbd8f43f505 · accessed 2026-09-25 · vendor-docGrounds: The best-in-class bar SB-FS-APPS and its barscan; the "Real-world events with RSVP" row.
  9. [arxiv-dating] arXiv listing, online dating sorted by submission date -- 70 results, newest 2026-08-20: two-sided receptivity to conversational AI agents in dating (2608.19545), delegation asymmetry in agentic recommender systems (2608.18058), MODE mutual optimality in reciprocal recommendations (2608.01731), folk deception cues in romance scams (2606.23241). publisher · read in our library knowledge/fetched/cmp_faithsocial_arxiv_dating.xml · pin hddddacad064c212a221989047735ad81c0e43e9d33b7c62653ba9f333d53b318 · accessed 2026-09-25 · mirrored-indexGrounds: The frontier bar SB-FS-MATCH and its barscan; the "Reciprocal matching" row.
  10. [arxiv-age] arXiv listing, age assurance sorted by submission date -- newest 2026-09-11: Reconceptualizing Age Assurance as a Sociotechnical Problem (2609.13598); August: dorsal hand images for XR and privacy-preserving age assurance and child safety (2608.21009); March: assessing age assurance technologies, effectiveness, side-effects and acceptance (2603.25695). publisher · read in our library knowledge/fetched/cmp_faithsocial_arxiv_ageassurance.xml · pin h1f6500a960480377e747b7b73ecb057f56c92238601ebbcddb8d5501f46b8268 · accessed 2026-09-25 · mirrored-indexGrounds: The frontier bar SB-FS-AGE and its barscan; the "Privacy-preserving age assurance" row.
  11. [church-gh20] General Handbook 20.7.1 Adult Supervision, The Church of Jesus Christ of Latter-day Saints -- at least two adults must be present at all Church activities attended by children and youth. publisher · read in our library knowledge/fetched/cmp_faithsocial_church_gh20.html · pin hbf02b62a6cb22da915ef4031bb75b7e14e1cbeb3badefd9b1ae9bd611eb6a897 · accessed 2026-09-25 · published-standardGrounds: The "Structural adult-minor wall" row: the two-deep norm every adult and minor pair on this board obeys.
  12. [rfc9807] Bourdrez, D., Krawczyk, H., Lewi, K., Wood, C. A. RFC 9807: The OPAQUE Augmented Password-Authenticated Key Exchange (aPAKE) Protocol. IETF, 2025. publisher · read in our library knowledge/fetched/cmp_faithsocial_rfc9807.html · pin h0e1ee56460c024fff7057d3743eb73aa4382a4fc274eb484597d6d43b41274cb · accessed 2026-09-25 · published-standardGrounds: The "Passwordless-at-rest login (OPAQUE aPAKE, RFC 9807)" row.
  13. [discord-family] Discord Family Center -- a teen may connect a parent or guardian, who then sees only recently added friends (names and avatars), servers joined or participated in, and users messaged or called, never the content of messages. publisher · read in our library knowledge/fetched/cmp_faithsocial_discord_family_center.html · pin hf542a4f49a31d4cfcc7a2f2c6a96ee052ebc8dded376bce94df633ddbf00c35c · accessed 2026-09-25 · vendor-docGrounds: The guardian-visibility clause of the "Concentric circles" row: the closest rival shape to a guardian seeing a youth friendship.
  14. [ldssingles] LDS Singles (ldssingles.com, Black Cap Holdings LLC) -- home page: Join Free sign-up through a third-party sign-in service (clerk.ldssingles.com), browse profiles of Latter-day Saint singles nearby or across the country, upgrade to premium for more features, iOS and Android apps, Google Tag Manager in the page head, and a footer stating it does not conduct background checks on members or subscribers. publisher · read in our library knowledge/fetched/cmp_faithsocial_ldssingles_202609.html · pin he40455e65258cf62c12e7a1f7c226b67e31cfbccbc77fd1f24f790bc1b438d0a · accessed 2026-09-25 · vendor-docGrounds: The "Games together inside circles (youth only in visible group rooms)" row and the LDS Singles research bar: the Latter-day Saint dating incumbent this ask exceeds, and the LDSSingles column (the Private sign-up, Passwordless-at-rest login, Ward and stake community boundary and Native mobile apps rows).
  15. [ldssingles-appstore] LDS Singles: Dating App by Black Cap Holdings, Apple App Store listing -- features Authentic Profiles, Curated Matches rooted in shared values, Send a Smile to see if the feeling is mutual, Messaging and Read Receipts (unlimited messaging with a paid subscription) and Profile Views for paid subscribers; free to download and explore; in-app purchases 1 Month Premium USD 49.99, 3 Months 104.99 and 6 Months 149.99; rated 18+ and containing Messaging and Chat; 19 ratings averaging 2.6; requires iOS 16.4 or later; its description claims thousands of Latter-day Saints who found love and friendships. publisher · read in our library knowledge/fetched/cmp_faithsocial_ldssingles_appstore_202609.html · pin h05ded8b9157f0bd62e8f523fd678c74d49022bc9483f2dd9ada9605ec8d7c056 · accessed 2026-09-25 · vendor-docGrounds: The LDSSingles column: the Reciprocal matching, Messaging that survives restart, Zero paywalled connection features, Fair exposure, Consented intent lanes, Installed user base, Native mobile apps and Trained matching rows.
  16. [ldssingles-safety] Black Cap Holdings, Online Dating Safety Policy (last modified 21 July 2026), covering Jdate, JSwipe, Christian Mingle, Zoosk and LDS Singles -- automated and human review of profiles, optional photo verification that confirms a live photo matches the profile photos and verifies no identity, age or criminal history, report and block tools on every profile and message, AI and machine learning to detect abuse and scam attempts, removal of prohibited content from profiles or messages, and no comprehensive criminal background checks. publisher · read in our library knowledge/fetched/cmp_faithsocial_ldssingles_safety_202609.html · pin h4482c414fceb91c74b9ec8132c3ba95821c2499ee8637d5d3271672c8f5f1afd · accessed 2026-09-25 · vendor-docGrounds: The LDSSingles column: the Verified real person, Privacy-preserving age assurance, Group moderation queue, Christian traditions, Date-safety check-in, Content-blind abuse and scam detection, End-to-end sealed messages, One family account and Trained matching rows.
  17. [ldssingles-privacy] Black Cap Holdings, Privacy Policy -- a third party (Persona) confirms with a selfie tool that a member is a real person and keeps the facial template and reference selfie, with government-ID verification an optional feature; identifiers collected include name, address, telephone number, account name and password and government ID; religious affiliation is collected as sensitive data; profiles may be displayed across the operator's affiliated dating services; information found to come from a child under 18 is deleted. publisher · read in our library knowledge/fetched/cmp_faithsocial_ldssingles_privacy_202609.html · pin h4e1e8d61f5466fa64af876d62db797984c258a88d0bdbbd4e5884439f4964047 · accessed 2026-09-25 · vendor-docGrounds: The LDSSingles column: the Private sign-up, Passwordless-at-rest login, Verified real person, Concentric circles, Christian traditions, End-to-end sealed messages and One family account rows.
  18. [ldssingles-terms] Black Cap Holdings, Terms of Use -- the platform is offered only to users 18 years of age or older, and paid access is a monthly subscription under a recurring payment authorization, cancelled through the account, the Apple App Store or Google Play. publisher · read in our library knowledge/fetched/cmp_faithsocial_ldssingles_terms_202609.html · pin h2addc3c4d4d79d08100f9678b5079ddd365a7eb53868520413aff40531acc112 · accessed 2026-09-25 · vendor-docGrounds: The LDSSingles column: the Privacy-preserving age assurance, Structural adult-minor wall and Zero paywalled connection features rows.
  19. [fbgroups-manage] Facebook Help Center, Manage a group -- the admin and moderator tool set, read 2026-09-28: Member-reported content, where an admin notified of a member's report keeps or removes the post, removes, bans or suspends the member or turns on post approval for them (a report to Facebook itself is anonymous); suspension temporarily stops a member posting, commenting and reacting; the activity log shows the actions admins, moderators and Admin Assist took over the past year and lets them undo some and add a note; Admin Assist decides automatically on the content of the post, the author and past moderation decisions; articles on moderation alerts and a Flagged by Facebook review. publisher · read in our library knowledge/fetched/cmp_faithsocial_fbgroups_manage_202609.html · pin h54d0d35b89734235f4722a8f517dc04f02673d7294efb72b47a4c0d7a7001328 · accessed 2026-09-28 · vendor-docGrounds: The "Group moderation queue, content-blind" row (rung FS11): the Facebook Groups Best code and the grading of cgm_mod_queue.
  20. [bumble-sharedate] Bumble Buzz, We've Created More Ways to Help You Find Love on Bumble with Discover, ID Verification, Share Date, and More (17 March 2025) -- Share Date lets a member send the details of a meetup to trusted contacts so they know where the member is and who they are with, updated in real time from the app; the page describes no check-in and no escalation. publisher · read in our library knowledge/fetched/cmp_faithsocial_bumble_share_date.html · pin h672a335dc1aafd560e21effed4a31340cef5af105d1270e09c8039655766eeb1 · accessed 2026-09-28 · vendor-docGrounds: The "Date-safety check-in between adults" row and rung FS8, graded against Bumble Share Date.
  21. [discord-automod] Discord Safety Center, Auto Moderation in Discord -- AutoMod keyword filters (one Commonly Flagged Words filter with Insults and Slurs, Sexual Content and Severe Profanity lists, plus up to 3 custom filters of up to 1,000 keywords each, with role and channel exemptions) and mention-spam and spam-content filters, whose automatic responses block the message, time the member out (no messages, reactions, voice or video for the period; moderators and admins can remove the timeout) or send an alert to a logging channel that previews the full content of the flagged message. publisher · read in our library knowledge/fetched/cmp_faithsocial_discord_automod_202609.html · pin h3801db16262ed2c2288108b6fe972908a02f5447d37db607e51bba13ed1c4bc4 · accessed 2026-09-28 · vendor-docGrounds: The "Group moderation queue, content-blind" row (rung FS11): the Discord Yes code and the grading of cgm_mod_queue.
  22. [tinder-sharemydate] Tinder press room, Shortcut Your Dating Admin Thanks to Tinder's Share My Date (22 April 2024) -- one link shares date information including location, date, time and a photo of the match; members choose who receives it and create an unlimited number of dates up to 30 days in advance; plans are editable. publisher · read in our library knowledge/fetched/cmp_faithsocial_tinder_share_my_date.html · pin h46b40176f2c7bd0aeede27b345593c16410999b1d577676650f8f21f340ed67b · accessed 2026-09-28 · vendor-docGrounds: Rung FS8 and the lead_max_s row of knowledge/connect_datesafety.conf (30 days); the location and match-photo fields ours refuses by construction.
  23. [apple-checkin] Apple, iPhone User Guide for iOS 27, Use Check In on iPhone -- When I Arrive, and After a timer (for example when meeting someone new) that notifies a friend if the Check In is not ended in time; Add Time; Cancel; Check In Data Limited (current location, network signal, battery) or Full (adds the route travelled and the last unlock). publisher · read in our library knowledge/fetched/cmp_faithsocial_apple_checkin_guide.html · pin h2bd79ea2b0c9ee9dcc6eb1ff88b32b17df99076a9f78862d1213fdca8e09faab · accessed 2026-09-28 · vendor-docGrounds: Rung FS8: the best-in-class check-in (Apple-only), the model for check in, add time (cds_date_extend) and cancel (cds_date_cancel).
  24. [apple-ios17] Apple Newsroom, iOS 17 makes iPhone more personal and intuitive (June 2023) -- Messages Check In notifies a family member or friend on arrival; if the user is not making progress, the device location, battery level and cell service status are temporarily shared with the selected contact, and any information shared is end-to-end encrypted. publisher · read in our library knowledge/fetched/cmp_faithsocial_apple_checkin_ios17.html · pin h624379330d782ff89256990c4c8ac227ec72d54f48f1fa31061fd7c3c4fcee3d · accessed 2026-09-28 · vendor-docGrounds: Rung FS8: the end-to-end encryption of Apple Check In and the location, battery and signal it shares on a failed check-in.
  25. [noonlight] Noonlight home page -- a Dispatch API to integrate emergency response, a Personal Safety product with 24/7 protection and remote dispatching, and the Tinder logo in its customer row. publisher · read in our library knowledge/fetched/cmp_faithsocial_noonlight_home.html · pin haefb38397ca997a0d6cb045e7f92edef437cdd7e204ea17b157a5d9f12c58e1b · accessed 2026-09-28 · vendor-docGrounds: Rung FS8: where ours trails -- no emergency-services dispatch.
  26. [rfc9180] Barnes, R., Bhargavan, K., Lipp, B., Wood, C. RFC 9180: Hybrid Public Key Encryption. IRTF, February 2022 -- the labeled KDF, DHKEM(X25519, HKDF-SHA256), the base-mode key schedule, nonce computation, the exporter, and the Appendix A.2.1 Base Setup test vectors for DHKEM(X25519, HKDF-SHA256), HKDF-SHA256, ChaCha20Poly1305. publisher · read in our library knowledge/fetched/cmp_faithsocial_rfc9180.txt · pin hf45a8b7c30231b26d668b1e8168074e5ab514b174d656b67e859895117f1f8f6 · accessed 2026-09-28 · published-standardGrounds: Rung FS8: the sealed box the date plan uses (nx_hpke_lib, reproduced byte for byte against Appendix A.2.1 by nx_hpke_lib_gate).

generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/faithsocial.matrix · source checks show implementation presence; runtime and user-outcome evidence are reported separately · JavaScript supports page controls