Titan Mem — Team Hub Dashboard

Active Team Knowledge Nodes

142

+18 indexed this week

Tool Schema Interceptions

1,280

Dynamic in-process pruning turns

Cross-Seat Query Recalls

640

Agent hits against verified team solutions

Prompt Telemetry

0 bytes

100% private • No prompts logged or monitored

Live Hub Activity Stream (Team Pushes)

Rule [email protected] (Principal Dev) • 2 hours ago git: 8f2a1b4

Synced to 8 Spokes

K8s cgroups v2 jemalloc OOM prevention

When deploying Rust services on K8s with cgroups v2, always set env MALLOC_CONF=background_thread:true. Without it, idle dirty pages purge stalls, triggering kernel OOM kill despite low active RSS.

# deploy/helm/values.yaml

+ env:

+ - name: MALLOC_CONF

+ value: "background_thread:true" # cgroups v2 OOM fix

#kubernetes #rust #jemalloc #cgroups-v2

Pattern [email protected] (Senior Backend) • 5 hours ago git: c49e721

Synced to 8 Spokes

Zero-Copy SQLite WAL PRAGMA settings for concurrent daemons

Use PRAGMA journal_mode=WAL; PRAGMA synchronous=NORMAL; PRAGMA busy_timeout=5000; to eliminate database locked errors when background collectors run in parallel.

# src/db/connection.rs

+ conn.execute_batch("PRAGMA journal_mode=WAL; PRAGMA synchronous=NORMAL;")?;

- conn.execute_batch("PRAGMA journal_mode=DELETE;")?;

#sqlite #wal #performance

Decision [email protected] (Staff Arch) • Yesterday git: e190d5a

Synced to 8 Spokes

Supersede Node.js reverse proxy with Native Axum/Tokio Engine

SUPERSEDES decision #89. Node.js gateway memory consumption spikes to 400MB under 10k connections. Migrated all HTTP routing to compiled Tokio/Axum binary (<18MB RAM).

# Dockerfile

+ FROM rust:alpine AS builder

- FROM node:20-alpine

#architecture #gateway #axum

Active Team Seats (8 / 10)

RC

Rick S. (Team Lead)

Claude Code • Linux Workstation
EB

Elena B.

Cursor • MacBook M3
ML

Marcus L.

Claude Code • Remote Devbox
JD

Junior Dev A

Cursor • MacBook Pro

Team Activation Key

tm_team_live_9x8f2k01a...

Teammates activate via CLI: titan-mem activate <key>

Local-First Persistence

All team memories synchronize directly into your local NVMe storage. No proprietary web export lock-in—query anytime directly:

sqlite3 ~/.titan/mem/memory_graph.db