Contributions should strengthen the repository's role as a research-and-synthesis project focused on coding-agent runtime behavior. Keep business-domain workflows, product marketing, and implementation-heavy detours out of the core unless they directly clarify runtime semantics.
- Source-backed system reviews.
- Pattern pages grounded in at least one verified implementation and ideally more than one.
- Corrections to factual claims.
- Better diagrams and comparative matrices.
- Narrower, clearer definitions of runtime boundaries.
- Build-from-zero guidance that reflects the current synthesis.
- Prefer primary sources such as source code, docs, issue threads, and design notes.
- Mark confidence explicitly when evidence is partial.
- Separate observed behavior from proposed standardization.
- State when a conclusion is inferred rather than directly documented.
Every system review should end with:
- reusable runtime patterns,
- non-transferable product specifics,
- confidence level,
- open questions.
- Be direct and concrete.
- Favor behavior descriptions over feature marketing.
- Use the shared terminology from research/glossary.md.
- Keep implementation advice narrow and evidence-backed.
- Describe the claim being added or revised.
- Link the sources that justify the change.
- Note whether the change affects the runtime contract, pattern catalog, or corpus status.
- Update the relevant matrix or synthesis page when needed.