Skip to content
PREVIEW - Version 0.2 - Open Submissions Arriving Soon!
Open Agentic ITSM Framework
Esc
↑↓navigate↵open⌘Jpreview
On this page

Contribution Rules

Standards and requirements for all contributions to the Open Agentic ITSM Framework

Every contribution to the Open Agentic ITSM Framework must meet these standards. They are not suggestions. Contributions that do not meet these standards will not be merged.

IP Requirement

Before contributing, read and accept the IP Policy. By submitting a Pull Request or any content to this repository, you confirm that:

  1. The content you are contributing is your original work or is properly attributed to its source.
  2. The content is not subject to any proprietary claim, trade secret protection, or confidentiality obligation.
  3. You are contributing the content freely, without assertion of any proprietary rights over it, under the terms of the Creative Commons Attribution 4.0 International License.
  4. You have the authority to make this contribution and are not contributing content that belongs to your employer or another party without their explicit written permission.

Contributions that incorporate IP-encumbered material, including proprietary vendor methodologies, confidential client information, or content subject to NDA, are not acceptable and will be rejected.

Content Standards

Be evidence-based. Every factual claim must be attributable to a source: published research, vendor documentation, industry analyst findings, or documented deployment experience. Claims without sources will be flagged for verification or removal.

Be vendor-neutral. The framework is not a marketing channel. Content that is promotional toward any vendor, that frames vendor capabilities in comparative or superlative terms without independent evidence, or that reads as a sales document will not be merged. Vendor landscape contributions have specific additional standards described in Section 8 of the framework.

Be independently derived. Do not contribute content that mirrors proprietary frameworks, methodologies, or documentation from other sources. Concepts and observations may be informed by other frameworks and sources; they must be expressed in original language and properly attributed.

Be accurate. Outdated information is a problem in its own right, separate from incompleteness. If you are contributing content about vendor capabilities, market data, or research findings, verify that the information is current at the time of contribution.

Formatting Requirements

All content files must include FrontMatter tags at the top of the file. The minimum required tags are:

---
title: "Page Title"
section: "framework" or "community"
description: "Brief description of page content"
version: "0.2-draft" (or current framework version)
status: "draft" or "stable"
license: "CC BY 4.0"
last_updated: "YYYY-MM-DD"
---

Additional optional tags for domain pages include domain_order, related_domains, and subsection.

Language standards:

  • Professional register: clear, direct, business-oriented. Not academic jargon, not marketing language.
  • No em-dashes. Use a comma, period, or restructure the sentence.
  • No emojis in framework content.
  • Active voice is preferred where it is clear and accurate.
  • No superlatives or promotional framing.
  • Cite sources in author-date format at the end of each page.

Diagrams: Mermaid is the standard for all diagrams. Contributions that include diagrams must use Mermaid syntax. Images are not accepted for diagram content.

What Is Not Acceptable

The following content will not be merged regardless of other qualities:

  • Content that makes factual claims without sources
  • Content that promotes or endorses specific vendors
  • Content sourced from proprietary or confidential documents
  • Content that incorporates IP belonging to any third party without explicit permission
  • Content that contradicts the framework’s guiding principles without providing a substantive argument for revising those principles
  • Content in a language other than English (at this time; multilingual support is a future consideration)
  • Content that does not comply with the IP Policy

Review Process

All Pull Requests are reviewed by the founding author or a designated maintainer. The review evaluates:

  1. IP compliance
  2. Content accuracy and source quality
  3. Vendor neutrality
  4. Formatting compliance
  5. Fit with existing framework content (no duplication, no contradiction without argument)

Reviewers may request changes before merging. Contributors are expected to respond to review feedback within 30 days. Pull Requests with no response within 30 days may be closed.

Merged contributions are acknowledged in the framework’s changelog.

Was this page helpful?