Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
53 lines (34 loc) · 3.03 KB

CONTRIBUTING.md

File metadata and controls

53 lines (34 loc) · 3.03 KB
Raw

Contributing to Intent-Centric Computing

Status: DESIGN PROPOSAL

This is an early-stage research and design project. There is no code to run, build, or test yet. Contributions at this stage are about ideas, research, critique, and design refinement.

Ways to contribute

  • Open issues: Ask questions, raise challenges, suggest directions, point out gaps.
  • Pull requests: Improve documentation, add research references, refine design proposals.
  • Discussions: Engage with existing issues and proposals. Thoughtful critique is as valuable as new ideas.

Guidelines

  1. Cite sources. Every factual claim about prior art, existing systems, or research findings must link to a primary source (paper, documentation, specification). Opinions and proposals should be clearly marked as such.

  2. Distinguish status. Use status labels to indicate maturity:

    • VISION — aspirational, not yet grounded in specific design
    • RESEARCH — surveying existing work, gathering evidence
    • DESIGN PROPOSAL — concrete proposal open for critique
    • IMPLEMENTATION — ready to build (none exist yet)

  3. Be honest about uncertainty. If something is speculative, say so. If you do not know whether an approach will work, say that too. False confidence is worse than acknowledged gaps.

  4. Respect scope. This project is in research and design phase. Contributions should advance understanding, not jump to implementation. Code will come when the design warrants it.

  5. One idea per issue. Keep discussions focused on a single question or proposal. If an issue grows to cover multiple topics, split it.

  6. Engage constructively. Challenge ideas rigorously. Do not challenge people. Disagreement is productive; dismissiveness is not.

Contribution types welcome

  • Prior-art references (academic papers, existing systems, related projects)
  • Philosophical critique (assumptions, values, tradeoffs)
  • Architectural proposals (how components might interact)
  • Scenario analysis (how the system would handle specific real-world situations)
  • Edge cases (where the design breaks or becomes ambiguous)
  • Accessibility considerations (how the system serves diverse users and needs)

How to propose a design change

  1. Open an issue describing the proposed change.
  2. Explain the rationale: what problem does this solve or what improvement does it offer?
  3. Identify which existing principles or documents are affected.
  4. Allow discussion before submitting a PR. Design changes benefit from community input before they are formalized.

Code of conduct

Be respectful, constructive, and intellectually honest. Assume good faith. Welcome newcomers. A detailed Code of Conduct will be adopted as the community grows.

Licensing and contributions

This project is licensed under Apache-2.0. By submitting a contribution (issue, pull request, or discussion content intended for incorporation), you agree that your contribution is made under the same license terms. A formal DCO or CLA process may be introduced later; for now, submission implies agreement.