Skip to content

Type to search titles, section headings and summaries across the Developer Portal.

↑ ↓ to move · Enter to open · Esc to close · searched locally in your browser

Concept

Understanding the Synthex Platform Architecture

The proposed engineering layers connecting scenario design, data generation, annotation, model training and evaluation, and where conceptual boundaries sit.

Page type: Explains how the platform is designed to fit together.

High-level architecture

Five layers, from the interfaces people use down to generic infrastructure concepts.
  1. Experience layer

    • Developer documentationImplemented
    • Research workflowsproposed
    • Future platform interfacesproposed
  2. Orchestration layer

    • Workflow configurationproposed
    • Job lifecycle conceptsproposed
    • Experiment metadataproposed
  3. Engine layer

    • Simulation Engineproposed
    • Data Engineproposed
    • Evaluation Engineproposed
  4. Data layer

    • Dataset artefactsproposed
    • Annotationsproposed
    • Scenario metadataproposed
    • Experiment reportsproposed
  5. Infrastructure concepts

    • Computeproposed
    • Storageproposed
    • Versioningproposed
    • Monitoringproposed
Solid: implemented Dashed: conceptual or proposed

Workflow relationships

  • Simulation produces scenario outputs: sensor data, ground truth and scenario metadata.
  • The Data Engine manages dataset preparation and annotations: it checks quality, then versions and packages datasets with manifests.
  • Model training may happen in an external customer environment with the customer's own framework and compute. Synthex does not offer model training as a managed service.
  • The Evaluation Engine assesses models and reports findings overall and per scenario condition.
  • Evaluation informs new scenarios and dataset improvements: failure categories become the next scenario requirements.
Workflow relationships
Conceptual workflow
  1. 01Scenario definition
  2. 02Simulation Engine: scenario outputs
  3. 03Data Engine: annotations, QA, packaging
  4. 04Model training (external environment)
  5. 05Evaluation Engine: metrics and findings

Evaluation findings inform new scenarios and dataset improvements

Batch processing concept

Generation and evaluation are long-running, so a platform would process them asynchronously. One possible lifecycle:
Possible asynchronous job lifecycle
Conceptual workflow
  1. 01Job submission
  2. 02Validation
  3. 03Queue or scheduling
  4. 04Compute execution
  5. 05Artefact storage
  6. 06Quality checking
  7. 07Completion status

Data governance

Dataset provenance
Every sample records whether it is real, synthetic or derived, and how it was produced.
Metadata
Scenario parameters, seeds, annotators and versions travel with the data, not in separate notes.
Access controls
Datasets are only as open as their licence and governance allow; sensitive data stays where its owner keeps it.
Versioning
Datasets, scenarios and models are referenced by immutable versions so results stay comparable.
Usage rights
Licences and usage restrictions are recorded in the manifest and respected downstream.
Traceability
A report can be traced back to the exact model, dataset version, configuration and seed.
Research reproducibility
Anyone with access can re-run an experiment from its recorded configuration.

System boundaries

The proposed design keeps clear boundaries between what Synthex would operate and what stays with the customer:

  • Customer environment: model training, model weights, and any sensitive or regulated source data, unless an engagement explicitly agrees otherwise.
  • Exchange format: datasets, manifests, scenario configurations, experiment configurations and reports, all in open, documented formats.
  • Simulator boundary: scenario definitions stay independent of any single simulator, with adapters translating them.
  • Public documentation boundary: this portal never publishes hosts, private endpoints, account identifiers, credentials or operational runbooks.