Skip to content

Documentation Index

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

Canonical source: docs/INDEX.md · Snapshot commit: 6b8b70b72148

Life in Days — document index

Updated: 2026-08-16

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

Current status: The bounded P0/R0 Gold Goal passed its separately reviewed three-file bootstrap through PR #69 and the strict same-worktree clean exact-main gate at 2dc4d05cdeca8cb9aeacf393076f6c6f946ff62b. Stage 0 is the one-time local/public control-plane and factual repair under existing issue #3. Its current acceptance/publication state derives from the exact-candidate dossier, append-only successor-review registry, and durable PR #70 evidence rather than this static index. No Stage 0 source text authorizes R0 implementation, private-system access, authentic-media processing, deployment, restore, rollback, acceptance, release, or production. Current execution authority is limited to R0 under that active bounded Goal. All R1-R10 tasks and artifacts are frozen and out of scope; broader execution requires a new direct Product Owner activation. Current structured control truth is 58 Incomplete; 45 Hold + 13 Historical non-authorizing; 0 Ready; 0 execution-allowed. Artifact state remains 342 Draft plus six PC-001 In review. The R0 shared-host spike retains its historical In-progress roadmap status but is not execution-authorized; deployment is Unknown — private read authority pending.

Earlier P0 readiness-control provenance remains available through PR #66, PR #67, and their exact-candidate records. As dated publication provenance, Wiki master commit 1927a91529b6df7918a353876fdf9d64a0fbbe78 represented repository snapshot e8130729d005fe6fd8731860963ab5ffa5ed1682 as 456 Wiki files with 450/450 Markdown sources mapped and zero preserved live-only pages. Those counts and commits are not asserted as current. The live Page Audit is the stable source for the currently published Wiki source SHA, dynamically derived N/N coverage, generated-page fingerprints, and preserved-page inventory; this source index intentionally embeds no current Page Audit or Wiki hash, avoiding a recursive source/Wiki fingerprint loop. The independently checked r14 workbook remains dated evidence at SHA-256 d8b21f955366a516bca0b0961b941b3f76c84b5aa2e9406e3740005ca7547994 for 7 sheets, 58 tasks, 78 requirements, 2,009 formulas with zero detected errors, and exact R10 blanks. It is planning-surface evidence, not execution or deployment evidence.

Phase 1 delivery baseline

Document Purpose Current role
AI Agent Operating Contract Mandatory same-change workflow for keeping the manifest, GitHub issues, Project roadmap views, issue map, Markdown plan, Excel workbook, and running log synchronized. Repository-wide instruction for every AI agent; evidence and authorization gates remain controlling.
AI Agent Resource Index — 2026-08-14 15:10:39 IST Timestamped AI boot sequence, authority model, GitHub links, roadmap fields and views, milestone and 58-item task navigation, resource map, tooling, cautions, hashes, and complete tracked-file inventory. Orientation snapshot only; current source documents and live GitHub evidence remain authoritative.
Codex Goal Prompt — P0 Requirements to Private Production Historical broad autonomous execution contract covering the 71 active P0 requirements and R0-R9 delivery. Directly activated on 2026-08-14, but superseded for the next bounded run by the P0/R0-only Gold Goal below. Read it only for inherited control history; do not use it to start R1-R10.
P0 Codex Gold Goal — Complete P0 and R0 Only Active bounded Goal for exactly the eight manifest tasks in milestones P0 and R0. It includes the completed three-file Activation Bootstrap, one-time Stage 0 repair, then the synthetic-only R0 foundation with evidence before stopping without R1-R10 work. Directly activated after PR #69 and the strict clean exact-main gate. Stage 0 is governed by its exact candidate, successor registry, and PR closure evidence; ordinary R0 execution and every private/deployment action remain subject to their named gates and evidence.
P0 Execution Context Digest Historical 2026-08-14 19:51 IST pre-publication repository, Git, GitHub/Project/Wiki, architecture, requirement/task, unknown, and next-work snapshot. Provenance only; use the P0 control review and GitHub Project sync runbook for current publication/parity state.
P0 Execution Authorization Preserves the historical authority record, private deployment boundary, and human-only acts; P0-ED-016 supplies the current R0-only scope interpretation. Current only within the active bounded Goal: R0 is in scope, R1-R10 is frozen, and broader execution needs new direct Product Owner activation.
P0 Execution Council Charter Five-seat membership, RACI, vetoes, release cadence, evidence, privacy, and naming controls. Current execution governance.
P0 Execution Decisions Dated decisions for authority, naming, R4, Health, prototype queue, containment, Wiki, and next work. Append-only execution change control.
P0 Task Definition of Ready Requires task-bound Product, Architecture, Design, QA, Delivery, and Council artifacts before substantive work. Current start gate for all 58 canonical issues.
P0/R0 Stage 0 Candidate Review Bounded review dossier for the one-time local/public control-plane repair, with its state contract, test plan, rollback plan, and delivery checklist. Candidate-preparation evidence only until an exact revision passes independent five-seat review, normal merge, and the separate add-only successor-review publication; it grants no R0 action or runtime authority.
P0/R0 Stage Approval Registry Machine-readable preparation-review and stage-approval envelopes for the five substantive R0 tasks. Inert in Stage 0: both collections are empty, the production module allowlist is empty, and no execution permission exists.
R1-R10 Activation Freeze Canonical activation snapshot for all 50 prohibited R1-R10 tasks, 300 task artifacts, and sanitized issue/Project projections. Permanent fail-closed comparison source for Stage 0, generation, sync, transition, rollback, and terminal reconciliation; it is not a mutable exception list.
P0 Task Artifact Register Machine-readable artifact paths, hashes, scenario IDs, owner actions, readiness, execution scope, and council disposition. Canonical task-dossier readiness projection: 58 Incomplete; 45 Hold + 13 Historical non-authorizing; 0 Ready; 0 execution-allowed.
P0 Task Readiness State Editable task-level evidence/coverage/council inputs consumed by the dossier generator. Change-controlled input; it cannot approve a task or grant execution permission by itself.
P0 Execution Reviewer Registry Stable public-safe reviewer IDs, one role per identity, and active state. Identity source for artifact, Council, QA-independence, authority, and action verification.
P0 Execution Approval Registry Separate machine-readable taskApprovals and audit-only controlReviews, with exact candidates, five-seat attestations, publication history, and bounded claims. controlReviews.PC-001 records the published readiness-control review with executionAllowed=false; taskApprovals remains empty, so no delivery task is authorized.
P0 Owner Action State Structured public-safe action requirements and candidate-bound pass evidence aligned to the human ledger. All named human gates remain Pending or Not triggered; no secrets or private evidence are stored.
P0 Task Work Items Six P0-prefixed artifacts for each stable task ID. Task-specific council inputs; 342 are Draft and the six PC-001 planning artifacts are In review; generation or planning approval is not execution authorization.
PC-001 Readiness-hardening Planning Review Exact six-artifact hashes, canonical dossier digest, five-seat attestations, veto repair, verified planning state, and code-start boundary. Gate A planning authority only; the separate exact implementation review is published under controlReviews.PC-001, while all delivery-task approvals remain absent.
P0 Owner Action Ledger Public-safe inventory of all foreseeable non-delegable R0–R10 actions and opaque evidence references. Current consolidated human-dependency source.
Product Council Decision Record Reconciles Product, UX, Architecture, and Project planning decisions, including P0/R0–R10, evidence gates, and the shared-host baseline. Current planning baseline; execution authority is separately limited to R0 by the active bounded Goal.
Phase 1 Release Plan Detailed 58-task schedule with milestones, dates, descriptions, requirements, task readiness, execution authorization, parent PRD/PID links, design inputs, ownership, and status rules. Project Manager-owned delivery plan.
Phase 1 Roadmap Manifest Machine-readable source for the Markdown plan, workbook, repository issues, and live GitHub Project, embedding every task dossier. Canonical task/status/date/link/readiness projection.
GitHub Project Sync Runbook Dry-run-first repository issue and Project V2 synchronization contract, schema, commands, recovery, and UI-only completion steps. Operational publication guide; live verification is recorded separately from planning claims.
Phase 1 Excel Release Plan Seven-sheet review workbook with summary charts, release plan, 58 tasks, weekly timeline, requirement map, and risks/gates. Review artifact generated from the manifest.
Product Manager Review Product framing, release decomposition, 78-requirement assignment, outcomes, risks, and task seed. Specialist council recommendation reconciled by the decision record.
UX Design Review v5 inspection, screenshots, design gaps, accessibility/privacy gates, and design traceability for all 58 tasks. Specialist design evidence; prototype intent does not prove implementation.
Project Manager Review Critical path, lane policy, Definition of Ready/Done, RAID, cadence, and GitHub operating model. Delivery-control baseline.
Phase 1 Implementation Plan Detailed architecture, domain, security, deployment, recovery, test, rollback, and work-package implementation guidance. Technical planning authority; no deployed behavior implied.
Hetzner Shared-host Deployment Spike First-party research, coexistence topology, SQLCipher/SQLite proof gates, PostgreSQL fallback, and live preflight plan. Research/design complete; live capacity and coexistence proof remains outstanding.
Wayfinder Phase 1 Adoption Report Deep assessment of the installed Wayfinder skill, Phase 1 fit, GitHub capabilities, source-of-truth boundaries, release-by-release use, risks, and a bounded R0 pilot. Conditional recommendation only; no Wayfinder map, ticket, label, relationship, or Project change is authorized or implied.
GitHub Projects Roadmap Research Deep current-capability research on Roadmap layouts, views, fields, automation, APIs, limits, and GitHub's public roadmap. Historical research snapshot that informed the current Project model.
GitHub Roadmap Design Spike Reversible eight-item pilot design, field taxonomy, view recipes, evidence policy, and operating rules. Historical pilot design; the 58-task manifest now governs execution.
Shared-host Runbook Sanitized commands, stop conditions, deployment, backup/restore, observation, and rollback sequence. Execution guide; not evidence that commands have run.
Release PRDs and conditional PID R0–R9 release-specific requirements plus date-free R10 transition definition. Drafted planning artifacts only. Current council delegation reaches eligible R0 work under the bounded Goal; R1-R10 remains frozen until a new direct Product Owner activation.
Life Reflection GitHub Project Status and date visualization of all manifest work packages. Live control surface; documents and issue evidence remain authoritative.

Start here

Document Purpose Current role
Proposed Shared Understanding Historical concise statement of the product promise, MVP boundary, capture model, AI/privacy rules, recovery direction, and deferrals. Discovery provenance; the governing PRD and current Phase 1 decision record control the release plan.
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 Historical G0–G9 gates, 12 milestones, 23 epics, 211 detailed tasks, dependencies, evidence, risks, decisions, and backlog. Detailed historical task inventory; Phase 1 execution/status is governed by the 58-task manifest.
Implementation Plan Earlier proposed architecture, domain model, integrations, jobs, security, storage, backup, testing, deployment, rollback, and technical gates. Preserved planning baseline; the Phase 1 implementation plan is current for delivery.
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.
Phase 1 Product Council Charter Current council membership, decision rights, evidence boundary, release gates, and four-lane roadmap contract.
Phase 1 Council Decision Record Final reconciliation of the four specialist seats for P0 and R0–R10.
Product Manager Review Product outcome, decomposition, requirement mapping, risks, and 58-task seed.
UX Design Review v5 evidence, design gaps, screenshots, veto gates, and 58-task design traceability.
Project Manager Review Critical path, status policy, readiness/completion rules, RAID, and GitHub operating model.
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.
Independent QA Lead Charter QA independence, evidence bundle, test matrices, severity, veto, AI-blind, and release-verdict contract.
P0 Execution-control Review Five-seat readiness/acceptance findings, remediation checklist, publication evidence, package-level Published disposition, and the continuing per-task Hold boundary.
PC-001 Readiness-hardening Planning Review Exact candidate/digest, five-seat planning approvals, resolved Design vetoes, and the merge-before-code boundary for PC-001.

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 Phase 1 Implementation Plan Current technical shape, persistence, integrations, security/privacy enforcement, AI orchestration, shared-host deployment, storage, operations, tests, and rollback.
Delivery Phase 1 Release Plan P0/R0–R10 milestones, 58 work packages, dates, owners, dependencies, statuses, evidence requirements, and GitHub contract.
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. Historical discovery artifact; not the current Phase 1 execution blocker.
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
AI Agent Operating Contract Mandatory living-roadmap, GitHub synchronization, Excel regeneration, validation, safety, and handoff workflow for AI agents.
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 Phase 1 implementation after the named gates

  1. Product Requirements Document
  2. P0 Execution Authorization and Owner Action Ledger
  3. Phase 1 Council Decision Record
  4. The applicable release PRD/PID
  5. UX Design Review and release-specific design evidence
  6. Phase 1 Implementation Plan
  7. Phase 1 Release Plan and Roadmap Manifest
  8. Hetzner Shared-host Deployment Spike and Runbook for R0

To understand evidence and governance

  1. Phase 1 Product Council Charter
  2. P0 Execution Council Charter
  3. P0 Execution Decisions
  4. Phase 1 Council Decision Record
  5. Project Manager Review
  6. Phase 1 Release Plan
  7. Requirements Traceability

Source precedence

When documents disagree, use this order:

  1. Arun's direct decisions and corrections.
  2. The Product Requirements Document for product behavior and stable requirement IDs.
  3. The UX Specification for interaction behavior, subject to direct corrections and the PRD.
  4. The Phase 1 Council Decision Record for release decomposition and planning decisions that do not alter the PRD.
  5. The applicable release PRD/PID, Phase 1 Implementation Plan, and Phase 1 Roadmap Manifest within their disciplines.
  6. The Detailed Discovery Requirements, Domain Language, discovery research, and historical G0/G1 council artifacts as provenance.

Do not silently resolve a remaining conflict by choosing the more convenient document. Record it through the Phase 1 Council Decision Record and affected manifest task.

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