EARLY ACCESSMagicStride is onboarding early-adopter organizations — help shape the platform.Request access

DOCUMENTATION / CORE CONCEPTS

A shared language for workflow owners and technical teams.

These terms explain how MagicStride organizes workflows and the work around them — written so the business owner and the engineer can use the same words.

/01

Workflow and workflow template.

A workflow describes how a type of work moves from a goal to an outcome. A ready-to-use workflow provides a starting point; teams can adapt it or create a new workflow, within the capabilities of their plan.

/02

People, agents, and responsibility.

People may set direction, review work, make decisions, or handle exceptions. Agents may carry out defined steps. A workflow makes those responsibilities visible — so everyone can see who owns what.

/03

Inputs, connected systems, and models.

A workflow uses the information, systems, and model/provider connections available and approved for it. The supported options depend on the current product configuration and the plan.

/04

Results and review.

The workflow returns its result to the next step or reviewer. What is retained — the outcome, the decisions, and the working — is agreed as part of the workflow's design.

STRAIGHT ANSWERS

Good questions.

What the platform is, who it’s for,
and how implementation works.

Read the documentation
Are these terms the exact labels in the product?

This guide explains the concepts. Refer to the current product interface and technical documentation for exact labels and availability.

WORK WITH MAGICSTRIDE

Bring the work. We'll shape how
people and agents get it done.

Tell us about the process your team wants to improve — a report, a review, a queue, an onboarding. We can configure and deploy it directly, or co-deliver it with your team.

PROVEN STARTING POINTS · DIRECT IMPLEMENTATION · CO-DELIVERY