mAi 68121c6e51 chore: bootstrap projax scaffolding + PRD
Copy the design PRD, .claude config, .m config, .mcp.json, and AGENTS.md
symlink from m's main working tree so the worker has the full project
context before starting Phase 1 implementation.
2026-05-15 13:09:32 +02:00

projax

m's personal project + self-management system. The data backbone for everything m tracks — code projects, physical projects, strategic threads, life themes, daily ops. Multiple interfaces consume the same model. Otto is one of them, not the owner.

Status

Bootstrap. Inventor designs schema + lifecycle + interface contracts before any code lands.

Vision

  • Single source of truth for what m is doing, has done, will do, is sitting on, is procrastinating about.
  • Multiple interfaces (none is canonical): Otto-PWA, browser UI, Excalidraw views, CalDAV task lists, CLI is not a requirement (m explicitly opted out).
  • Project Code as the lingua franca — concise, human-readable, ambiguity-free across all interfaces.
  • Subsumes today's scattered state: mai.projects, Gitea issues, CalDAV tasks, mBrian topic-hubs, Dokploy services, ~/dev/CLAUDE.md files. Migration over time.
  • Goes beyond code: physical projects (mGreen greenhouse, household), strategic threads (career positioning), life themes (sport goals, learning) — all first-class.

Out of scope (for now)

  • Replacing mai.projects-the-table. projax will likely own it instead, or sync, or supersede gradually — design pass decides.
  • Multi-user. m only.
  • Public exposure / sharing. Local-first, runs on m's infra.
  • Becoming a generic project-management product. Built for m's stack and tone.

Architecture (TBD by inventor)

Open questions for the first design pass:

  • Schema shape: relational (Postgres? SQLite?) vs graph (mBrian-style) vs hybrid
  • Project Code generation: shortcode pattern, collision rules, retro-fitting to existing 30+ projects
  • Lifecycle states + transitions (idea → active → paused → done → archived?)
  • How interfaces share the model — REST API? GraphQL? direct DB read?
  • Where the data lives: msupabase schema? Own DB? mBrian sub-graph?
  • Integration shape with: mai.* (tasks, workers, sessions), Gitea, CalDAV, mBrian, Otto-PWA, Excalidraw
  • Migration: 28 active mai.projects + ~15 test rows + 4 archived — how to clean up and import

Refs

  • mai.projects current state: msupabase mai.projects table
  • otto's project inventory walk-through (head session 2026-05-15)
  • mBrian topic-hubs (paliad, hlckm, tech-msbls, ai, professional-positioning, schadensberechnung-lizenzanalogie, flexsiebels-brand)
  • CalDAV calendars on dav.msbls.de: work, plan, privat, mhome, mcalendar, logm, people
Description
m's personal project + self-management system. Data backbone with multiple interfaces (Otto-PWA, web UI, Excalidraw views, CalDAV tasks).
Readme 775 KiB
Languages
Go 88.4%
CSS 6.6%
PLpgSQL 4.7%
JavaScript 0.2%