Event naming inconsistency

How to fix

1. Use the established event naming convention.
2. Prefer past-tense fact names for domain events when that is the local pattern.
3. Update publisher, handler, and contract names together.

What the rule validates

An event name appears inconsistent with adjacent event names or documented conventions.

Why it matters

Consistent event naming helps teams understand event meaning, ownership, and lifecycle.

Common causes

• Some events are named as commands and others as facts.
• Pluralization or tense varies across modules.
• Renames did not update all references.

Typical violation example

StartUpload, RepositoryUploadedEvent, and upload_finished all describe the same style of event.

Typical compliant example

RepositoryUploaded follows the same noun/verb tense convention as adjacent events.

Related rules

Adjacent categories

Related files/config

• apps/api/src
• packages/contracts/src

Related CLI commands

• archpilot validate
• archpilot validate --ci