Architecture RFCs

Architecture RFCs are public design proposals. Each RFC should name its status, decision boundary, non-goals, smallest useful implementation slice, and validation criteria. An RFC may describe future work; current behavior is defined by the implementation and stable reference contracts.

Active Drafts

• Agent IM, LoopX, and OpenViking collaboration v0: separate runtime delivery, durable control state, and scoped context while preserving direct agent-to-LoopX interaction.

RFCs must not contain internal conversations, private links, local filesystem paths, credentials, raw transcripts, or non-public organizational context.