📌 For agent integration rules, see the Agent Database Creation Convention — the technical spec for how AI agents interact with this ticket system.

Naming Convention Summary

Format: <CODE>-<TYPE>-<NNN>

For tickets, the full serialized ID looks like: {PREFIX}-OPS-001, CLIENT-014

When a pipeline client converts to an active engagement, they get an engagement type suffix. So if a client signs for advisory work, their first ticket would be CLIENT-ADV-001.

For internal work, the company prefix groups everything together, and the second segment distinguishes the workstream — so you can filter all internal tickets by {PREFIX}-* or drill into {PREFIX}-TKT-* for just ticket system work.

🏢 Internal ({COMPANY_NAME})

Populated during onboarding. The agent will generate codes like {PREFIX}-OPS, {PREFIX}-WEB, etc.

📁 Client Engagements

Populated when clients sign engagements. Each gets a short code + engagement type suffix.

🚀 Initiatives / Pipeline

Populated as strategic initiatives are created.

🗂️ Client Pipeline

Populated as new leads and prospects are added to the Client Database.

➕ How to Add a New Project Code

When a new client signs, a new engagement starts, or a new internal project is created, follow these steps:

1. Choose the code format:
   • Internal projects: {PREFIX}-<SHORTNAME> (e.g., {PREFIX}-CRM)
   • New client (no engagement yet): <CLIENT_ABBREV> (e.g., ACME)
   • Client engagement: <CLIENT_ABBREV>-<ENGAGEMENT_TYPE> (e.g., ACME-MIG for migration, ACME-ADV for advisory)