What really works today
This page is measured, not written: scripts/generate-feature-status.py runs every example and counts what parses and what executes, and the site is regenerated from its result. Where it disagrees with the rest of the documentation, this page is the one that ran.
The promise — what is Core, AI, Experimental or Laboratory — is Support tiers.
39 registered q: tags · 30 executors · 136 examples executed · live AI: yes.
Columns: tier comes from quantum/core/tiers.py. examples: files in examples/ and components/ that use the tag. parses: at least one of them passes the parser. executes: of the executable examples, how many quantum run executes without error, in a temporary copy of the repository (only Core and AI; interactive targets and experimental tags are not executed). tests and docs: files that mention the tag.
Core (15 tags)
| Tag | Examples | Parses | Executes | Tests | Docs |
|---|---|---|---|---|---|
q:action | 47 | yes | 19/19 (28 not executed) | 37 | 52 |
q:data | 10 | yes | 7/7 (3 not executed) | 9 | 23 |
q:file | 4 | yes | 4/4 | 6 | 11 |
q:flash | 7 | yes | 6/6 (1 not executed) | 5 | 16 |
q:function | 31 | yes | 16/16 (15 not executed) | 26 | 45 |
q:if | 80 | yes | 30/30 (50 not executed) | 28 | 62 |
q:import | 2 | yes | 1/1 (1 not executed) | 6 | 16 |
q:invoke | 8 | yes | 4/4 (4 not executed) | 15 | 19 |
q:loop | 57 | yes | 31/31 (26 not executed) | 22 | 55 |
q:mail | 12 | yes | 5/5 (7 not executed) | 4 | 19 |
q:query | 48 | yes | 12/12 (36 not executed) | 32 | 59 |
q:redirect | 36 | yes | 11/11 (25 not executed) | 23 | 40 |
q:set | 129 | yes | 84/84 (45 not executed) | 60 | 62 |
q:slot | 3 | yes | — (3 not executed) | 3 | 12 |
q:transaction | 5 | yes | 3/3 (2 not executed) | 5 | 24 |
AI (3 tags)
| Tag | Examples | Parses | Executes | Tests | Docs |
|---|---|---|---|---|---|
q:agent | 4 | yes | 2/2 (2 not executed) | 18 | 43 |
q:knowledge | 6 | yes | — (6 not executed) | 13 | 41 |
q:llm | 9 | yes | — (9 not executed) | 16 | 44 |
Experimental (21 tags)
| Tag | Examples | Parses | Tests | Docs |
|---|---|---|---|---|
q:class | 2 | yes | 2 | 2 |
q:decorator | 1 | yes | 1 | 6 |
q:dispatchEvent | 0 | — no example | 0 | 6 |
q:dump | 6 | yes | 1 | 6 |
q:job | 2 | yes | 10 | 10 |
q:log | 13 | yes | 4 | 7 |
q:message | 10 | yes | 8 | 9 |
q:messageAck | 2 | yes | 2 | 6 |
q:messageNack | 2 | yes | 2 | 6 |
q:pyclass | 0 | — no example | 1 | 7 |
q:pydecorator | 0 | — no example | 0 | 6 |
q:pyimport | 2 | yes | 2 | 6 |
q:python | 2 | yes | 8 | 10 |
q:queue | 3 | yes | 3 | 6 |
q:schedule | 2 | yes | 5 | 12 |
q:subscribe | 3 | yes | 3 | 6 |
q:team | 1 | yes | 6 | 13 |
q:thread | 2 | yes | 4 | 7 |
q:websocket | 1 | yes | 5 | 10 |
q:websocket-close | 1 | yes | 1 | 6 |
q:websocket-send | 1 | yes | 1 | 6 |
Core/AI examples that do not execute
None.
Not executed, and why
- 61 file(s): Cookbook recipe: runs as its app, in tests/docs/test_cookbook.py
- 25 file(s): uses an experimental tag
- 6 file(s): Laboratory (game)
- 4 file(s): component requires parameters
- 3 file(s): interactive target (terminal)
- 1 file(s): interactive target (ui)
Gaps this measurement exposes
- 3 tags without any example:
q:dispatchEvent,q:pyclass,q:pydecorator. - 0 tags whose examples do not parse: none.
- 0 Core/AI examples that do not execute (table above).