RFC: LSS 1.1 composition blocks #11
Replies: 4 comments
RFC LSS 1.1 — maintainer synthesis (2026-06-24)Summary of decisions while awaiting framework-maintainer feedback:
Artifacts synced to Loop-Core: Question for LangGraph / CrewAI / Cursor users: Does Full RFC: RFC-LSS-1.1-composition.md |
Framework maintainers — LSS 1.1 composition mappingRFC synthesis is merged; LangGraph / CrewAI / Cursor users: does this topology match your harness? composition:
type: parallel
children: [...]
adapters: [...]
merge: { strategy: synthesize }RFC: RFC-LSS-1.1-composition.md One paragraph on what maps / what doesn't is enough to unblock stable promotion. |
|
RFC outreach posted for framework mapping feedback:\n- LangGraph: https://github.com/langchain-ai/langgraph/issues/8186\n- CrewAI: https://github.com/crewAIInc/crewAI/issues/6316\n\nLSS 1.1 promoted to stable in Loop-Core: https://github.com/KanakMalpani/Loop-Core-Engineering/blob/main/specs/lss-1.1.md — errata welcome here. |
Wave 13 — subgraph ↔ nested / crew ↔ parallel mappingWe need one external framework mapping to close RFC #11. Reply with 3–5 bullets:
Example composed spec: scenario-swarm-rehearsal.yaml Posted 2026-06-28 UTC via adoption_wave13.py (Discussion #11 fix) |
Uh oh!
There was an error while loading. Please reload this page.
Kickoff for RFC-LSS-1.1-composition.md.
Scope: sequential/parallel composition blocks, adapter refs, evaluator product types.
Not in scope: implementation (2027 target).
Please comment with: use cases, breaking changes, and validator implications.
All reactions