OS — Home

reminder Continue virtual company build: Ops Monitor is deployed and filed first report (3 products unreachable). Next steps: (1) Wire cron trigger for 30-min auto-runs, (2) Build Team Activity dashboard page, (3) Build second employee (Research Agent). Plan: context/plans/virtual-company-architecture.md. Aliases ready: ops-monitor, consolidate, quorum-check, decay, synthesis. →

reminder Kin has no DB migration system — schema.sql changes don't propagate to running DBs (local or production). The role column incident proved this. Build either: (1) a migrations/ directory with numbered SQL files and a startup runner, or (2) a startup diff that compares schema.sql column definitions against information_schema and warns/auto-applies. Repo: ~/dev/kin, schema: src/server/schema.sql, DB init: src/server/db.ts →

reminder Review post-compaction recovery effectiveness data. V7 deployed 2026-03-12 — check Recovery Effectiveness card on /reliability for production metrics. Compare production signal/notes/learnings rates against benchmark predictions (85%/100%/100%). If production diverges significantly from benchmark, investigate whether the full context (CLAUDE.md + compaction summary + recovery text) creates different dynamics than the isolated benchmark. Update cognitive-principles.md #12 and #13 with production findings. →

task Context Refresh Architectures — Research Paper. Formalize CRA framework, design experiments, collect data, publish. Blocked: OS system must reach steady state first. See [projects/context-refresh-paper.md](projects/context-refresh-paper.md) — active for 22 days →

connection 6 signals about publication in 30 days but no file updates — knowledge may not be captured →

connection 39 signals about core in 30 days but no file updates — knowledge may not be captured →

connection 7 signals about context/chief-of-staff/voice-interface.md in 30 days but no file updates — knowledge may not be captured →

connection 5 signals about kin/product in 30 days but no file updates — knowledge may not be captured →

connection 8 signals about ops/docker in 30 days but no file updates — knowledge may not be captured →

connection 25 signals about context/publication in 30 days but no file updates — knowledge may not be captured →

connection 15 signals about context/plans in 30 days but no file updates — knowledge may not be captured →

connection 7 signals about context/tasks/projects/cognitive-infrastructure-ecosystem.md in 30 days but no file updates — knowledge may not be captured →

connection 9 signals about core/process in 30 days but no file updates — knowledge may not be captured →

connection 7 signals about context/initiatives in 30 days but no file updates — knowledge may not be captured →

connection 6 signals about research/social-simulation in 30 days but no file updates — knowledge may not be captured →

connection 6 signals about publication/experiment-log in 30 days but no file updates — knowledge may not be captured →

connection 16 signals about sinew/product-strategy in 30 days but no file updates — knowledge may not be captured →

connection 5 signals about publication/substack in 30 days but no file updates — knowledge may not be captured →

connection 9 signals about career/learnworlds in 30 days but no file updates — knowledge may not be captured →

connection 19 signals about context/research in 30 days but no file updates — knowledge may not be captured →

connection 8 signals about context/sinew in 30 days but no file updates — knowledge may not be captured →

connection 8 signals about soma in 30 days but no file updates — knowledge may not be captured →

connection 18 signals about sinew in 30 days but no file updates — knowledge may not be captured →

connection 11 signals about publication/threads in 30 days but no file updates — knowledge may not be captured →

connection 8 signals about context/ops/security-audit.md in 30 days but no file updates — knowledge may not be captured →

connection 11 signals about context/dev-skills in 30 days but no file updates — knowledge may not be captured →

connection 10 signals about ops/infrastructure in 30 days but no file updates — knowledge may not be captured →

connection 7 signals about sinew/nerv in 30 days but no file updates — knowledge may not be captured →

connection 7 signals about people in 30 days but no file updates — knowledge may not be captured →

connection 6 signals about career/learnworlds/recommendations-kb in 30 days but no file updates — knowledge may not be captured →

connection 12 signals about context/publication/threads/compaction-survival.md in 30 days but no file updates — knowledge may not be captured →

connection 6 signals about ops/deploy in 30 days but no file updates — knowledge may not be captured →

connection 5 signals about engineering in 30 days but no file updates — knowledge may not be captured →

connection 12 signals about context/core in 30 days but no file updates — knowledge may not be captured →

connection 28 signals about ops in 30 days but no file updates — knowledge may not be captured →

connection 12 signals about publication/research in 30 days but no file updates — knowledge may not be captured →

connection 34 signals about context/ops in 30 days but no file updates — knowledge may not be captured →

Focus

Foresight

Quick Settings

Theme

Integrations

Options

Sync