The event schema is the centrepiece of suky. It stores every event your product fires, along with its typed property schema, lifecycle state, and ownership metadata.
Event lifecycle
Each event moves through a governed lifecycle:
| Stage | Description |
|---|---|
| Draft | Initial state. The event is being authored and is not yet ready for review. |
| In Review | Submitted for team review. Reviewers can approve or return it to draft. |
| Approved | Reviewed and approved. Ready to be scheduled for implementation. |
| Planned | Scheduled for implementation in an upcoming sprint or release. |
| In Progress | A developer is actively implementing the event in code. |
| Implemented | Code is written and deployed, awaiting validation against live data. |
| Validated | Confirmed firing correctly in production with the expected schema. |
| Enforced | Live and actively enforced as a production event contract. |
| Deprecated | Marked for removal. Still firing but should no longer be relied upon. |
| Retired | Fully removed from the codebase and no longer expected in data. |
Property types
Supported property types: string, number, boolean, array, object, datetime.
Global properties
Define properties that are automatically attached to every event (e.g. platform, app_version). Managed in Settings → Global Properties.