yuri × Miguel meeting: sort out the universe’s architecture — folders and languages — and agree on how the three Miguel projects fit into the larger universe. Today is about form and organization (we’ll deal with functionality later), thinking ahead to when co takes over. Everything approved. ✅
Goals
- 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 downloaded
1. The central idea: content × form
The same idea from method organizes everything:
- Content = what is written (the texts). It’s what counts — and it’s all that co will use.
- Form = translation, visuals, widgets, publishing. It’s scaffolding: it builds the site today, but co takes over later.
Agreed: keep the 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 goal:
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 a 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 already is a separate universe; App Agro and Alpha Scholars today live as sections within 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 alongside it, as children; the public ones can be subscribed to.
Agreed: hub + missions; each mission is promoted to a universe as it matures. ✅
3. Folders — tidy up
how it looks
- At the top: what counts (content + the universe’s record + the translation memory)
- Alongside: the scaffolding, marked as disposable
- Set apart: the references (drafts, comparisons)
Clean content → the switch to co is just “point at the content”. ✅
4. Languages (PT / EN)
- PT is the original; EN is an automatic translated copy, page by page.
- The translation has stored memory — it doesn’t re-translate needlessly, and co reuses it later at no cost.
- Switching language is form (a button), it doesn’t go in the menu.
- Chosen translation model: Sonnet (see comparison). ✅
5. Board and widgets
- The tasks live in the text’s tables (single source). 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 fit widgets like this.
Agreed: the table is the source; the kanban is disposable. ✅
6. When co is downloaded (first time)
The universe should present itself on its own: what the home page is, which languages, who is parent and who is child, what is public.
- Then the user opens co and lands on the Miguel hub with the projects beside it to subscribe to — without configuring anything.
- To decide: is Miguel a public showcase or a more private hub? The new user’s path points to a private hub + public projects. ⬅️ the only open question
What was decided ✅
- Content separated from scaffolding
- 3 projects = child missions of the hub; promoted to universes as they grow
- Translation memory stored; default model = Sonnet
- Markdown table = single source of the board
- Miguel public (showcase) × private (hub) — settle today