Maestro should generate an empty cluster environment on a directory which can be versioned directly. Generated files in the environment should be ignored by default. Consider installing maestro using a package manager like homebrew and apt, so that the maestro cli is available system-wide and metadata about generated clusters is kept in ~/.maestro or similar. The user then generates new cluster environments or initiates from existing ones. This makes the whole approach much cleaner, more intuitive and user-friendly.