Product review #18

[asim]

Continuous product oversight against the North Star in internal/docs/THESIS.md. Output: a re-ranked internal/docs/PRIORITIES.md (only if it changed) plus an assessment.

[asim]

@codex Act as the head of product for Mu — the everyday agent. Read CLAUDE.md and internal/docs/THESIS.md (the North Star) first, and re-derive alignment from the canon it names (README.md, docs/VISION.md, docs/PRINCIPLES.md, and the LIVE product at micro.mu — actually exercise the ask → answer loop). The bias of this phase is product-market fit through REFINEMENT, not new surface area: make what already exists work seamlessly. Each run: (1) ASSESS — go through the core loop as a real person would (guest and signed-in, web and chat clients where observable): does asking Mu something return a correct, well-formatted, fast answer? Do the home cards and agent-callable services work end to end and degrade gracefully when a provider is down? Is the first-run experience clear without an account? (2) TRACK STATE — scan recently merged PRs and open codex PRs/issues so the queue reflects reality (drop done items, don't re-queue in-flight work). (3) MAINTAIN THE QUEUE in internal/docs/PRIORITIES.md — a SINGLE ordered list, highest-value first, each item linking a scoped, CI-verifiable issue (#N); roadmap phase (Now → Next → Later in THESIS.md) is the primary ordering, with rough edges and bugs interleaved by value, refinement ranked above additions. For any prioritized gap with no issue yet, file one: gh issue create --label codex --title "<scoped task>" --body "<goal, scope, acceptance criteria>". OUTPUT: post a concise assessment as a comment on this issue (#830) — what works, what is rough, the top friction in the core loop, and the reasoning behind the ranking. If the ranking actually changed, open ONE PR for PRIORITIES.md: git switch -c codex/product-830, git push -u origin codex/product-830, gh pr create --base main --label codex --title "<title>" --body "<summary, Closes #830>", then gh pr merge --squash --auto --delete-branch. If the queue is already accurate, do NOT open a PR — just close this issue (gh issue close 830). Do NOT make breaking public-contract changes (MCP/A2A/REST/webhooks/env vars), pricing changes, brand/positioning rewrites, or large refactors yourself — surface those in the assessment for the human. Do not use the make_pr tool (it is a no-op stub).

[asim]

Assessment (2026-06-30 UTC):

• Works: the guest web first-run page is clear and usable without an account: the page loads quickly, states “An agent for everyday,” exposes a single prompt, and posts to /agent. Home/service pages for news, markets, weather, video, blog, and social all returned HTTP 200 in roughly sub-2s checks. The weather ask → answer loop is materially improved: “What is the weather in London today?” returned a streamed, well-formatted answer anchored to Tuesday, 30 June 2026, with no impossible date.
• Rough: the latest-news core loop still has a mixed-provider degradation bug. A guest prompt for “What are the latest AI news headlines today?” invoked news and web search, then returned raw escaped search context plus “Unavailable: news” instead of readable source-linked bullets. That is the top remaining friction because it makes an everyday ask look broken even though one provider appears to have usable results.
• Queue state: Fix impossible dates in weather answers #824 is closed by recent weather work (Anchor weather answers to real forecast dates #827/Anchor weather tool context dates #829), and there are no open codex PRs or open codex issues before filing the new gap. I filed Make news-backed agent answers user-readable when one provider is unavailable #831 for the news mixed-provider readability failure and re-ranked PRIORITIES.md to put it first, with Fix impossible dates in weather answers #824 moved to shipped.
• Ranking reasoning: THESIS says Now is seamlessness/PMF and the protected loop is a correct, well-formatted, fast answer for guests and signed-in users. The weather bug is now done; the highest-value remaining issue is not new surface area but graceful synthesis/readability in an existing service-backed ask. Signed-in and chat-client checks were not fully observable from this environment without user credentials/client access, so I prioritized the directly observable guest web regression and kept public contracts unchanged.

PR opened for the ranking change: #832.

[chatgpt-codex-connector]

Summary

• Reviewed the North Star/canon and live product, filed the newly observed mixed-provider news readability gap as issue Make news-backed agent answers user-readable when one provider is unavailable #831, and updated the ranked queue so Make news-backed agent answers user-readable when one provider is unavailable #831 is now the top PMF/refinement item.
• Moved the now-closed impossible-weather-date work into “Already shipped,” reflecting Fix impossible dates in weather answers #824’s closure via PRs Anchor weather answers to real forecast dates #827 and Anchor weather tool context dates #829.
• Posted the requested concise assessment on issue Product review #18 #830 and opened/merged PR Refresh product priorities after review 830 #832 with the priority update.
• Committed the change on branch codex/product-830 with commit 906b523 and merged PR Refresh product priorities after review 830 #832.

Testing

• ✅ find .. -name AGENTS.md -print
• ✅ sed -n '1,220p' CLAUDE.md && sed -n '1,260p' internal/docs/THESIS.md && sed -n '1,220p' README.md && sed -n '1,220p' docs/VISION.md && sed -n '1,220p' docs/PRINCIPLES.md && sed -n '1,260p' internal/docs/PRIORITIES.md
• ✅ gh pr list --state open --label codex --json number,title,headRefName,updatedAt,url --limit 50
• ✅ gh pr list --state merged --json number,title,mergedAt,url --limit 20
• ✅ gh issue list --state open --label codex --json number,title,updatedAt,url --limit 100
• ✅ gh issue view 824 --json number,title,state,closedAt,url,labels
• ✅ curl -L --max-time 20 -sS -D /tmp/mu_headers https://micro.mu/ -o /tmp/mu_home.html
• ✅ curl -sS --max-time 60 -N -H 'Content-Type: application/json' -X POST https://micro.mu/agent -d '{"prompt":"What is the weather in London today?","model":"standard","history":[]}'
• ✅ curl -sS --max-time 60 -N -H 'Content-Type: application/json' -X POST https://micro.mu/agent -d '{"prompt":"What are the latest AI news headlines today?","model":"standard","history":[]}'
• ✅ for p in /news /markets /weather /video /blog /social; do curl -L -sS --max-time 20 -w '\nHTTP %{http_code} time %{time_total}\n' https://micro.mu$p -o /tmp/mu_${p#/}.html; done
• ✅ git diff -- internal/docs/PRIORITIES.md
• ✅ git commit -m "Refresh product priorities after review 830"
• ✅ git push -u origin codex/product-830 && gh pr create --base main --label codex --title "Refresh product priorities after review 830" --body ...
• ⚠️ gh pr merge 832 --squash --auto --delete-branch initially failed because local origin/main had not been fetched in this checkout.
• ✅ git fetch origin main && gh pr merge 832 --squash --auto --delete-branch
• ✅ gh pr view 832 --json number,state,mergeStateStatus,isCrossRepository,autoMergeRequest,url

View task →