Database DDL

Artekis uses nine tables, created by your DBA from the vendor's script and never altered by the module:

Table	Holds
artekis_schema	the schema version (exactly 1 for 1.x)
artekis_owner	the database-ownership lease (one row)
artekis_run	every run: playbook, collection, trigger, state, times, the candidates offered, the cuts, the KPI document, tool calls, the Ask answer, the actor
artekis_finding	findings, one row per fingerprint and lifecycle
artekis_evidence	each finding's evidence items (capped at 64 KB per finding)
artekis_feedback	verdicts and Ask thumbs
artekis_egress	every model call, email and MQTT send with its outcome and what was sent, as the policy keeps it
artekis_document	uploaded documents (text only)
artekis_chunk	their search chunks

The scripts ship beside this manual as ddl/mssql/v1.sql (SQL Server), ddl/mysql/v1.sql (MariaDB and MySQL) and ddl/postgres/v1.sql (PostgreSQL), and the installed module serves the one for its configured connection at GET /data/artekis/ddl. Apply the script in the default schema of the gateway connection's database; the Status page confirms the tables and the version. Findings and feedback are never deleted by the module; size the database for runs and egress at your retention.