modified: README.md

README.md

@@ -64,8 +64,17 @@ on the other hand, for example, `clas12Tags` triggers may use a new build of `cl
 
 The table below shows the configuration file versions and the `gemc` version, for each triggering repository:
 
-| Triggering Repository | `clas12-config` branch | `gemc` configuration `gcard` version | `coatjava` configurations `yaml` version | `gemc` version | `coatjava` version |
-| ---                   | ---                    | ---                                  | ---                                      | ---            | ---                |
+| Triggering Repository             | `clas12-config` branch | `gcard` version | `yaml` version | `gemc` version | `coatjava` version |
+| ---                               | ---                    | ---             | ---            | ---            | ---                |
+| `clas12-validation`               | `main`                 | latest          | latest[^1]     | `gcard`[^2]    | `development`      |
+| `coatjava`                        | `main`                 | latest          | latest[^1]     | `gcard`[^2]    | triggering version |
+| `clas12Tags`                      | `dev`                  | `dev`           | latest         | CI build       | `development`      |
+| `clas12-config`, `dev` branch     | `dev`                  | `dev`           | latest         | CI build       | `development`      |
+| `clas12-config`, any other branch | triggering version     | latest          | latest[^1]     | `gcard`[^2]    | `development`      |
+
+[^1] the latest `yaml` version that _is compatible_ with the `gcard` version.
+
+[^2] use the `gcard` version to `module switch` to the corresponding `gemc` version
 
 ## Legacy Version
 The original version of this repository is found in [release `v0.1`](https://github.com/JeffersonLab/clas12-validation/releases/tag/v0.1).