Taratibu

Compute nodes only

new-repo

Make a GitHub origin. Clone it into origin-home. Make the kanban and the claims layout. Then make the repo match the standard.

ganda repo new <name>

Select a node, or run the path that the host uses.

How you write it

You write the routine in C#. Each call adds one node. Build makes the intermediate representation.

public static RoutineDefinition Build()
{
  return Routine.Named(RoutineId)
    .Compute("create-origin", CreateOrigin)
    .Compute("clone-origin-home", CloneOriginHome)
    .Compute("kanban-claims", KanbanClaims)
    .Compute("ensure", Ensure)
    .Build();
}

The file is source/timewarp-taratibu/routines/new-repo/new-repo.cs. Taratibu master 53de8c4.

Why this shape

A new TimeWarp solution follows a rule. It is not a judgment. This routine has four compute nodes. It has no classify step and no gate. The files gitignore, LICENSE, and README belong to the commands. They are not extra nodes. The repeat for ensure stays in the connection. The graph does not cycle until the standard is true.

What you get

  • A new origin is not an oracle. The model does not invent the layout.
  • This routine is not the command ganda repo setup. Setup is Peacock and the avatar. The graph stops at ensure.
  • The normal origin is private.

Rules

  • There is no classify step. There is no gate.
  • Each library function does not change the data. Ganda replaces each function.
  • Pass --public when the origin must not be private. Pass --dry-run to show the plan. Then the command makes no repo.

The drawing follows the D2 file in the repo. Node ids do not change. Ganda connects the commands. Ganda does not change the graph.