You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See parent EPIC #28 for full mission scope, threat model (TM-1..TM-10), R-CHAT laws (R-CHAT-1..R-CHAT-12), acceptance gates G-C1..G-C10, and 21 cited sources.
Detailed design: docs/chat/trinity-chat-design.md (added in PR feat/trios-chat-epic).
cargo run --bin falsifier_runner — direct 100 % / indirect 90 % / multi-turn 100 %
cargo test --tests r_chat_guard — 3/3 pass
6 Coq theorems Defined + 1 Admitted (R5 budget honored)
200-attack falsifier corpus committed
10 ADR-CHAT-001..010 + 29 KB design doc with 21 sources
Honesty (R5)
Lanes 3 (MLS) and 5 (Persistence) are explicitly [ASPIRATIONAL] in this
scaffold — ADR-CHAT-001 / ADR-CHAT-008 capture the design; full impl lands
in follow-up PRs. Coq INV-CHAT-4 (sender unlinkability) is Admitted
within the documented R5 budget.
Checked against gHashTag/trios main at 8b229e9 (2026-09-24). Trios CI on that commit is green: run 36028910601 runs the unit tests of crates/trios-chat/rings/*.
The 2026-07-07 comment points to gHashTag/trios-mesh#21. That repository returns 404 for this account, so I cannot confirm that PR was merged, and it is not counted here. Leaving this open.
On trios main:rings/CR-CHAT-02 has the root/chain KDF, dh_kem_step (takes a 32-byte KEM secret), FS/PCS key-divergence tests (rfs_01..rfs_05, post_compromise_security_after_dh_step_recovers) and deniable::den_06_no_per_message_signature. They pass in CI.
Missing:
The ring calls itself a "Triple Ratchet skeleton" and tags the full Double/Triple Ratchet [ASPIRATIONAL] (lib.rs header).
Activity
gHashTag commentedon May 9, 2026
🔥 IGNITE — Trinity Secure Chat scaffold landing
PR: Trinity-S-AI-DNA/trios#631
Local trios tracker: Trinity-S-AI-DNA/trios#632
Verification snapshot [VERIFIED]
cargo test -p trios-chat --lib— 35/35 passcargo run --bin e2e_chat_25— 25/25 passcargo run --bin falsifier_runner— direct 100 % / indirect 90 % / multi-turn 100 %cargo test --tests r_chat_guard— 3/3 passHonesty (R5)
Lanes 3 (MLS) and 5 (Persistence) are explicitly
[ASPIRATIONAL]in thisscaffold — ADR-CHAT-001 / ADR-CHAT-008 capture the design; full impl lands
in follow-up PRs. Coq
INV-CHAT-4(sender unlinkability) isAdmittedwithin the documented R5 budget.
L1 ✅ no
.sh· L2 ✅Closes #632in PR body.gHashTag commentedon May 9, 2026
🔥 Wave-2 — harden + tighten
Wave-2 PR: Trinity-S-AI-DNA/trios#633
Builds on PR #631 (scaffold).
Verification snapshot [VERIFIED]
Lifted from [ASPIRATIONAL] in this PR
L1 ✅ · L2 ✅
gHashTag commentedon Jul 7, 2026
✅ L-CHAT-2 implemented → trios-mesh PR #21
PR: https://github.com/gHashTag/trios-mesh/pull/21
Files:
src/chat/x3dh.rs+src/chat/ratchet.rsPQXDH (X25519×4 + ML-KEM-768 → HKDF root) + triple ratchet (symmetric + DH + KEM). Deniable (no per-message signature).
decrypt()stages-then-commits so a forged message can't desync state.Gate: G-C2 (FS/PCS) + G-C10 (no per-msg sig on the wire).
Part of EPIC #28. 163 tests green · fmt + clippy -D clean.
dmitrii-f-t27 commentedon Oct 11, 2026
Checked against gHashTag/trios
mainat 8b229e9 (2026-09-24). Trios CI on that commit is green: run 36028910601 runs the unit tests ofcrates/trios-chat/rings/*.The 2026-07-07 comment points to gHashTag/trios-mesh#21. That repository returns 404 for this account, so I cannot confirm that PR was merged, and it is not counted here. Leaving this open.
On trios main:
rings/CR-CHAT-02has the root/chain KDF,dh_kem_step(takes a 32-byte KEM secret), FS/PCS key-divergence tests (rfs_01..rfs_05,post_compromise_security_after_dh_step_recovers) anddeniable::den_06_no_per_message_signature. They pass in CI.Missing:
[ASPIRATIONAL](lib.rsheader).dh_kem_stepfixed bytes, not an ML-KEM-768 encapsulation (and the bundle's ML-KEM key is a placeholder, see 🔐 L-CHAT-1: Identity & Onboarding — Ed25519 + X25519 + ML-KEM-768 prekey bundle #29).Dmitrii Fedorov (@dmitrii-f-t27)