yuri × Miguel meeting: fixing the architecture of the universe — folders and languages — and agreeing on how Miguel’s three projects fit into the larger universe. Today is about form and organization (we’ll look at functionality later), thinking about when co takes over. Everything approved. ✅
Objectives
- Understand the current organization (folders + languages)
- Separate what is content from what is scaffolding
- Agree on how the 3 projects fit into the Miguel universe
- Define how the universe presents itself when co is installed
1. The central idea: content × form
The same idea from method organizes everything:
- Content = what is written (the texts). That’s what matters — and it’s the only thing co will use.
- Form = translation, visuals, widgets, publishing. It’s scaffolding: builds the site today, but co takes over later.
Agreed: keep content clean and separate from the scaffolding, so the switch to 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, measurable objective:
the three missions
- MSE (
MGMSE) — MS&E degree; it’s the foundation of the others.- App Agro (
MGAGRO) — WhatsApp bot for farm management.- Alpha Scholars (
MGALPHA) — study universe (the 22 hours per week).
How they fit together:
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 currently live as sections inside Miguel and become their own universe when they grow (the same promotion we’ve done before).
- The MG code ties the whole tree together:
MG-at the hub,MGMSE·MGAGRO·MGALPHAin each mission — a single identity. - When co loads Miguel, the projects appear beside it, as children; the public ones can be subscribed to.
Agreed: hub + missions; each mission promotes to a universe when it matures. ✅
3. Folders — cleaning up
how it looks
- At the top: what matters (content + the universe profile + the translation memory)
- Together: the scaffolding, marked as disposable
- Apart: references (drafts, comparisons)
Clean content → switching to co is just “point to the content”. ✅
4. Languages (PT / EN)
- PT is the original; EN is an automatic translated copy, page by page.
- The translation has saved memory — it doesn’t re-translate needlessly, and co can use it later at no cost.
- Switching languages is form (a button), not part of the menu.
- Translation model chosen: Sonnet (see comparison). ✅
5. Board and widgets
- Tasks live in the text tables (single source of truth). The kanban is just a view of them — co has its own board that reads the same tables.
- The calendar is a real widget; co needs a space to plug in widgets like that.
Agreed: table is the source; kanban is disposable. ✅
6. When co is installed (first time)
The universe should introduce itself: what’s the home page, which languages, who is parent and who is child, what is public.
- Then the user opens co and lands on Miguel’s hub with the projects beside it, ready to subscribe to — no configuration 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 to universe when they mature
- Translation memory saved; default model = Sonnet
- Markdown table = single source of truth for the board
- Miguel public (showcase) × private (hub) — close today