full

Overview ¶

Command target is the groomed user surface, compiling: user code is a mix of Resource, Activity, and plain control flow; everything else — registration, containers, delivery — is wiring the libraries hide.

Groomed decisions living in this file:

• The primitive is the HANDLE (pipeline.Resource[...]), not the verb: libraries bring their own constructors (k8sClient.Resource, dockerlib.Container, pipeline.NewAgent), all returning the same handle; the tree (Parent/Children), cascade, and visibility are properties of the handle.
• Specs are FOREIGN structs (crossplane-provider-yc here): plain fields their authors made — dependencies are explicit Ready calls, never wrapped Output types.
• Library resources (their activities) run on the run's worker: the user's kubeconfig never leaves the run's contour. The managed run container lives until the LAST resource of the run is deleted; the system keeps the resource tree to know that.
• Machine and Agent are two different resources: Machine is the real hardware we do not operate (here it is the crossplane vm), Agent is our process and record; its CloudInit identity goes into the vm's user-data. (MachineIntent — later.)
• Long life is a TRANSFER: the pipeline's Stand always exists; KeepFor bounds the stay under it.