Guidelines
Research Standards
Grounding All research must be grounded in one or more of the following: mathematical proofs or formal models, empirical evidence and reproducible results, rigorous engineering analysis, or clear philosophical argument from first principles.
Scope Research should address questions of lasting relevance to systems architecture and design. We favor depth over breadth, and timeless insights over timely commentary.
Originality Contributions should advance the field — not simply summarize existing work. Synthesis across domains is valued. Derivative or purely review-based work is acceptable when it makes a genuinely novel contribution to understanding.
Research Cycle Format
ObjectSpread organizes work into research cycles — typically 8 months per topic. Each cycle follows a structured process:
Topic Selection (Month 1) — The community proposes and votes on the research focus for the cycle.
Literature Review (Months 1–2) — Participants survey existing work and identify open questions.
Active Research (Months 2–6) — Independent and collaborative research, with regular check-ins and feedback from mentors.
Publication & Review (Months 6–8) — Papers and artifacts are submitted for peer review within the community before external publication.
You are welcome to participate in any phase of a cycle, regardless of when you join.
Publication Standards
Research Papers Papers should be clearly structured: introduction, problem statement, methodology, findings, and conclusion. All claims must be supported. Where possible, include worked examples or case studies that ground abstract arguments in concrete systems.
Code & Prototypes Code contributions should demonstrate design principles, not just implement solutions. Include documentation that explains why the design decisions were made — not just what the code does.
Writing Style Write to be understood by an intelligent generalist, not only by domain specialists. Avoid unnecessary jargon. If a concept requires technical vocabulary, define it on first use.
Community Standards
Peer Review We practice constructive, blameless peer review. Feedback should focus on the work, not the person. Reviewers are expected to offer specific, actionable suggestions — not just verdicts.
Mentorship Mentors commit to timely and substantive feedback. Researchers commit to engaging with that feedback in good faith. The goal is growth, not gatekeeping.
Attribution Cite your sources. Acknowledge collaborators. When building on community work, reference it clearly. We operate on the assumption of good faith — violations of attribution norms are taken seriously.
Participation Active participation is valued. Passive lurking is understandable but limited in value. We encourage everyone to contribute — even small comments, questions, or connections between ideas are meaningful.
Eligibility
ObjectSpread is open to anyone with a genuine interest in systems architecture and design philosophy. There are no credential requirements. We welcome undergraduates, graduate students, independent researchers, and experienced practitioners equally.
What we ask is that you bring intellectual rigor, good faith, and a commitment to the community’s long-term work.
Questions?
If you have questions about research standards, the cycle process, or community participation, post in the community or reach out to an active mentor. We’re here to help you do your best work.