Core Concepts
Supported vs Assisted Capabilities
How Morph determines what is built autonomously
What This Classification Means
Morph does not treat all functionality the same.
When Morph analyzes your requirements, it classifies each capability in your specification as either Supported or Assisted. This tells you, before implementation begins, what Morph will build autonomously through sprints and where human engineering involvement is needed.
Supported capabilities are built entirely by Morph within the autonomous execution surface. These move directly into sprint execution.
Assisted capabilities require human engineering support to complete. This typically applies to third-party integrations, specialized external services, or logic outside the platform's current autonomous build surface.
This classification is not a constraint on what your application can do. It is a transparency mechanism that makes execution boundaries explicit before work begins.
Where You’ll See It
The Supported vs Assisted classification is shown during review phases so you can confirm what Morph will build autonomously and what, if anything, requires coordination.
1. Requirements Review
Within the Requirements sprint, Morph summarizes capability status in one review surface:
The System Overview labels architectural components as Supported and, when applicable, Assisted.
The Capability Summary lists Supported functionalities and, if any exist, Assisted functionalities.
If your project is fully Supported, you will only see Supported items and no Assisted items will be listed.
2. System Design
In the System Design sprint, the same classification is reiterated within the finalized architecture. If Assisted items exist, they will be called out explicitly. If the system is fully Supported, the document will reflect that.
What to Do If a Capability Is Assisted
If something critical to your application is marked Assisted, you have several options.
Evaluate roadmap timing
Morph continuously expands its autonomous build surface. Some Assisted capabilities may transition to Supported. If timing matters, contact our team to confirm current status.
Engage implementation support
For capabilities required at launch, the Morph team can provide engineering support to implement the Assisted component alongside your autonomous build.
Adjust scope
You may choose to redesign a feature using currently Supported approaches or defer the Assisted capability to a later phase. In many cases, this is the fastest path to initial deployment.
How This Affects Your Build
Assisted capabilities influence how the build is executed, not whether it can be built.
Supported capabilities proceed through autonomous sprint execution as planned.
Assisted capabilities, if present, may require additional coordination to implement depending on the integration or logic involved.
The Requirements review is the right moment to confirm these classifications so you can choose the best path forward before implementation begins.
Classifications Evolve Over Time
Morph is actively expanding what it can build autonomously. A capability marked Assisted today may become Supported as the platform evolves.
If a specific capability is central to your application, it is worth confirming its current status before finalizing scope.
If your project includes Assisted capabilities and you want guidance on execution pathways, integration planning, or scope tradeoffs, contact the Morph team. We can help you determine the most effective approach before you proceed.
Related Documentation
Requirements & System Overview - Step-by-step explanation of how Supported and Assisted classifications appear in your project
Autonomous Sprints - How Supported capabilities move through bounded execution phases
Requirements (Core Concepts) - How Morph translates conversational intent into structured specifications
What This Classification Means
Morph does not treat all functionality the same.
When Morph analyzes your requirements, it classifies each capability in your specification as either Supported or Assisted. This tells you, before implementation begins, what Morph will build autonomously through sprints and where human engineering involvement is needed.
Supported capabilities are built entirely by Morph within the autonomous execution surface. These move directly into sprint execution.
Assisted capabilities require human engineering support to complete. This typically applies to third-party integrations, specialized external services, or logic outside the platform's current autonomous build surface.
This classification is not a constraint on what your application can do. It is a transparency mechanism that makes execution boundaries explicit before work begins.
Where You’ll See It
The Supported vs Assisted classification is shown during review phases so you can confirm what Morph will build autonomously and what, if anything, requires coordination.
1. Requirements Review
Within the Requirements sprint, Morph summarizes capability status in one review surface:
The System Overview labels architectural components as Supported and, when applicable, Assisted.
The Capability Summary lists Supported functionalities and, if any exist, Assisted functionalities.
If your project is fully Supported, you will only see Supported items and no Assisted items will be listed.
2. System Design
In the System Design sprint, the same classification is reiterated within the finalized architecture. If Assisted items exist, they will be called out explicitly. If the system is fully Supported, the document will reflect that.
What to Do If a Capability Is Assisted
If something critical to your application is marked Assisted, you have several options.
Evaluate roadmap timing
Morph continuously expands its autonomous build surface. Some Assisted capabilities may transition to Supported. If timing matters, contact our team to confirm current status.
Engage implementation support
For capabilities required at launch, the Morph team can provide engineering support to implement the Assisted component alongside your autonomous build.
Adjust scope
You may choose to redesign a feature using currently Supported approaches or defer the Assisted capability to a later phase. In many cases, this is the fastest path to initial deployment.
How This Affects Your Build
Assisted capabilities influence how the build is executed, not whether it can be built.
Supported capabilities proceed through autonomous sprint execution as planned.
Assisted capabilities, if present, may require additional coordination to implement depending on the integration or logic involved.
The Requirements review is the right moment to confirm these classifications so you can choose the best path forward before implementation begins.
Classifications Evolve Over Time
Morph is actively expanding what it can build autonomously. A capability marked Assisted today may become Supported as the platform evolves.
If a specific capability is central to your application, it is worth confirming its current status before finalizing scope.
If your project includes Assisted capabilities and you want guidance on execution pathways, integration planning, or scope tradeoffs, contact the Morph team. We can help you determine the most effective approach before you proceed.
Related Documentation
Requirements & System Overview - Step-by-step explanation of how Supported and Assisted classifications appear in your project
Autonomous Sprints - How Supported capabilities move through bounded execution phases
Requirements (Core Concepts) - How Morph translates conversational intent into structured specifications
