RFC Intake: How Aftergraph Proposals Become Changes

[github-actions[bot]]

Use this thread to understand and improve the Aftergraph RFC intake process.

Start a new Ideas discussion with an [RFC] title when a proposal changes public contracts, cross-repository behavior, compatibility, normative semantics, governance, or long-lived primitives.

A strong RFC discussion covers:

• problem and scope,
• evidence,
• prior art and simpler alternatives,
• proposed semantics,
• compatibility and migration,
• authority/security impact,
• economic/control-plane cost,
• verification/conformance plan,
• falsifiers.

The intended lifecycle is:

Discussion -> evidence/prior art -> owner resolved -> RFC/issue -> implementation -> conformance/interoperability -> decision/versioned release.

Full process:
https://github.com/Aftergraph/.github/blob/main/RFC-PROCESS.md

The process should reject unnecessary abstractions as readily as it accepts useful ones.