Now
Understand the product through the single-capability loop first
The current platform can already complete the single-capability loop of identifying a need, recommending a capability, confirming execution, and returning a result in a stable way.
Orchestration
Orchestration
Roadmap After 2.0Capability orchestration is not part of the delivered
1.0 / 1.1 scope today. It becomes a formal product direction only after 2.0.Only after trusted single-Skill execution is stable, and after the platform closes composite-request decomposition, node-level confirmation, formal fallback or rollback, and partial-success or recoverable states, should orchestration become a real product layer.
Orchestration is not about piling more buttons together. It is about taking multiple execution steps and turning them into one real working chain that still sits inside rules.
multi-step executionparameter passinghuman confirmationresult handofffull-chain trace
Next
Later extend into multi-step task chains
The next step is not only step linking and parameter passing. It also includes composite-request decomposition, node-level confirmation, formal fallback or rollback, and partial-success or recoverable states.
EXECFABRIC // ORCHESTRATIONDOC 04
const step01 = 'identify_need'const step02 = 'match_skill'const step03 = 'confirm_then_run'const step04 = 'pass_result_forward'
MULTI STEP / CONFIRMED / TRACEABLE
Stringing several Skills together is not enough. Formal productization requires at least the following constraints and recovery capability.
Need decompositionSplit a composite request into step nodes that can be confirmed
Node confirmationHigher-risk steps must still be able to stop and wait for human confirmation
Failure rollbackThe system must know where the chain failed and whether fallback or rollback is allowed
Chain traceThe input, artifacts, and state of the whole task chain must remain traceable
Available Now
What already exists today
- AI identifies the need
- A Skill is recommended inside the permission boundary
- Human confirmation exists
- A single capability can execute
- The result returns with audit traces kept
What It Adds
What orchestration would add later
- One task splits into multiple steps
- Multiple Skills or capability nodes execute in sequence
- Parameters, results, or file references pass between steps
- Higher-risk steps can require additional confirmation
- The whole chain keeps logs, audit, and failure records
Best Fit
Which scenarios fit orchestration
- Collect first, then clean, then generate a report
- Read data first, then transform it, then write into a target system
- Generate a result file first, then notify or archive
- Organize multiple reusable capabilities into one stable task chain
Current Phase
How to read the current phase correctly
- The platform already stabilizes trusted single-Skill execution
- Multi-step orchestration is not a delivered
1.0 / 1.1capability - Formal orchestration belongs to the product direction after
2.0 - This path becomes valuable when a task needs multiple confirmations, parameter passing, file handoff, or cross-step tracking
Summary
One-sentence summary
ExecFabric is first stabilizing trusted single-Skill execution. After the governance base is stronger, it can expand after 2.0 into a multi-step orchestration platform that remains confirmable, traceable, and auditable.