---
name: META-DB ↔ REI-AIOS full auto-sync future goal
description: Long-term target for fully automatic real-time synchronization between private rei-aios META-DB and public rei-open-problems (beyond current 24h daily cycle)
type: project
originSessionId: 2812f631-04af-4dd8-a8cd-4f872e1e1383
---
**Goal**: 全自動リアルタイム同期 between private rei-aios (data/open-problems/) and public rei-open-problems. No manual intervention, no 24h delay.

**Why**: reduce friction between private development and public dissemination; ensure Rei-AIOS contributions become world-visible without human bottleneck. 藤本さん 2026-04-24 session verbal expression.

**Current state (commit cfd835b, 2026-04-24)**:
- ✓ (C) `npm run publish:metadb` — manual one-command sync
- ✓ (B) `rei-learning-cycle.bat` Phase 8 — auto daily 14:10 JST
- Max delay: 24h when no manual trigger; PC off during 14:10 skips that day

**How to apply**: when user requests or opportunity arises, propose upgrading via one of:
- (D) post-commit git hook on rei-aios: fires on every commit touching `data/open-problems/`
- file-watcher daemon: real-time but requires background process
- (A) GitHub Actions: tempting but 藤本さん expressed concern re Actions error rate (2026-04-24); prefer local-based solutions unless Actions reliability improves significantly

**Tradeoff**: real-time vs reliability vs simplicity. Current daily cycle is reliable and simple; upgrading sacrifices one of those unless carefully designed.

**Precondition to revisit**: when META-DB update cadence exceeds daily (e.g., auto-approved Rei inventions flow increases), or when external users begin actively tracking the public repo in near-real-time.