System map

How it all connects

Scroll: the map builds column by column, from the sources to you. Then it follows one link end to end, shows where a new skill plugs in, and how your decisions become rules.

SOURCESROOT FOLDERROUTINESAGENTS & SKILLSARTIFACTSyour decisions become rulesMailread-onlyCalendarwrite after approvalCloud storageshared documentsPubMed · trainingpublic sourcesDownloadswhat comes inDepartment scheduleread-onlyRules and plans_SYSTEMWork foldersflatLocal mail indexfast searchResearch databaseaggregates onlyHolding areafiles in doubtArchivenever deleteMorningtriage, daily planEveningprojects, decisionsFilingevery eveningWeeklydeadlines, watchMonthlyCV, index, backupmail-triageby actionfilingrule of doubtorchestratorroutes, never doesmanuscript-reviewnever overwritecongress-talkplan approved firstliterature-watchweekly digestnew skillyour next building blockDashboardanticipation, in a databaseApproval pagesapprove · fix · discardMonitoringstatus lightsSkills mapwho does whatYoudecide, send, sign
  • flow
  • read-only
  • plan or rule
  • hand-over
  • database write
  1. 1

    What comes in

    Everything starts from six sources. The AI reads them; it writes to none of them without your approval. The department schedule stays strictly read-only.

  2. 2

    One root folder

    Whatever the AI must see lives in a single folder: rules and plans, flat work folders, a mail index for fast search, a holding area for files in doubt, and an archive instead of a bin.

  3. 3

    Routines that read a plan

    Four or five scheduled routines, not twenty-five. Each reads its run plan in the rules folder: adding a task means adding a line to the plan.

  4. 4

    Agents and skills do the work

    Routines call the agents and their skills. An orchestrator does nothing itself: it qualifies the request and hands over to the right building block (purple dashes).

  5. 5

    Artifacts to see

    Skills write into the artifacts' databases (gold lines): the dashboard, the approval pages, the monitoring page, the skills map. The page stays the same; its data changes.

  6. 6

    You, at the end of every chain

    Nothing leaves without you: sending, signing, writing to the calendar. Your decisions on approval pages become rules that the next routine will read.

  7. 7

    Follow one link end to end

    An email arrives → it is indexed → the morning routine applies its plan → the triage skill sorts it by action → it writes it into the dashboard → you decide. Every arrow is written somewhere: a plan, a hand-over or a database write.

  8. 8

    Add a skill

    An instruction comes back three times? Write a skill, declare who calls it (here the orchestrator) and where it writes (the dashboard), then add it to the skills map. A link that is not written does not exist.

  9. 9

    The improvement loop

    Your corrections on approval pages are reviewed every week and become rules or skill updates, which you install after reading. The system improves without ever acting in your place.

Academic map: who hands over to whom

Each box is a real skill; each link, a handover. Hover over a skill to see its links.

SystemOrchestratorA · ResearchB · CongressC · DepartmentD · CareerE · Teachingreacteurgestion-mailcapture-agendaagendaannuaireclassementfichieracademiquearticlebiblioresearchveillesoutenance-thesemegabase-cardiomegabase-requetepresentation-congrespresentationesc365-toposlidepdf-figure-vers-diapocas-cliniqueechoechopacirm-cardiaquecongres-organisationstaffplanningcvhistoriquebilan-activiteidentitefacdiu-echoformation

Agents and their skills →All building blocks