Domain model
Both clients should use the same domain vocabulary. This page describes concepts, not implemented database tables or API fields.
Incident
Section titled “Incident”An incident is a report of suspected digital ghost activity affecting infrastructure. It provides the context for investigation and progress tracking.
The eventual model needs to represent what was reported, its progress, and its resolution. Identifiers, required fields, timestamps, and allowed status values have not been defined.
Reporter
Section titled “Reporter”A reporter submits a sighting and follows its resolution. The project has not yet established whether reporters have accounts, use a shared demo identity, or submit through another mechanism.
Operative
Section titled “Operative”An operative is a fictional member of the response team. Operatives have stored profiles and backstories. Moxie “Hotfix” Mallow is the selected first playable demo operative.
Character roles such as field responder or supervisor are story details. They do not establish application permissions. The identity and authorization model still needs to be designed.
Assignment and progress
Section titled “Assignment and progress”The proposed workflow associates an incident with the operative handling it and records progress toward resolution. Assignment rules, status transitions, and any history or diagnostic notes remain design decisions.
Core should enforce the agreed rules, while each client presents them in its own interface. See the Core overview for the initial milestone and in-memory H2 data lifecycle.