Documentation

SenSym Data Factory: the opposite of blackbox. Every generated value comes from a distribution you set and can see; every export ships a data dictionary and a provenance record naming exactly how it was made.

Start here#

• Getting started — launch, describe a dataset, and export your first file in under 3 minutes.
• Sample recipes — five real, ready-to-run recipe files spanning a first tabular dataset, a business table, a declared causal structure, cohort generation, and multi-modal speech narration. Open one and see the product working before building anything by hand.

Concepts and walkthroughs#

• Scenario Mode — the three answer tiers (template, local, cloud) and how a description becomes a recipe.
• Building without Scenario Mode — typing columns and choosing distributions by hand, one field at a time.
• Settings overview — a tour of all seven Settings panels, with what each control actually does.
• Recipe files — saving, opening, and why there is only one recipe format, shared with the CLI.
• Recipe library — a live view over your project library folder: open, duplicate, reveal, or delete a saved recipe.
• Cohort generation — one seeded dataset per row of a class roster.
• The causal graph view — declaring a treatment/outcome/confounder structure and reading its true, closed-form ATE.
• Speech narration — installing the real neural TTS runtime and reading a text column aloud into real WAV files.

Reference#

• Type catalog reference — every registered type, grouped by data category, with its real summary, example, and parameters. Generated from the live registry.
• CLI reference — every sensym command and flag. Generated from the real argparse tree; shell completions and a man page are generated alongside it in completions/ and sensym.1.
• Type-catalog build inventory — the flat build-progress table catalog.md expands on.

All of the above are either hand-written and screenshot-verified against the real compiled app, or generated directly from the running registry/CLI/settings copy and drift-tested — see each generated page's own header for exactly which.