oxFlow Wiki

Daily Log — 2026-04-17

3 min read

Tasks

Action points out of the 2026-04-16 Thursday 361 meeting — Oxflow overview:

  • Database analysis — analyse the different databases for Oxflow (S3, AWS, Neon). Pros and cons. Existing platform solutions. · Bilal Jawadi (@bilaljawadi45)
  • AWS — chosen platform for Oxflow. Look into its nuances in light of estimation software. What do we need to expect? Any other estimation platforms that use this infrastructure? How does it fit with the CI/CD workflow and BMAD? · Bilal Jawadi (@bilaljawadi45)
  • Superpowers plugin for Claude Code — what is it? How does it fit in with BMAD? · Bilal Jawadi (@bilaljawadi45)
  • CI/CD workflows — what is it? How do we set it up and document it for the team so we are all on the same page? Something visual — Excalidraw, HTML files with Opus 4.7. Setting up actual environments and GitHub setups. Agents triggered through webhooks to review. Ties in with Multica or Managed Agents Platform from Claude. · Ibrahim Houissa (@ibrahim-h361)
  • Shared project memory & shared CLAUDE.md — research how Claude Code memory works across team members and sessions; shared-repo CLAUDE.md patterns; memory MCPs for team-wide recall; how our conventions in this repo should evolve as more people start using Claude on it. · Ibrahim Houissa (@ibrahim-h361)
  • Claude Managed Agents + Multica — for automatic pull-request reviews and other code reviews. · Bilal Jawadi (@bilaljawadi45)
  • Git research — GitHub projects, getting Claude to automate things for the team on GitHub. · Bilal Jawadi (@bilaljawadi45)

Notes

  • Moved working memory off Google Drive today. This repo (oxflow-hub, formerly oxflow-docs) is now the single source for daily logs, meeting notes, research, and decisions. See ../../TEAM.md for who’s who and ../../templates/README.md for how to write new docs.
  • The original Google Drive “Oxflow Work” folder had per-person subfolders colour-keyed by name. Colours don’t translate to markdown, so per-item attribution (Real Name (@handle)) replaces them.
  • Question for the team: do we want the app docs viewer (app/app.js) to surface daily logs in its sidebar, or is browsing via github.com fine? Leaning github.com for now — one fewer manual step per day.

Done today

  • Scaffolded ../../templates/ with daily-log / meeting / research / ADR templates.
  • Created ../../TEAM.md with the four GitHub handles → real names mapping.
  • Added ../../CLAUDE.md so any LLM working in this repo picks up the conventions automatically.
  • First daily log (this file) migrated from the Google Drive doc.

Next

  • Pick the first action-point task and write its research note (likely Database analysis or the Azure vs AWS question).
  • Decide whether to write an ADR capturing “we moved team working memory from Google Drive to this repo” — probably yes, it’s the kind of thing a future teammate will want to understand.

References

  • Meeting this log works from: tbd — 2026-04-16 meeting notes not yet written to the repo; will land at meetings/2026-04-16-oxflow-overview.md
  • Templates: ../../templates/README.md
  • Team: ../../TEAM.md

Graph View

Backlinks