Skip to content

Repository README

Arun Prakash N edited this page Aug 14, 2026 · 10 revisions

Canonical source: README.md · Snapshot commit: dbd497b496c0

Life in Days

Life in Days is a proposed private, single-user visual memory archive that brings together textual VoiceNotes journals, Telegram photos, and manually uploaded .txt or .md journals as trustworthy, calendar-based Journal Days.

Important

This repository contains a planning baseline and throwaway static UI prototypes built with fictional data. It is not a working or deployed application. No integration, persistence, authentication, backup, recovery, accessibility-conformance, or production-readiness claim is made.

Life in Days fictional calendar prototype

Product principles

  • Authentic journals and photos remain distinct from AI-derived titles, summaries, tags, briefs, and artwork.
  • Real photos and photo-derived data must never be sent to AI providers.
  • Journal Dates use fixed Asia/Kolkata time while immutable original timestamps are preserved.
  • The MVP is private and single-user, with no sharing, public links, reminders, coaching, or historical import.
  • Backdating is deliberate and visible; receipt time is never silently treated as the Journal Date.

Current status

Area Status
Phase 1 Product Council package Complete as a planning artifact; 58 work packages across P0 and R0–R10
P0 execution authority Activated under a five-seat execution council; local/public/synthetic work only until each named gate passes
Per-task Product Council gate 58 six-artifact P0 dossier bundles generated as drafts; 58 Incomplete/Hold, 0 Ready, and 0 with executionAllowed=true
Release PRDs/PID Council-reviewed planning baselines; task-specific approval and executed evidence remain separate
R0 shared-host coexistence spike Historically In progress; restricted to readiness/control documentation until its task dossier passes; no private-host probe authorized
Latest frozen UI prototype v10 Resilient Application Shell
Product implementation and deployment Substantive implementation has not started; live state is Unknown — private read authority pending; no implementation release is Done
Conditional storage transition R10 is trigger-gated and intentionally has no dates

The prototypes use browser-memory-only behavior and simulated states. They do not connect to VoiceNotes, Telegram, AI providers, storage, authentication, backup, or recovery systems.

Start here

Area Document
AI-agent operating contract Living Phase 1 roadmap and Excel instructions
AI-agent orientation Phase 1 AI Agent Resource Index — 2026-08-14 15:10:39 IST
Autonomous execution goal Codex Goal prompt — Phase 1 P0 requirements to private production
Complete navigation Document index
Phase 1 council decision Product Council Decision Record
Current execution authority P0 Execution Authorization
Five-seat execution council P0 Execution Council Charter
Per-task start gate P0 Task Definition of Ready
Task artifact register P0 Task Artifact Register
Task readiness state P0 Task Readiness State
Task dossier library P0 Task Work Items
Owner-only dependencies P0 Owner Action Ledger
Detailed release plan Phase 1 Release Plan
Review workbook Phase 1 Excel Release Plan
Live visualization Life Reflection GitHub Project
Product intent Proposed shared understanding
Requirements Product Requirements Document
Release requirements Release PRDs and conditional PID
Experience UX Specification
Phase 1 design review UX Design Review
Architecture Phase 1 Implementation Plan
Shared-host deployment Hetzner Shared-host Spike
Wayfinder adoption Wayfinder Phase 1 Adoption Report
GitHub roadmap research GitHub Projects Roadmap Research
Historical roadmap pilot GitHub Roadmap Design Spike
Delivery task source Phase 1 Roadmap Manifest
Roadmap synchronization GitHub Project Sync Runbook
Prototype roadmap Prototype Completeness Tracker
Requirement coverage Requirements Traceability

The project Wiki mirrors every Markdown project artifact into reader-friendly pages. The version-controlled source documents and their stated precedence remain authoritative.

GitHub history begins with a sanitized snapshot of the current project files. Machine-local paths and pre-publication author metadata are intentionally excluded, while the local repository retains the earlier development history. Some documents preserve earlier commit identifiers as evidence labels; those identifiers may not resolve in the public repository. See Publication provenance.

Run the latest static prototype

Node.js is the only runtime requirement. No package installation, live service, or credential is used.

cd prototypes/calendar-ui
npm run check:v10
npm run prototype

Then open:

http://127.0.0.1:4173/index-v10.html?view=calendar&month=2026-08

The root / route is the historical v1 prototype, so use the explicit v10 URL. See the v10 run guide for its exact scope and evidence boundary.

Repository map

  • docs/discovery/ — decisions, source research, and provider evaluation plans
  • docs/product/ — detailed product requirements
  • docs/design/ — experience and accessibility specification
  • docs/architecture/ — proposed implementation and operations plan
  • docs/research/ — Phase 1 deployment and integration spikes
  • docs/spikes/ — bounded design spikes and pilot proposals
  • docs/project/ — gates, tasks, traceability, and prototype roadmap
  • docs/council/ — governance, role charters, and review records
  • docs/work-items/ — six P0-prefixed task-bound Product, Architecture, Design, QA, Delivery, and Council artifacts for every canonical issue
  • docs/prototypes/ — versioned handoffs, council decisions, and screenshots
  • outputs/ — generated review artifacts, including the Phase 1 Excel plan
  • tools/ — deterministic generators and GitHub synchronization utilities
  • prototypes/calendar-ui/ — dependency-free static prototype versions
  • design-qa*.md — bounded, version-specific prototype QA records
  • PUBLICATION.md — public-snapshot scope and provenance

Privacy boundary

The checked-in prototype media and journal content are fictional fixtures. Never commit real journals, photos, identifiers, credentials, provider responses, private URLs, or descriptions derived from private photos. See Security for private reporting instructions if sensitive material is exposed.

Contributing

This is an owner-led personal project. Read Contributing before proposing a change, especially the synthetic-data and frozen-prototype rules.

License

No open-source license has been selected. Copyright remains with the repository owner; the public repository does not by itself grant reuse rights.

Life in Days

Home

Product, experience, architecture, and delivery

Discovery and research

Governance and council

Prototype handoffs

Prototype run guides

Prototype councils

QA and audits

Repository and project record

Evidence and maintenance

Clone this wiki locally