# Contributing to ABCS

Contributions to the Autonomous Business Capability Specification are welcome.

Before proposing a domain, capability, Business Object or field, verify that it expresses enduring **business meaning**, not implementation technology.

Use this scope test:

> Would this still make business sense if humans performed the work manually and all implementation technology disappeared?

A proposal should identify:

- the owning business domain
- the canonical business meaning
- proposed stable identifier(s)
- related Business Objects and business relationships
- business preconditions/effects when relevant
- compatibility impact
- provenance/source material

Do not derive canonical definitions from proprietary or licensing-ambiguous frameworks. ABCS follows a GREEN-only provenance policy.

Open an issue or pull request in this repository with the rationale and examples. Draft 0.x definitions may evolve as implementation experience grows.