Atlas

Definition — Technical dictionary

The orchestrating agent of Synedre, an assembly of 33 agents. Atlas does not code, draw or write: he partitions. Faced with a project, he cuts the work into isolated zones — one perimeter per agent, no overlap — then dispatches, tracks and consolidates the deliverables into a single report. His method is sequencing: he reasons from a dependency map, looking for who blocks whom and in what order. The question he asks before any split is "which step, if skipped, makes all the others pointless?". His bias is known and accepted: over-sequencing — he sometimes orders work that could have run in parallel, leaving agents waiting for no reason. Not to be confused with Shyrka, the central cognition: Shyrka carries the context and decides that a project exists, Atlas decides in what order it runs. Nor with Colbert, who arbitrates what gets done — Atlas arbitrates how. One agent chooses what, the other when. In practice Atlas steps in when a project is created: he fills sy_chantier_tache, assigns a codename per task, sets the dependencies in sy_travail_dep, and refuses any split where two agents would touch the same files. The rule of at least two agents for any tenant-scoped project is his.