Yuri × Miguel meeting: fix the universe architecture — folders and languages — and align how the three Miguel projects fit into the larger universe. Today is about form and organization (functionality comes later), thinking about when the co takes over. All approved. ✅
Objectives
- Understand current organization (folders + languages)
- Separate what is content from what is scaffolding
- Align how the 3 projects fit into the Miguel universe
- Define how the universe presents itself when the co is downloaded
1. The central idea: content × form
The same idea as method organizes everything:
- Content = what is written (the texts). That’s what matters — and that’s all the co will use.
- Form = translation, visuals, widgets, publishing. It’s scaffolding: builds the site today, but the co takes over later.
Agreed: keep content clean and separate from scaffolding, so the transition to the co is easy. ✅
2. The 3 projects inside the Miguel universe (MG)
Miguel is the umbrella universe (the person, the hub). Each project is a mission = a group of people with a clear and measurable goal:
the three missions
- MSE (
MGMSE) — undergraduate in MS&E; it’s the base for the others.- App Agro (
MGAGRO) — WhatsApp bot for agricultural management.- Alpha Scholars (
MGALPHA) — study universe (22 hours a week).
How they fit in:
Miguel (MG) — hub pessoal
├── MSE (MGMSE) — já é universo próprio
├── App Agro (MGAGRO) — seção hoje → vira universo
└── Alpha Scholars (MGALPHA) — seção hoje → vira universo
- Each project is a child sub-universe of Miguel. MSE is already a separate universe; App Agro and Alpha Scholars today live as sections inside Miguel and become their own universe when they grow (same promotion we’ve done before).
- The MG code ties the whole tree together:
MG-in the hub,MGMSE·MGAGRO·MGALPHAin each mission — one identity only. - When the co loads Miguel, the projects appear next to it, like children; audiences can be subscribed.
Agreed: hub + missions; each mission promotes its universe when it matures. ✅
3. Folders — organize
how it looks
- At the top: what matters (content + universe profile + translation memory)
- Next to it: scaffolding, marked as disposable
- Separately: references (drafts, comparisons)
Clean content → transition to the co is just “point to content”. ✅
4. Languages (PT / EN)
- PT is original; EN is an auto-translated copy, page by page.
- The translation has saved memory — doesn’t re-translate unnecessarily, and the co can use it later at no cost.
- Switching languages is form (a button), not part of the menu.
- Chosen translation model: Sonnet (see comparison). ✅
5. Board and widgets
- Tasks live in the tables within the text (single source). The kanban is just a view — the co has its own board that reads the same tables.
- The calendar is a real widget; the co needs space to embed widgets like this.
Agreed: table is the source; kanban is disposable. ✅
6. When the co is downloaded (first time)
The universe should introduce itself: which is the homepage, which languages, who is parent and who is child, what is public.
- Then the user opens the co and lands on Miguel’s hub with projects beside it to subscribe — no setup needed.
- To decide: is Miguel a public showcase or a more private hub? The new user path points to private hub + public projects. ⬅️ only open question
What was decided ✅
- Content separated from scaffolding
- 3 projects = child missions of the hub; promote their universe when they grow
- Saved translation memory; default model = Sonnet
- Markdown table = single source of the board
- Miguel public (showcase) × private (hub) — close today