Table of Contents

TrizAgenda — Week 01 (Mon 27 Jul – Fri 31 Jul 2026)

✅ Shipped this week
🚧 In progress
⛔ Blockers & decisions needed
📅 Next week
Risks

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

TrizAgenda — Week 01 (Mon 27 Jul – Fri 31 Jul 2026)

Draft pre-filled at kickoff — the PM completes the REPLACE parts on Friday 31 Jul, then copies this page as Status-Week-02 for next week. Naming: Status-Week-NN.

Milestone: M1 — Foundations & Auth ▸ Progress: REPLACE/20 issues (7 API + 6 web + 6 mobile in M1 after the kickoff triage — adjust to actual counts)

✅ Shipped this week

Project setup: 3 repos + trizagenda-team live, backlog pasted (100 issues), starters pushed, agreements ratified at kickoff (see Decisions)
API: REPLACE — e.g. "API-01 onboarding + API-02 code tour merged; error envelope work started"
Web: REPLACE — e.g. "WEB-01/02 done; login against real API verified; app shell started"
Mobile: REPLACE — e.g. "MOB-01 emulator run green (starter compiled with N trivial fixes); code tour done"

🚧 In progress

API: REPLACE (issue IDs + on track / at risk because …)
Web: REPLACE
Mobile: REPLACE

⛔ Blockers & decisions needed

REPLACE (or "none")

📅 Next week

All three apps authenticating against the real API (M1 exit criterion #1)
Every dev has ≥2 merged PRs (M1 exit criterion #2)
REPLACE — the 3–5 things that will be demoed next Friday

Risks

Week 1 watch item: setup friction (first docker compose up, first emulator run) — 30-minute rule actively enforced. REPLACE if anything moved in the register, else "no other change".