| Bloom | DataFactory's synthetic data engine. |
| Cardinality | How many child rows each parent has, e.g. 1–5 accounts per customer. |
| Connection | Saved details for reaching a source or target database. |
| Delete script | A script that deletes everything a prune didn't keep. Run it only on a copy of the source. |
| Diagnostics pack | A file with versions, service state and logs, secrets removed, to send to Enov8 support. Made in Admin → System. |
| Follow relationships | Bringing related rows along from linked tables when pruning. |
| Learn from source | Bloom matching table sizes from a real database, and copying the value mix of columns you approve. |
| Licence | The signed text from Enov8 that turns DataFactory on. Without a valid one it's read-only. |
| Pack | A group of industry or platform skills and templates an admin can show or hide. |
| Plan | A Bloom project: schema, relationships, skills, rules and run settings, on the Data, Generate and Advanced tabs. |
| Project brief | A short description of your business that guides Bloom and the AI. |
| Prune | DataFactory's subsetting engine. |
| Region | Australia, UK, US or Europe. Decides which country-specific skills and templates are shown. |
| Restore SQL | One SQL file that creates a prune's tables and inserts its rows. |
| Rule | A business rule Bloom enforces: date order, if/then, or parent total. |
| Seed | The number that makes a Bloom run repeatable. |
| Skill | A recipe for one kind of value, e.g. Medicare number (checksum-valid). |
| Starting table | A table a virtual data set starts from, e.g. customers. Related tables are found by following relationships from it. |
| Template | A ready-made industry schema with skills and rules set up. |
| Test database | A connection its owner has approved for Bloom to load into. |
| Virtual data set (VDS) | A saved definition of the tables you test with and everything they link to. |