Suggest edit — session-review-codex-2026-04-23

Title

Name

Note

---
visibility: public
---

# Session Review — 2026-04-23 picortex planning

## 1. Unresolved questions

- The biggest unanswered question is still the one Jacob explicitly reframed toward at the end: what is the minimum definition of an "awesome texting experience"? The session created `picortex-adb`/Q0 to answer it, but no answer exists yet, so every architecture choice still floats on top of an unpinned product target.
- OpenChat stayed unresolved. The session estimated reactions at about a day and a Linq-compatible adapter at 1-2 weeks, but it also discovered that the live `chat.globalbr.ai` deployment has no git remote and the public GitHub repo is stale, so the estimate rests on missing source control.
- The privacy/isolation question was scoped but not decided: Linux users only, Linux users plus `bwrap`/Landlock, two-box remote-host separation, or something more ephemeral. `picortex-1cy` exists, but Jacob's "if we really care about privacy" question remained open.
- The final user ask was left hanging: interview agents about WikiHub UX, preserve the session history, and ask Codex to review the full session for misses. The earlier Codex review covered the docs package, not the whole conversation.

## 2. Contradictions or pivots we should reconcile

- The docs still have two incompatible product stories. `README.md`, `llms.txt`, the PRD, ADR-0003, and Specs 002/003 all describe a tmux-centered architecture as the plan. But `docs/plans/2026-04-23-prototype-options.md` and `docs/wiki/piyush-era-design.md` explicitly reopen the core choice and even say Option 2 (`claude -c -p` / `--session-id`, two-box) is probably the best v0.1 shape.
- "No OpenClaw" was initially stated as a hard rule, including PRD NG7, but the later prototype-options doc reopens OpenClaw as Option 5. That is a valid pivot, but it is not reconciled. Right now the written docs simultaneously say "explicit non-goal" and "still on the table."
- The project status is stale at the top level. `AGENTS.md` says the first implementation stage is S1 of the initial roadmap, while the later Q0-Q8 tickets say implementation should not begin until the option bundle is chosen and the roadmap is replaced.

## 3. Missing tickets

- There should be a `picortex-` blocker ticket specifically for locating and/or reconstructing the real OpenChat source of truth. D3 assumes an adapter can be built later, but the session discovered a more basic blocker: nobody knows where the live code actually lives.
- There should be a `picortex-` or meta cleanup ticket for "choose option bundle, then reconcile README/PRD/ADRs/specs with the chosen architecture." Q0-Q8 decide the future, but no ticket retires stale tmux assumptions afterward.
- There should be a `wikihub-` ticket for agent-experience research itself: interview agents, summarize friction points, and turn them into a standing UX backlog. Several specific Agent UX tickets were filed, but the user's explicit interview/synthesis request was not.

## 4. Documentation gaps

- The docs package never absorbed the documentation-best-practices research that informed it. The report existed in `~/memory/research`, but nothing in `~/code/picortex/` records which conventions were adopted deliberately.
- The WikiHub publication outcome is missing from picortex's own docs. The session published the planning set to `wikihub.globalbr.ai/@jacobcole/picortex`, but the local README does not record that public mirror.
- The transcript's strongest reframing, "texting and mediating is the product; dev surface is optional," lives mainly in `prototype-options.md`. It never got promoted into the PRD itself, which still reads as if terminal/file-browser capability is part of the default answer rather than one branch of the decision tree.

## 5. Risks not acknowledged

- The plan underestimates product drift in Claude CLI itself. Both the tmux design and the Piyush-style per-turn design depend on exact CLI behavior (`-c`, `--session-id`, output formatting, auth persistence). That is a platform risk, not just an implementation detail.
- Group-text privacy risk is framed mostly as filesystem isolation, but not as social/data-retention risk. Saving other people's messages, files, and maybe knowledge-graph enrichments for long periods may create a trust problem even if the POSIX isolation story is sound.
- The simulator gap is bigger than the docs admit. linq-sim lacking reply/thread support was flagged, but real Linq/iMessage semantics for edits, reactions, threading, and delivery ordering may still diverge where this product cares most.

## 6. Net positive surprises

- The session produced a genuinely strong planning base in one pass: PRD, roadmap, ADRs, specs, wiki, repo-version pinning, and a second-opinion review. That is unusually disciplined for a zero-code day.
- The best move was the willingness to pivot instead of defending the first plan. The Codex review changed the roadmap, and the Piyush study reopened a simpler, probably better architecture instead of being dismissed because it was "old."
- Ticketing quality was high. The Q0-Q8 chain is the clearest part of the whole plan because it converts a vague product rethink into an ordered decision process.
- Using WikiHub immediately exposed real agent-UX pain, and that pain turned into concrete platform tickets the same day. That feedback loop is worth preserving.