Files
nibiru-framework.com/application/settings/config/database/203-ai_message.sql
stephan 48c839d927 Initial public push: docs cosmos v4 + AI module + framework groundwork
This is the snapshot the production landing site (nibiru-framework.com) is
deployed from. Brings together the recent splash + docs migration to the v4
"Cosmos" design system, the new in-framework AI module, and the framework
groundwork that backs the framework-reference extraction.

What lands:
- docs/: Astro + Starlight site with the v4 dark cosmic palette, GalaxyHero
  canvas constellation, Mission Control chat (wired to /api/oracle →
  api.neuronetz.ai via providers.mjs Ollama), 5-panel MMVC stage
  (Model · AI · Module · Controller · View), translated EN/DE/JA/ES/FR
  content, PWA + sitemap + llms.txt + Umami analytics.
- docs/design-system/: canonical mockup bundle (source/index-v2.html for
  splash, source/docs-system.html + preview/ for docs, SPEC.md, tokens).
- docs/scripts/extraction/framework-reference-v2.md: deep framework
  reference (~1.6k lines, file:line citations, every public factory and
  idiom — basis for the LoRA training corpus.
- application/module/ai/: AI module with chat / embed / RAG / agent
  plugins, plus pdoQuery / httpGet / fileRead tools and Modelfile +
  smoke-test in training/.
- application/module/users/: user / ACL / form-factory traits used as the
  reference plugin pattern for the framework docs.
- application/settings/config/database/: schema + seed migrations
  including the AI module tables (200–203).
- Form factory + autogenerator changes the framework-reference-v2 covers.

Production secrets stay out: docs/.env, settings.production.ini and
ai.production.ini are all gitignored (.example files are in tree).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-08 15:22:18 +02:00

24 lines
1.2 KiB
SQL

-- =============================================================================
-- ai_message
--
-- One row per turn in an ai_conversation. Role is one of: system, user,
-- assistant, tool. token_count is best-effort (filled in by the plugin
-- when the model returns usage info; 0 otherwise).
-- =============================================================================
CREATE TABLE IF NOT EXISTS ai_message (
ai_message_id INT(11) NOT NULL AUTO_INCREMENT,
ai_message_conversation_id INT(11) NOT NULL,
ai_message_role ENUM('system','user','assistant','tool') NOT NULL,
ai_message_content MEDIUMTEXT NOT NULL,
ai_message_tool_name VARCHAR(64) NULL,
ai_message_token_count INT(11) NOT NULL DEFAULT 0,
ai_message_created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (ai_message_id),
KEY ai_message_conversation_idx (ai_message_conversation_id),
CONSTRAINT ai_message_conversation_fk
FOREIGN KEY (ai_message_conversation_id)
REFERENCES ai_conversation (ai_conversation_id)
ON DELETE CASCADE
) ENGINE = InnoDB DEFAULT CHARSET = utf8mb4 COLLATE = utf8mb4_unicode_ci;