# Modules with no module source yet. They appear in /modules/index.json with spec: "pending",
# so an agent can still map a customer's request onto them and plan a sequence.
#
# `spec: pending` means: there is no reference vocabulary to start from, so phase 2 is done from
# scratch with the customer — read the modules that DO have specs (their shape is the house
# style), reuse the shared master data they own, and write the customer's ERP_<MODULE>.md the
# same way. Where `reference.packages` is non-empty, working code exists and can be read; where
# it is empty, nothing has been built yet.
#
# A module with modules/<id>/module.yaml is listed from that file instead.
pending:
- id: itsm
name: IT help desk & incidents
domain: it-operations
customer_words: ["support tickets", "help desk", "incidents", "outages"]
replaces: [shared inbox, Zendesk, ServiceNow, Jira Service Management]
first_module_fit: high
depends_on: []
references_master_data: [person]
owns_master_data: [configuration_item]
maturity: tested
reference: { packages: [/code/itsm-suite-app/], build_guide: null } # the old suite post is retired; a build guide follows the spec
start_from: [business-partner]
- id: helpdesk
name: Help desk (small teams)
domain: it-operations
customer_words: ["people email me when something breaks", "track requests", "nothing gets forgotten"]
replaces: [shared inbox, spreadsheets, Zendesk]
first_module_fit: high
depends_on: []
references_master_data: [person]
owns_master_data: []
maturity: planned
reference: { packages: [], build_guide: null }
start_from: [crm]
note: "the ITSM module is built for large IT departments (change boards, major-incident rooms); a small team wants tickets, categories and a search"