Systems Overview

Use this section when you already know the feature area you need to change, but not yet the exact file or module.

The frontend is easier to navigate by system than by folder. The main systems are:

• workflow
• experiments
• data analysis and model execution
• query and find-data
• store and files
• tool development
• data modeling
• local operations

These are not all isolated. Some of them sit on top of shared modules, and some of them only exist in one app.

Start here

If the change is about...	Start here
flow editing, workflow detail, or workflow validation	Workflow system
app-owned experiment pages and run comparison	Experiments system
model execution, outputs, uploads, or run chat	Data analysis system
query composition or query UI reused in local views	Query system
browsing store content or platform files	Store and files system
app authoring, config, validation, or test app setup	Tool development system
schema, ontology, datatype, or UMLS work	Data modeling system
cohort, patient, connector, training, logs, or admin	Local operations system

If you are still figuring out app ownership rather than feature ownership, go back to Workspace map or Where to change what.

Fast rule

If a feature smells cross-cutting, check projects/shared-lib/src/lib/modules first.

That is where most of the reusable system code already lives:

• workflow
• app-execution
• experiments
• store
• files
• data-modeler

These pages are intentionally practical. They are meant to tell contributors where to start, what the system owns, and which neighboring system they should inspect next.