Experimental tags

Tags outside the Core and the AI.

Experimental

These tags exist and run, with no stability promise: they may change or go away in any release, and the SPEC does not specify them (SUPPORT_TIERS.md).

q:dispatchEvent

Publishes an event to the event bus.

Attribute	Type	Required	Default	Values	Description
event	string	yes			Event name
data	expression				Event payload
queue	string				Target queue
exchange	string				Exchange name
routingKey	string				Routing key
priority	enum		normal	low, normal, high	Event priority
delay	string				Delay before delivery (e.g., '5s')
ttl	string				Time-to-live (e.g., '60s')

<q:dispatchEvent event="user.created" data="{userData}" />

q:dump

Dumps a variable's contents for debugging.

Attribute	Type	Required	Default	Values	Description
var	string	yes			Variable to dump
label	string				Label for the dump output
format	enum		auto	auto, json, table, tree	Output format

<q:dump var="users" />

<q:dump var="config" label="Configuration" format="json" />

q:log

Logs a message for debugging or monitoring.

Attribute	Type	Required	Default	Values	Description
message	expression				Log message (supports databinding)
level	enum		info	debug, info, warn, error	Log level
var	string				Variable to dump

<q:log message="Processing user {userId}" level="debug" />

<q:log var="userData" level="info" />

q:message

A chat message of a q:llm

Attribute	Type	Required	Default	Values	Description
role	enum		user	system, user, assistant	Who says it

Without a schema

The editor schema does not describe these yet: q:class, q:decorator, q:job, q:messageAck, q:messageNack, q:pyclass, q:pydecorator, q:pyimport, q:python, q:queue, q:schedule, q:subscribe, q:team, q:thread, q:websocket, q:websocket-close, q:websocket-send.

Application types

q:application type= — Laboratory: game; Experimental: terminal, ui (APP-1). A web application is pages in components/.

:::