23 lines
1.3 KiB
Markdown
23 lines
1.3 KiB
Markdown
# platform/model
|
|
|
|
Database models live here and are the source of truth for table structure. Migrations must reference these models or be kept in sync with them.
|
|
|
|
Required model groups:
|
|
|
|
- users and roles.
|
|
- game management plugins and installed plugin versions.
|
|
- server instances and config versions.
|
|
- AI providers and secret references.
|
|
- run endpoints and capabilities.
|
|
- jobs and job events.
|
|
- artifacts and chunks.
|
|
- log streams and ingestion cursors.
|
|
- operational events.
|
|
- server-bound plugin lifecycle installations and linked jobs.
|
|
- AI config execution metadata is carried by durable jobs; retired recommendation records are no longer part of the active model or snapshot schema.
|
|
|
|
Every implemented database model must include field comments, JSON/database tags, and an explicit table name function or equivalent mapping in the chosen stack.
|
|
# Durable Client Manager persistence
|
|
|
|
File and MySQL stores persist the Client Manager installation aggregate, component sessions, registration nonce fences, and lifecycle metadata. Session tokens are stored only as hashes; nonce and heartbeat sequence checks are bounded and restart-safe. Reset, ownership/endpoint reassignment, update activation, rollback, revoke, and uninstall fence or expire component sessions without deleting distribution history.
|