ad4134e280
- Eliminate the tidal/ self-contained doc mirror; docs now have two canonical homes (root *.md and docs/), with planning/specs/research/reviews moved up - Remove stale .agents/skills and .ai mirrors; canonicalize skills under .claude/ - Add pre-commit hook + scripts/check-docs.sh doc-guard + scripts/install-hooks.sh - Implement M0-M10 seven-dimension review findings across engine, net, server, and tidalctl (durability, replication, query, WAL, storage, CLI hardening) |
||
|---|---|---|
| .. | ||
| app | ||
| components | ||
| engine | ||
| lib | ||
| .eslintrc.json | ||
| .gitignore | ||
| architecture.md | ||
| devsetup.md | ||
| dump-briefs.mjs | ||
| next-env.d.ts | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.mjs | ||
| README.md | ||
| ROADMAP.md | ||
| test-briefs.mjs | ||
| test-briefs.sh | ||
| tsconfig.json | ||
| tsconfig.tsbuildinfo | ||
| tunnel.sh | ||
| vision.md | ||
iknowyou
Communication personalization as a signal-processing problem. iknowyou wraps tidalDB's signal ledger, preference vectors, and windowed aggregation with an observation pipeline (LM-as-classifier), a briefing engine (query-to-profile), and a generation interface (brief-to-prompt) — so a system can learn how each person prefers to be communicated with and adapt continuously, without a training loop or feature store.
Design vs shipped. The vision/architecture docs describe the target tidalDB-native design; what runs today is a Next.js + vLLM implementation. See the roadmap and dev setup for current state.
Docs
| Doc | What it covers |
|---|---|
| vision.md | The problem and the product thesis (target design) |
| architecture.md | Domain model, pipelines, components (target design) |
| ROADMAP.md | Milestones and current build status |
| devsetup.md | Running the engine + Next.js app locally |
| engine/README.md | The personalization engine service |
Part of the tidalDB workspace's applications/ example consumers — see the
repository root for the database itself.