Skip to content

Documentation Index

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

Canonical source: docs/INDEX.md · Snapshot commit: b9f2813f22e4

Life in Days — document index

Updated: 2026-08-14

This is the single navigation point for the Life in Days product, design, architecture, delivery, research, and governance documents.

Current status: G0 planning baseline complete. G1 is blocked on Arun's explicit confirmation of the proposed shared understanding. No implementation, credential collection, paid evaluation, provider configuration, infrastructure mutation, deployment, recovery exercise, or production verification is implied by these documents.

Start here

Document Purpose Current role
Proposed Shared Understanding Concise statement of the product promise, MVP boundary, capture model, AI/privacy rules, recovery direction, and deferrals. Next owner action: Arun's explicit confirmation closes G1.
Product Requirements Document Complete product contract with 78 prioritized requirements, acceptance behavior, data handling, risks, and non-goals. Council-approved G0 planning baseline.
UX Specification Information architecture, screens, flows, states, content language, responsive behavior, accessibility, and validation plan. Council-approved G0 planning baseline; no usability testing claimed.
Project Tracker G0–G9 gates, 12 milestones, 23 epics, 211 executable tasks, dependencies, evidence, risks, decisions, and 24 backlog items. Authoritative planning/status tracker. G1 is the current blocker.
Implementation Plan Proposed architecture, domain model, integrations, jobs, security, storage, backup, testing, deployment, rollback, and technical gates. Council-approved planning recommendation; implementation is not authorized.
Requirements Traceability Maps each of the 78 PRD requirements to UX coverage, tracker tasks, architecture sections, and planned evidence. Planning coverage is complete; code and executed evidence remain future work.
Product Council Review Records specialist reviews, resolved findings, validation results, approvals, and G0 disposition. Evidence that the integrated planning baseline passed council review.

Product governance and council

Document What it contains
Product Council Charter Council mandate, membership, source precedence, decision rights, review workflow, G0–G9 gates, RACI, and change control.
Council Review Final G0 review record and the material contradictions resolved during reconciliation.
Senior Product Manager Charter Product role mission, owned outputs, responsibilities, decision rights, review checklist, and guardrails.
UI/UX Design Lead Charter Design role mission, owned outputs, responsibilities, decision rights, review checklist, and guardrails.
Project Manager Charter Delivery-governance role mission, owned outputs, responsibilities, decision rights, review checklist, and guardrails.
Technical Architect Charter Architecture role mission, owned outputs, responsibilities, decision rights, review checklist, and guardrails.

Product, experience, architecture, and delivery

Discipline Primary document Use it for
Product Product Requirements Document Product scope, user stories, exact behavior, acceptance criteria, priorities, non-goals, data handling, and risks.
Experience UX Specification Navigation, page anatomy, interaction rules, empty/error/conflict states, responsive design, accessibility, and content language.
Architecture Implementation Plan Proposed technical shape, persistence, integrations, security/privacy enforcement, AI orchestration, storage, operations, tests, and phased implementation.
Delivery Project Tracker Gates, milestones, epics, tasks, dependencies, statuses, evidence requirements, critical path, registers, and backlog.
Coverage Requirements Traceability Requirement-by-requirement navigation across Product, UX, Architecture, Delivery, and planned verification.

Active design exploration

Document Purpose
Calendar UI prototype Throwaway, simulated comparison of three calendar and Journal Day layout directions on prototype/calendar-ui-directions; no production behavior is implied.
Calendar UI prototype v2 Versioned Margin Companion revision of Archive Desk, Living Mosaic, and Monthly Almanac on prototype/calendar-ui-v2-margin-companion.
Calendar UI v2 design QA Selected-reference comparison, captured v2 image set, interaction checks, responsive checks, and the bounded prototype QA result.
Unified Calendar and Almanac prototype v3 Selected single direction combining Living Mosaic as the default Calendar with a collapsible Monthly Almanac reading view on prototype/calendar-ui-v3-unified.
Calendar UI v3 prototype guide Local run instructions, routes, screen inventory, responsive behavior, interactions, and prototype boundaries.
Calendar UI v3 design QA Side-by-side design comparison, desktop/mobile interaction checks, accessibility review, fixes, and bounded QA result.
Museum Margin Calendar prototype v4 Approved revision with an image-only default Calendar and source provenance revealed in a selected-day right margin on prototype/calendar-ui-v4-museum-margin.
Calendar UI v4 prototype guide Local run instructions, two-state URL model, image-only tile contract, responsive behavior, and prototype boundaries.
Calendar UI v4 design QA Approved-reference comparisons, primary interaction checks, responsive sheet evidence, and bounded QA result.
Private Settings and compact privacy prototype v5 Source-grounded Settings suite and a subtle Journal Day privacy entry point on prototype/calendar-ui-v5-settings.
Calendar UI v5 prototype guide Local routes, Settings screen inventory, responsive model, truthful simulated states, and prototype boundaries.
Calendar UI v5 design QA Same-input privacy-density comparison, Settings screen review, interaction checks, responsive evidence, and bounded QA result.
Prototype v5 PRD feature audit Product, design, and technical audit of all 78 PRD requirements, including missing/partial/placeholder coverage, current-run screenshots, and the recommended v6 completeness sequence.
Prototype completeness tracker QA-gated v6–v35 remediation program mapping every prototype-representable v5 audit gap to one stable version while keeping backend proof outside prototype claims.
Private Search prototype v6 First remediation slice: page-memory-only Search terms, legacy q removal, and an honest no-suggestions initial state on prototype/calendar-ui-v6-private-search.
Calendar UI v6 prototype guide Local run instructions, privacy behavior, deliberate Search limits, responsive intent, and evidence boundaries.
Calendar contract prototype v7 Second remediation slice: private-content-free month/year navigation, external Calendar state rings, progressive provenance, and cross-month keyboard behavior on prototype/calendar-ui-v7-calendar-contract.
Calendar UI v7 prototype guide Local routes, Calendar/chooser interaction contract, frozen v6 Search regression, responsive behavior, and evidence boundaries.
Calendar UI v7 design QA Independent chooser, Calendar-state, history/focus, responsive, motion, URL, console, and v6 Search-regression pass on the final v7 hashes.
Cross-month Almanac prototype v8 Third remediation slice: deterministic cross-month reading, one-month pagination, safe range state, Almanac index, jump, and canonical Journal Day return.
Calendar UI v8 prototype guide Local routes, Cross-month Almanac interaction contract, inherited regressions, and prototype evidence boundaries.
Cross-month Almanac v8 council Product, Design, and Project reconciliation for PVA-003.
Cross-month Almanac v8 independent QA Exact artifact fingerprints, full interaction/responsive regression matrix, resolved findings, Pass verdict, and evidence boundary.
First-use Readiness prototype v9 Fourth remediation slice: empty Calendar plus independent VoiceNotes, Telegram, AI, Backup, and always-blocked Recovery Ceremony readiness.
Calendar UI v9 prototype guide Local routes, truthful readiness fixtures, inherited regressions, and evidence boundaries.
First-use Readiness v9 council Product, Design, and Project reconciliation for PVA-004.
First-use Readiness v9 independent QA Exact artifact fingerprints, current-run interaction/responsive regression matrix, resolved findings, Pass verdict, and evidence boundary.
Resilient Application Shell prototype v10 Fifth remediation slice: coordinated loading, failure, interruption, unsaved-work, session, and guarded-retry states.
Calendar UI v10 prototype guide Local run instructions, shell-state contract, deliberate limits, and review artifacts.
Resilient Application Shell v10 council Approved Product, Design, and Project contract for PVA-005.
Resilient Application Shell v10 independent QA Exact six-file fingerprint, current-run shell-state and regression matrix, Pass verdict, and evidence boundary.

Discovery and research record

These documents preserve how the current planning baseline was reached. Later confirmed decisions take precedence over earlier proposals.

Document What it contains Interpretation
Initial Brief Original product request and inspiration links. Historical input; later decisions supersede conflicts.
Detailed Discovery Requirements The requirements interview record and decisions 1–65. Canonical detailed discovery decisions beneath Arun's direct corrections.
Product and Integration Research Research on inspiration products, VoiceNotes, Telegram, hosting, authentication, privacy, backup, and integrations. Evidence base; distinguishes documented facts, observations, proposals, and unknowns.
Proposed Shared Understanding Concise synthesis of the intended MVP. Awaiting Arun's explicit G1 confirmation.
AI Text Model Evaluation Candidate comparison, privacy/cost analysis, synthetic test protocol, hard gates, and production contract for text AI. Evaluation design only; no model is selected or qualified yet.
AI Artwork Model Evaluation Candidate comparison, blind visual evaluation, privacy/cost controls, hard gates, and artwork configuration contract. Evaluation design only; no model is selected or qualified yet.
Media Storage Evaluation Cost, privacy, operational, backup, and migration comparison for local disk, R2, B2, and Hetzner alternatives. Planning recommendation; provisioning and migration remain gated.
Worktree Provenance Repository, branch, base, worktree, and isolation provenance for discovery work. Historical Git provenance.

Domain language and repository entry points

Document What it contains
Domain Language Canonical terms such as Journal Day, Journal Date, Source Item, Daily Photo, Original Timestamp, Correction, and Derived Artifact.
Repository README Short project status, primary artifact links, and discovery entry points.
Publication Provenance Scope of the clean public snapshot, intentional metadata exclusions, and the boundary between publication and product deployment.
Security and Privacy Reporting Private vulnerability-reporting path and rules for sensitive content.
Contributing Synthetic-data, status-language, documentation, and frozen-prototype contribution rules.

Recommended reading paths

To approve the product understanding

  1. Proposed Shared Understanding
  2. Detailed Discovery Requirements, when a statement needs its full decision history
  3. Product Requirements Document, for the complete product contract

To design or review the experience

  1. Product Requirements Document
  2. Domain Language
  3. UX Specification
  4. Requirements Traceability

To prepare implementation after authorization

  1. Proposed Shared Understanding and the recorded G1 decision
  2. Product Requirements Document
  3. Implementation Plan
  4. Project Tracker
  5. Requirements Traceability

To understand evidence and governance

  1. Product Council Charter
  2. Council Review
  3. Project Tracker
  4. Requirements Traceability

Source precedence

When documents disagree, use this order:

  1. Arun's direct decisions and corrections.
  2. The Proposed Shared Understanding after Arun explicitly confirms it.
  3. The Detailed Discovery Requirements.
  4. The Domain Language.
  5. Discovery research and evaluation evidence.
  6. The council-created PRD, UX specification, implementation plan, tracker, and traceability matrix.

Do not silently resolve a remaining conflict by choosing the more convenient document. Record it through the Project Tracker change-control process.

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