ARCIVE is a hardware + software platform that lowers the barrier to record, retrieve, interact, and create memories — past, present & future — for individuals, friends, and family.
Every page on this site is rendered directly from a markdown file in docs/ on the repo’s master branch. Edit a .md file → push → site rebuilds. No sync step, no second copy.
Start here
Master Plan
Product thesis, current-state architecture (with diagrams), strategic principles, phased roadmap, monetization tiers, and the risk register.
Progress
Living status of the build. What's shipping now, what's next, what's paused. Updated as work moves between buckets.
Decisions (ADRs)
Architecture Decision Records — immutable once accepted. The "why" behind every meaningful technical call, with options considered and consequences.
Discussions
Working session notes — exploratory, dated, partner-facing. Where alignment happens before decisions get promoted to ADRs.
Software Plan
Detailed software architecture — stack rationale, AI layer model, per-phase deliverables, integration contract surfaces.
Hardware Plan
Hardware track — XVF3800 + ESP32-S3 firmware, BLE GATT schema, enclosure phases, OTA strategy.
Operations
Runbook for deploys, secret rotation, on-call basics. Plus the sharing guide for distributing docs across the team.
Dev Journal
Chronological narrative of the build. Daily working notes, what we tried, what we learned.
Where to look (quick triage)
| You want to know… | Read |
|---|---|
| Why we made some choice | Decisions index — search by keyword |
| What’s the AI architecture | Master Plan §2.7 Architecture → ADR-0011 vendor strategy |
| What we shipped recently | Progress — Just shipped |
| What’s the story behind a feature | Dev Journal — chronological narrative of the build |
| What might we explore next | Discussions — exploratory, dated |
Source-of-truth split
Repo
/docs/is the engineering source of truth — ADRs, plans, runbook, all immutable-once-accepted. This site is the rendered, partner-friendly view of the same content. The Notion mirror is the partner-collaboration surface — discussions get partner sign-off there before being promoted to ADRs in the repo.All three are kept in lockstep via the
/sync-notionslash command and the docs site’s auto-rebuild on git push.