The work model.
A workflow describes how a type of work moves from a goal to an outcome: its steps, the people and agents responsible for each, the information and systems it may use, and what happens at exceptions. Proven starting points cover common cases; your team extends them.
Models and providers.
Work runs against the model and provider options agreed for it — across leading labs, open-source models, and specialist providers. The supported list, connection approach, and any customer-managed requirements are confirmed during planning — talk to us about your providers.
Systems and integrations.
The work reaches the systems approved for it during implementation. Integration fit is confirmed per use case rather than promised as a universal list — tell us what it needs to reach.
Hosting and data boundaries.
The two monthly plans run on MagicStride's shared service — hosted and operated by us, with each organization's workflows and records scoped to it. Enterprise engagements can be scoped to different hosting and data-handling requirements — the specifics are agreed as part of the engagement.
Readable by humans. Fetchable by agents.
Public documentation has HTML and Markdown representations from one content model. Request a page with Accept: text/markdown, or follow its .md alternate.
curl -H "Accept: text/markdown" \
"$SITE_URL/architecture"Built to be extended with you.
Direct implementation means MagicStride configures and deploys the workflow; co-delivery means we build it alongside your engineers. Either way, the organization ends up able to operate and adapt what it owns.