-
Notifications
You must be signed in to change notification settings - Fork 0
Documentation Index
Canonical source:
docs/INDEX.md· Snapshot commit:b9f2813f22e4
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.
| 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. |
| 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. |
| 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. |
| 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. |
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. |
| 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. |
- Proposed Shared Understanding
- Detailed Discovery Requirements, when a statement needs its full decision history
- Product Requirements Document, for the complete product contract
- Proposed Shared Understanding and the recorded G1 decision
- Product Requirements Document
- Implementation Plan
- Project Tracker
- Requirements Traceability
When documents disagree, use this order:
- Arun's direct decisions and corrections.
- The Proposed Shared Understanding after Arun explicitly confirms it.
- The Detailed Discovery Requirements.
- The Domain Language.
- Discovery research and evaluation evidence.
- 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.
Generated from arunpr614/Life-Reflection@6b8b70b72148 · Canonical content lives in Git · Fictional prototype data only
- Life in Days — Hetzner shared-host runbook
- Life in Days — Phase1 implementation plan
- PID R10 — Conditional Object-Store Transition
- PRD R0 — Shared-Host Private Foundation
- PRD R1 — Manual Journal Archive
- PRD R2 — Telegram Photo Capture
- PRD R3 — Retrieval and Date Integrity
- PRD R4 — Source History and Lifecycle Safety
- PRD R5 — Prospective VoiceNotes Sync
- PRD R6 — Generated Text Reflection
- PRD R7 — Generated Artwork
- PRD R8 — Operational Scale and Resilience
- PRD R9 — Private Launch Acceptance and Stabilization
- Life in Days release documents
- Life in Days Phase 1 — AI agent resource index
- Codex Goal prompt — Phase 1 P0 requirements to private production
- P0 Codex Gold Goal prompt — complete P0 and R0 only
- Phase 1 GitHub Project V2 sync
- Life in Days — Phase 1 Release Plan
- Life in Days — detailed implementation plan
- Life in Days Global PRD
- Life in Days — project tracker
- Life in Days — prototype completeness tracker
- Life in Days — requirements traceability
- Life in Days — UX specification
- Life in Days — AI Artwork Model Evaluation
- Life in Days — AI Text Model Evaluation
- Initial product brief
- Life in Days: Private Media Storage Evaluation
- Requirements under discovery
- Product and integration research
- Project Git provenance
- Life in Days — proposed shared understanding
- Life in Days — Product Council planning-baseline review
- Life in Days Phase 1 — Independent QA Lead charter
- Agent charter — Project Manager
- Agent charter — Senior Product Manager
- Agent charter — Technical Architect
- Agent charter — UI/UX Design Lead
- Life in Days Phase 1 — P0 Owner Action Ledger
- Life in Days Phase 1 — P0 execution context digest
- Life in Days Phase 1 — P0 execution authorization addendum
- Life in Days Phase 1 — P0 execution council charter
- Life in Days Phase 1 — P0 execution decision ledger
- Life in Days Phase 1 — P0 task Definition of Ready
- Life in Days Phase 1 — P0 execution-control review
- P0/R0 Stage 0 control-repair candidate review dossier
- P0/R0 Stage 0 delivery checklist
- P0/R0 Stage 0 rollback and recovery plan
- P0/R0 Stage 0 state contract
- P0/R0 Stage 0 test plan
- PC-001 readiness-control hardening — planning review
- Life in Days — Phase 1 Product Council Decision Record
- Life in Days Phase 1 — source baseline
- Life in Days Phase 1 — Product Council charter
- Life in Days — Product Manager Council Review
- Life in Days — Project Manager Council Review
- Life in Days — Product Council UX Design Review
- Life in Days Product Council
- Life in Days — calendar UI prototype
- Life in Days — calendar UI prototype v2
- Life in Days — unified Calendar and Almanac prototype v3
- Life in Days — Museum Margin Calendar prototype v4
- Life in Days — private Settings and compact privacy prototype v5
- Life in Days — private Search prototype v6
- Life in Days — Calendar contract prototype v7
- Life in Days — Cross-month Almanac prototype v8
- Life in Days — First-use Readiness prototype v9
- Life in Days — Resilient Application Shell prototype v10
- Life in Days calendar UI prototype
- Life in Days calendar UI prototype v2
- Life in Days unified calendar prototype v3
- Life in Days Museum Margin prototype v4
- Life in Days Settings prototype v5
- Life in Days — private Search prototype v6
- Life in Days prototype v7 — Calendar contract completion
- Life in Days prototype v8 — Cross-month Almanac
- Life in Days prototype v9 — First-use Readiness
- Life in Days prototype v10 — Resilient Application Shell
- v6 Product Council contract — Private Search State
- Life in Days prototype v7 — Product Council contract
- Life in Days prototype v8 — Product Council contract
- Life in Days prototype v9 — Product Council contract
- Life in Days prototype v10 — Product Council contract
- Life in Days v2 — design QA
- Life in Days unified prototype v3 — design QA
- Life in Days v4 — design QA
- Life in Days v5 design QA
- Life in Days v5 design QA
- Life in Days v6 — independent design and interaction QA
- Life in Days v7 — independent design and interaction QA
- Life in Days prototype v8 — independent design QA
- Life in Days prototype v9 — independent design QA
- Life in Days prototype v10 — independent design QA
- Life in Days prototype v5 — PRD feature audit
- AI agent operating contract — keep Phase 1 alive
- Contributing to Life in Days
- GitHub Projects Roadmap — current capability research
- Life in Days — Hetzner shared-host deployment spike
- Wayfinder for Life in Days Phase 1 — adoption and GitHub integration report
- Life in Days — GitHub Projects Roadmap design spike
- ARCH-R0-001 — Product Council task readiness
- ARCH-R0-001 — task delivery checklist
- ARCH-R0-001 — task design specification
- ARCH-R0-001 — task product requirements
- ARCH-R0-001 — task QA plan
- ARCH-R0-001 — task technical plan
- ARCH-R1-001 — Product Council task readiness
- ARCH-R1-001 — task delivery checklist
- ARCH-R1-001 — task design specification
- ARCH-R1-001 — task product requirements
- ARCH-R1-001 — task QA plan
- ARCH-R1-001 — task technical plan
- ARCH-R2-001 — Product Council task readiness
- ARCH-R2-001 — task delivery checklist
- ARCH-R2-001 — task design specification
- ARCH-R2-001 — task product requirements
- ARCH-R2-001 — task QA plan
- ARCH-R2-001 — task technical plan
- ARCH-R3-001 — Product Council task readiness
- ARCH-R3-001 — task delivery checklist
- ARCH-R3-001 — task design specification
- ARCH-R3-001 — task product requirements
- ARCH-R3-001 — task QA plan
- ARCH-R3-001 — task technical plan
- ARCH-R4-001 — Product Council task readiness
- ARCH-R4-001 — task delivery checklist
- ARCH-R4-001 — task design specification
- ARCH-R4-001 — task product requirements
- ARCH-R4-001 — task QA plan
- ARCH-R4-001 — task technical plan
- ARCH-R5-001 — Product Council task readiness
- ARCH-R5-001 — task delivery checklist
- ARCH-R5-001 — task design specification
- ARCH-R5-001 — task product requirements
- ARCH-R5-001 — task QA plan
- ARCH-R5-001 — task technical plan
- ARCH-R6-001 — Product Council task readiness
- ARCH-R6-001 — task delivery checklist
- ARCH-R6-001 — task design specification
- ARCH-R6-001 — task product requirements
- ARCH-R6-001 — task QA plan
- ARCH-R6-001 — task technical plan
- ARCH-R7-001 — Product Council task readiness
- ARCH-R7-001 — task delivery checklist
- ARCH-R7-001 — task design specification
- ARCH-R7-001 — task product requirements
- ARCH-R7-001 — task QA plan
- ARCH-R7-001 — task technical plan
- ARCH-R8-001 — Product Council task readiness
- ARCH-R8-001 — task delivery checklist
- ARCH-R8-001 — task design specification
- ARCH-R8-001 — task product requirements
- ARCH-R8-001 — task QA plan
- ARCH-R8-001 — task technical plan
- ARCH-R10-001 — Product Council task readiness
- ARCH-R10-001 — task delivery checklist
- ARCH-R10-001 — task design specification
- ARCH-R10-001 — task product requirements
- ARCH-R10-001 — task QA plan
- ARCH-R10-001 — task technical plan
- AUD-001 — Product Council task readiness
- AUD-001 — task delivery checklist
- AUD-001 — task design specification
- AUD-001 — task product requirements
- AUD-001 — task QA plan
- AUD-001 — task technical plan
- ENG-R0-001 — Product Council task readiness
- ENG-R0-001 — task delivery checklist
- ENG-R0-001 — task design specification
- ENG-R0-001 — task product requirements
- ENG-R0-001 — task QA plan
- ENG-R0-001 — task technical plan
- ENG-R1-001 — Product Council task readiness
- ENG-R1-001 — task delivery checklist
- ENG-R1-001 — task design specification
- ENG-R1-001 — task product requirements
- ENG-R1-001 — task QA plan
- ENG-R1-001 — task technical plan
- ENG-R2-001 — Product Council task readiness
- ENG-R2-001 — task delivery checklist
- ENG-R2-001 — task design specification
- ENG-R2-001 — task product requirements
- ENG-R2-001 — task QA plan
- ENG-R2-001 — task technical plan
- ENG-R2-002 — Product Council task readiness
- ENG-R2-002 — task delivery checklist
- ENG-R2-002 — task design specification
- ENG-R2-002 — task product requirements
- ENG-R2-002 — task QA plan
- ENG-R2-002 — task technical plan
- ENG-R3-001 — Product Council task readiness
- ENG-R3-001 — task delivery checklist
- ENG-R3-001 — task design specification
- ENG-R3-001 — task product requirements
- ENG-R3-001 — task QA plan
- ENG-R3-001 — task technical plan
- ENG-R4-001 — Product Council task readiness
- ENG-R4-001 — task delivery checklist
- ENG-R4-001 — task design specification
- ENG-R4-001 — task product requirements
- ENG-R4-001 — task QA plan
- ENG-R4-001 — task technical plan
- ENG-R4-002 — Product Council task readiness
- ENG-R4-002 — task delivery checklist
- ENG-R4-002 — task design specification
- ENG-R4-002 — task product requirements
- ENG-R4-002 — task QA plan
- ENG-R4-002 — task technical plan
- ENG-R5-001 — Product Council task readiness
- ENG-R5-001 — task delivery checklist
- ENG-R5-001 — task design specification
- ENG-R5-001 — task product requirements
- ENG-R5-001 — task QA plan
- ENG-R5-001 — task technical plan
- ENG-R6-001 — Product Council task readiness
- ENG-R6-001 — task delivery checklist
- ENG-R6-001 — task design specification
- ENG-R6-001 — task product requirements
- ENG-R6-001 — task QA plan
- ENG-R6-001 — task technical plan
- ENG-R7-001 — Product Council task readiness
- ENG-R7-001 — task delivery checklist
- ENG-R7-001 — task design specification
- ENG-R7-001 — task product requirements
- ENG-R7-001 — task QA plan
- ENG-R7-001 — task technical plan
- EVAL-R6-001 — Product Council task readiness
- EVAL-R6-001 — task delivery checklist
- EVAL-R6-001 — task design specification
- EVAL-R6-001 — task product requirements
- EVAL-R6-001 — task QA plan
- EVAL-R6-001 — task technical plan
- EVAL-R7-001 — Product Council task readiness
- EVAL-R7-001 — task delivery checklist
- EVAL-R7-001 — task design specification
- EVAL-R7-001 — task product requirements
- EVAL-R7-001 — task QA plan
- EVAL-R7-001 — task technical plan
- PC-001 — readiness-control hardening Council record
- PC-001 — readiness-control hardening delivery plan
- PC-001 — readiness-control evidence design specification
- PC-001 — readiness-control hardening product requirements
- PC-001 — readiness-control hardening QA plan
- PC-001 — readiness-control hardening technical plan
- PID-R10-001 — Product Council task readiness
- PID-R10-001 — task delivery checklist
- PID-R10-001 — task design specification
- PID-R10-001 — task product requirements
- PID-R10-001 — task QA plan
- PID-R10-001 — task technical plan
- PRD-R0-001 — Product Council task readiness
- PRD-R0-001 — task delivery checklist
- PRD-R0-001 — task design specification
- PRD-R0-001 — task product requirements
- PRD-R0-001 — task QA plan
- PRD-R0-001 — task technical plan
- PRD-R1-001 — Product Council task readiness
- PRD-R1-001 — task delivery checklist
- PRD-R1-001 — task design specification
- PRD-R1-001 — task product requirements
- PRD-R1-001 — task QA plan
- PRD-R1-001 — task technical plan
- PRD-R2-001 — Product Council task readiness
- PRD-R2-001 — task delivery checklist
- PRD-R2-001 — task design specification
- PRD-R2-001 — task product requirements
- PRD-R2-001 — task QA plan
- PRD-R2-001 — task technical plan
- PRD-R3-001 — Product Council task readiness
- PRD-R3-001 — task delivery checklist
- PRD-R3-001 — task design specification
- PRD-R3-001 — task product requirements
- PRD-R3-001 — task QA plan
- PRD-R3-001 — task technical plan
- PRD-R4-001 — Product Council task readiness
- PRD-R4-001 — task delivery checklist
- PRD-R4-001 — task design specification
- PRD-R4-001 — task product requirements
- PRD-R4-001 — task QA plan
- PRD-R4-001 — task technical plan
- PRD-R5-001 — Product Council task readiness
- PRD-R5-001 — task delivery checklist
- PRD-R5-001 — task design specification
- PRD-R5-001 — task product requirements
- PRD-R5-001 — task QA plan
- PRD-R5-001 — task technical plan
- PRD-R6-001 — Product Council task readiness
- PRD-R6-001 — task delivery checklist
- PRD-R6-001 — task design specification
- PRD-R6-001 — task product requirements
- PRD-R6-001 — task QA plan
- PRD-R6-001 — task technical plan
- PRD-R7-001 — Product Council task readiness
- PRD-R7-001 — task delivery checklist
- PRD-R7-001 — task design specification
- PRD-R7-001 — task product requirements
- PRD-R7-001 — task QA plan
- PRD-R7-001 — task technical plan
- PRD-R8-001 — Product Council task readiness
- PRD-R8-001 — task delivery checklist
- PRD-R8-001 — task design specification
- PRD-R8-001 — task product requirements
- PRD-R8-001 — task QA plan
- PRD-R8-001 — task technical plan
- PRD-R9-001 — Product Council task readiness
- PRD-R9-001 — task delivery checklist
- PRD-R9-001 — task design specification
- PRD-R9-001 — task product requirements
- PRD-R9-001 — task QA plan
- PRD-R9-001 — task technical plan
- QA-R8-001 — Product Council task readiness
- QA-R8-001 — task delivery checklist
- QA-R8-001 — task design specification
- QA-R8-001 — task product requirements
- QA-R8-001 — task QA plan
- QA-R8-001 — task technical plan
- QA-R9-001 — Product Council task readiness
- QA-R9-001 — task delivery checklist
- QA-R9-001 — task design specification
- QA-R9-001 — task product requirements
- QA-R9-001 — task QA plan
- QA-R9-001 — task technical plan
- REL-R0-001 — Product Council task readiness
- REL-R0-001 — task delivery checklist
- REL-R0-001 — task design specification
- REL-R0-001 — task product requirements
- REL-R0-001 — task QA plan
- REL-R0-001 — task technical plan
- REL-R1-001 — Product Council task readiness
- REL-R1-001 — task delivery checklist
- REL-R1-001 — task design specification
- REL-R1-001 — task product requirements
- REL-R1-001 — task QA plan
- REL-R1-001 — task technical plan
- REL-R2-001 — Product Council task readiness
- REL-R2-001 — task delivery checklist
- REL-R2-001 — task design specification
- REL-R2-001 — task product requirements
- REL-R2-001 — task QA plan
- REL-R2-001 — task technical plan
- REL-R3-001 — Product Council task readiness
- REL-R3-001 — task delivery checklist
- REL-R3-001 — task design specification
- REL-R3-001 — task product requirements
- REL-R3-001 — task QA plan
- REL-R3-001 — task technical plan
- REL-R4-001 — Product Council task readiness
- REL-R4-001 — task delivery checklist
- REL-R4-001 — task design specification
- REL-R4-001 — task product requirements
- REL-R4-001 — task QA plan
- REL-R4-001 — task technical plan
- REL-R5-001 — Product Council task readiness
- REL-R5-001 — task delivery checklist
- REL-R5-001 — task design specification
- REL-R5-001 — task product requirements
- REL-R5-001 — task QA plan
- REL-R5-001 — task technical plan
- REL-R6-001 — Product Council task readiness
- REL-R6-001 — task delivery checklist
- REL-R6-001 — task design specification
- REL-R6-001 — task product requirements
- REL-R6-001 — task QA plan
- REL-R6-001 — task technical plan
- REL-R7-001 — Product Council task readiness
- REL-R7-001 — task delivery checklist
- REL-R7-001 — task design specification
- REL-R7-001 — task product requirements
- REL-R7-001 — task QA plan
- REL-R7-001 — task technical plan
- REL-R8-001 — Product Council task readiness
- REL-R8-001 — task delivery checklist
- REL-R8-001 — task design specification
- REL-R8-001 — task product requirements
- REL-R8-001 — task QA plan
- REL-R8-001 — task technical plan
- REL-R9-001 — Product Council task readiness
- REL-R9-001 — task delivery checklist
- REL-R9-001 — task design specification
- REL-R9-001 — task product requirements
- REL-R9-001 — task QA plan
- REL-R9-001 — task technical plan
- REL-R10-001 — Product Council task readiness
- REL-R10-001 — task delivery checklist
- REL-R10-001 — task design specification
- REL-R10-001 — task product requirements
- REL-R10-001 — task QA plan
- REL-R10-001 — task technical plan
- SPK-R0-001 — Product Council task readiness
- SPK-R0-001 — task delivery checklist
- SPK-R0-001 — task design specification
- SPK-R0-001 — task product requirements
- SPK-R0-001 — task QA plan
- SPK-R0-001 — task technical plan
- SPK-R5-001 — Product Council task readiness
- SPK-R5-001 — task delivery checklist
- SPK-R5-001 — task design specification
- SPK-R5-001 — task product requirements
- SPK-R5-001 — task QA plan
- SPK-R5-001 — task technical plan
- UX-R0-001 — Product Council task readiness
- UX-R0-001 — task delivery checklist
- UX-R0-001 — task design specification
- UX-R0-001 — task product requirements
- UX-R0-001 — task QA plan
- UX-R0-001 — task technical plan
- UX-R1-001 — Product Council task readiness
- UX-R1-001 — task delivery checklist
- UX-R1-001 — task design specification
- UX-R1-001 — task product requirements
- UX-R1-001 — task QA plan
- UX-R1-001 — task technical plan
- UX-R2-001 — Product Council task readiness
- UX-R2-001 — task delivery checklist
- UX-R2-001 — task design specification
- UX-R2-001 — task product requirements
- UX-R2-001 — task QA plan
- UX-R2-001 — task technical plan
- UX-R3-001 — Product Council task readiness
- UX-R3-001 — task delivery checklist
- UX-R3-001 — task design specification
- UX-R3-001 — task product requirements
- UX-R3-001 — task QA plan
- UX-R3-001 — task technical plan
- UX-R4-001 — Product Council task readiness
- UX-R4-001 — task delivery checklist
- UX-R4-001 — task design specification
- UX-R4-001 — task product requirements
- UX-R4-001 — task QA plan
- UX-R4-001 — task technical plan
- UX-R5-001 — Product Council task readiness
- UX-R5-001 — task delivery checklist
- UX-R5-001 — task design specification
- UX-R5-001 — task product requirements
- UX-R5-001 — task QA plan
- UX-R5-001 — task technical plan
- UX-R6-001 — Product Council task readiness
- UX-R6-001 — task delivery checklist
- UX-R6-001 — task design specification
- UX-R6-001 — task product requirements
- UX-R6-001 — task QA plan
- UX-R6-001 — task technical plan
- UX-R7-001 — Product Council task readiness
- UX-R7-001 — task delivery checklist
- UX-R7-001 — task design specification
- UX-R7-001 — task product requirements
- UX-R7-001 — task QA plan
- UX-R7-001 — task technical plan
- Life in Days — document index
- Life in Days
- Life in Days - Running Log
- Publication provenance
- Pull-Request-Template
- Life in Days
- Security and privacy reporting