Reported by: codex
Suggested exploration: identify the missing higher-level abstractions that would materially simplify common workflow patterns without obscuring runtime behavior
Affected surfaces: runtime primitives, workflow authoring model, long-term product direction
Question to answer
Which higher-level runtime primitives should SIH add beyond the current orchestration surface, and which of them provide enough leverage to justify the additional abstraction cost?
Why this matters
The roadmap calls out higher-level primitives as a mid-term direction, but the problem statement is still too broad to implement directly. Without a sharper definition, this risks becoming vague product drift instead of a decision-ready initiative.
Known facts
- SIH is currently strongest as a local-first API orchestration runtime.
- The runtime already supports composition, contract-aware validation, reporting, and structured workflow expressions.
- The roadmap explicitly lists higher-level runtime primitives as a future direction.
Unknowns
- Which user problems are not solved adequately by the current orchestration model.
- Which abstractions would reduce workflow complexity versus merely hiding it.
- How any new primitive would interact with YAML readability, validation, and MCP authoring flows.
Expected output
A recommendation set that identifies candidate primitives, their target use cases, the tradeoffs they introduce, and whether each should advance to a concrete feature issue or be discarded.
Notes
- Source: local roadmap at
.doc/positioning-and-roadmap.md.
- This issue was created while migrating local backlog ownership to GitHub.
Reported by: codex
Suggested exploration: identify the missing higher-level abstractions that would materially simplify common workflow patterns without obscuring runtime behavior
Affected surfaces: runtime primitives, workflow authoring model, long-term product direction
Question to answer
Which higher-level runtime primitives should SIH add beyond the current orchestration surface, and which of them provide enough leverage to justify the additional abstraction cost?
Why this matters
The roadmap calls out higher-level primitives as a mid-term direction, but the problem statement is still too broad to implement directly. Without a sharper definition, this risks becoming vague product drift instead of a decision-ready initiative.
Known facts
Unknowns
Expected output
A recommendation set that identifies candidate primitives, their target use cases, the tradeoffs they introduce, and whether each should advance to a concrete feature issue or be discarded.
Notes
.doc/positioning-and-roadmap.md.