Proposals

OpenArmature evolves through numbered RFC-style proposals. Each proposal targets a capability spec and moves through a Draft → Accepted lifecycle. Once Accepted, a proposal's text is immutable — further changes happen via new proposals that supersede the prior. See Governance for the full lifecycle and the proposal template.

#	Title	Capability	Status
0001	Foundation	graph-engine	Accepted
0002	Subgraph explicit I/O mapping	graph-engine	Accepted
0003	Node-boundary observer hooks	graph-engine	Accepted
0004	Middleware	pipeline-utilities	Accepted
0005	Parallel fan-out	pipeline-utilities	Accepted
0006	Core abstraction + OpenAI wire mapping	llm-provider	Accepted
0007	OpenTelemetry span mapping	observability	Accepted
0008	Checkpointing	pipeline-utilities	Accepted
0009	Per-instance fan-out resume	pipeline-utilities	Accepted
0010	Bounded drain — configurable timeout	graph-engine	Accepted
0011	Parallel branches	pipeline-utilities	Accepted
0012	Completed event fires after edge evaluation	graph-engine	Accepted
0013	Fan-out config on node event	graph-engine	Accepted
0014	State migration hooks for checkpoints	pipeline-utilities	Accepted
0015	Image content blocks for user messages	llm-provider	Accepted
0016	Structured output	llm-provider	Accepted
0017	Prompt management core	prompt-management	Accepted
0018	State migration chain ambiguity	pipeline-utilities	Accepted
0019	Multi-provider wire-format extension	llm-provider	Accepted
0020	Sessions capability	sessions	Draft
0021	Graph suspension and external-signal resume	suspension	Draft
0022	Harness contract	harness	Draft
0023	Canonical state reducers	graph-engine	Draft
0024	LLM span payload + GenAI semconv	observability	Accepted
0025	LLM provider tool_choice parameter	llm-provider	Accepted
0026	§8.X wire-format mapping subsection template	llm-provider	Accepted

Click any column header to sort.