Animated execution trace overlaid on the creator-platform system sigil — open in a browser to watch it play
Each span is colored by operational category (SQL, cache, storage, transcode, mail, auth…) and arrives at its node in temporal order. The timeline below the sigil shows relative span durations per depth layer.
Example programs showcasing Clavicula Turing language features and standard library usage.
Status note:
- This examples catalog is current through
FASE 39 completed. - Some filenames keep historical phase tags to preserve traceability.
- SVG artifacts (sigils and trace renders) are described in the Visual Gallery section below.
Simple "Hello World" program demonstrating basic syntax.
- INCIPIT/EXPLICIT grimoire structure
- RITUALE definition
- OBSECRO scribe statement
cct hello.cct
./helloComprehensive language tour demonstrating:
- ORDO (enums) and SIGILLUM (structs)
- SERIES (arrays) and SPECULUM (pointers)
- Memory management (pete/libera/DIMITTE)
- Control flow (SI/ALITER, DUM, DONEC, REPETE)
- Exception handling (TEMPTA/CAPE/SEMPER, IACE)
- Function calls (CONIURA)
cct ars_magna_showcase.cct
./ars_magna_showcaseOption and Result types (introduced in FASE 12C, still supported):
- Option<T> for nullable values (Some/None)
- Result<T, E> for error handling (Ok/Err)
- Safe error patterns
cct option_result.cct
./option_resultDynamic collections basics:
- Creating collections with fluxus_init
- Adding elements with fluxus_push
- Accessing with fluxus_get
- Memory cleanup with fluxus_free
cct fluxus_demo.cct
./fluxus_demoFunctional operations:
- Map: transform collections
- Filter: select elements
- Fold: aggregate values
- Chaining operations
cct collection_ops_12d2.cct
./collection_ops_12d2Iterator patterns with ITERUM:
- Iterating FLUXUS collections
- Iterating SERIES arrays
- Using with map operations
cct iterators.cct
./iteratorsCode with linter warnings:
- Unused variables
- Unreachable code
cct lint lint_showcase_before_12e2.cctClean version after fixing warnings.
cct lint lint_showcase_after_12e2.cctStable modular Sigilo showcase with a composed system view and a realistic media upload trace.
- route-composed system sigil already present
- animated operational trace over the composed
.system.sigil - explicit
--sigil-view routesoption to project the same trace on pure route view - interactive
--stepSVG with scrubber
./cct --sigilo-only \
--sigilo-style routes \
--sigilo-out examples/sigilo_web_system_35/routes_view \
examples/sigilo_web_system_35/main.cct
./cct sigilo trace render \
--animated \
--trace examples/sigilo_web_system_35/media_upload_pipeline_39.ctrace \
--sigil examples/sigilo_web_system_35/routes_view.system.sigil \
--out examples/sigilo_web_system_35/media_upload_pipeline_39_animated.svg
./cct sigilo trace render \
--animated \
--trace examples/sigilo_web_system_35/media_upload_pipeline_39.ctrace \
--sigil examples/sigilo_web_system_35/routes_view.system.sigil \
--sigil-view routes \
--out examples/sigilo_web_system_35/media_upload_pipeline_39_routes_animated.svgLarger creator-platform Sigilo showcase with studio, auth, media, billing, moderation, analytics, notifications, admin, webhooks, and internal task routes.
- denser composed system sigil than
sigilo_web_system_35 - deeper publish trace crossing several modules
- explicit route-only trace rendering via
--sigil-view routes - animated and
--steprenders over the real composed.system.sigil
./cct --sigilo-only \
--sigilo-style routes \
--sigilo-out examples/sigilo_creator_platform_39/routes_view \
examples/sigilo_creator_platform_39/main.cct
./cct sigilo trace render \
--animated \
--trace examples/sigilo_creator_platform_39/creator_release_pipeline_39.ctrace \
--sigil examples/sigilo_creator_platform_39/routes_view.system.sigil \
--out examples/sigilo_creator_platform_39/creator_release_pipeline_39_animated.svg
./cct sigilo trace render \
--animated \
--trace examples/sigilo_creator_platform_39/creator_release_pipeline_39.ctrace \
--sigil examples/sigilo_creator_platform_39/routes_view.system.sigil \
--sigil-view routes \
--out examples/sigilo_creator_platform_39/creator_release_pipeline_39_routes_animated.svgEvery time the compiler runs with sigilo mode active, it emits a .svg alongside the binary. Open any of these directly in a browser with file:// — no server, no extension, no JavaScript framework. The animated ones use pure CSS @keyframes; they just play.
These are the richest artifacts in the repo. They overlay a real .ctrace execution trace onto the route sigil, coloring each span by operational category and animating the signal flow through the system.
A creator-platform publish pipeline — auth check, SQL lookups, cache hits, storage upload, transcode queue, email confirmation, task dispatch — playing out as a CSS animation over the full composed system sigil. Each span arrives at its node in temporal order: green for SQL, orange for cache, violet for storage, pink for transcode, blue for handlers. Below the sigil, a synchronized timeline lane shows the relative duration of every span at its depth. Open it, watch it once, then hover any node for the data-category tooltip. Slow spans glow with a drop-shadow.
sigilo_creator_platform_39/creator_release_pipeline_39_animated.svg — 1420×1344 px · open in browser to watch the animation
open examples/sigilo_creator_platform_39/creator_release_pipeline_39_animated.svgThe same trace projected onto the routes-only view. The system structure compresses into a constellation of route nodes; spans animate along the arcs between them. Cleaner than the full system view — good for focusing on routing topology.
open examples/sigilo_creator_platform_39/creator_release_pipeline_39_routes_animated.svgSame canvas as the animated version, but with an interactive scrubber rail at the bottom. Each dot on the rail is one span in execution order. Click a dot or drag the knob to advance the trace one span at a time — nodes light up as active, completed spans dim, timeline lanes update in sync. Ideal when you want to read the trace carefully rather than watch it play.
sigilo_creator_platform_39/creator_release_pipeline_39_step.svg — scrubber rail at bottom · drag the knob
open examples/sigilo_creator_platform_39/creator_release_pipeline_39_step.svgThe smaller sigilo_web_system_35 system: web server + upload + processing modules. Less dense than the creator platform, making it easier to read each individual span category as it arrives. A good starting point before moving to the creator platform trace.
open examples/sigilo_web_system_35/media_upload_pipeline_39_animated.svgThe upload flow on the routes view: request → auth → upload → transcode → callback. Category colors on the arcs tell the whole story in one compact frame.
open examples/sigilo_web_system_35/media_upload_pipeline_39_routes_animated.svgStep scrubber on the media upload pipeline. A slower system than the creator platform, so stepping through it is a good introduction to how the step UI feels before tackling the denser trace.
open examples/sigilo_web_system_35/media_upload_pipeline_39_step.svgThe static structural view — the topology of the program before any trace is overlaid.
The base canvas for all the animated traces above. Ten module groups (studio, auth, media, billing, moderation, analytics, notifications, admin, webhooks, internal tasks) arranged as a constellation around the core. Each arc is a declared route; the density here is what makes the animated traces look so complex.
open examples/sigilo_creator_platform_39/routes_view.svgTwo complementary views of the same system. The routes sigil (left) shows the pure route topology; the system view (right) is the composed multi-module sigil — a multi-ring structure where each ring is a module in the closure, with cross-module dependencies as arcs between rings.
open examples/sigilo_web_system_35/routes_view.svg
open examples/sigilo_web_system_35/system_view.svgThe largest pure-topology sigil in the repo — 1208×1080 px, 508 lines. The layout algorithm places routes radially around a common core, producing a star-map appearance. No trace overlay; just the structure at rest. A good reference for what a production-scale route set looks like in sigil form.
open examples/sigilo_rotas_constelacao_35.svg591 lines — the most detailed standard sigil in the examples. ars_magna_showcase.cct exercises nearly every language surface: ORDO, SIGILLUM, SERIES, SPECULUM, exception handling, all control flow forms. The resulting sigil is correspondingly rich, with many distinct node types visible in the ring structure.
open examples/ars_magna_showcase.svgThe composed sigil of the complete Bibliotheca Canonica as it stood at FASE 11H — plus seven individual module sigils (__mod_001 through __mod_007). The __mod_001 file alone is 1396 lines, the densest module sigil in the repo. Together they show the full stdlib decomposed module by module.
open examples/tmp_sig_11h_complete.svg
open examples/tmp_sig_11h_complete.__mod_001.svgThe first sigils generated with the full multi-ring omniversal layout. The variant uses a slightly different arc-routing algorithm; comparing them side by side illustrates how layout parameters affect the output.
open examples/fase13_omniversal_13m.svg
open examples/fase13_omniversal_13m_variant.svgOne of the richer single-module sigils: the log analyzer uses cct/fs, cct/io, cct/verbum, cct/fmt, and cct/parse, so the dependency arc structure is noticeably busier than a simple example. 349 lines.
Each one is the structural fingerprint of a real example program. Smaller and more readable than the system sigils — good for understanding what a sigil looks like for a specific kind of program.
option_result.svg (311 lines · branching Some/None, Ok/Err paths) and hello.svg (109 lines · the simplest possible sigil)
cadastro_sqlite_app (106 lines · config → db → main) and phase30_data_app (125 lines · JSON + SQLite + HTTP)
http_simple_server_20f2.svg (minimal arc · single-request server) and config_sqlite_app_20f2.svg (INI + SQLite arc)
The cadastro_sqlite_app/tests/ directory contains sigils for the test files themselves — the sigilo system captures test modules as first-class artifacts, not just production code.
For most examples you will also find a .system.svg companion alongside the main .svg. The .system.svg is the composed multi-module view — it includes the full transitive closure of imported modules, rendered as concentric rings. The plain .svg shows only the primary module. For small programs they look similar; for complex apps like cadastro_sqlite_app or sigilo_web_system_35, the difference is dramatic.
Single-request HTTP server returning JSON on 127.0.0.1:8091.
cct/httprequest accept/reply flowcct/jsonbody construction- explicit
Content-Typeheader
./cct examples/http_simple_server_20f2.cct
./examples/http_simple_server_20f2HTTP client consuming JSON from the local server.
http_get_jsonjson_get_key/json_expect_*- local loopback workflow
Run after starting http_simple_server_20f2.cct in another terminal.
./cct examples/http_json_client_20f2.cct
./examples/http_json_client_20f2Configuration-driven SQLite mini app.
- INI parsing with
cct/config - local persistence with
cct/db_sqlite - explicit project-local file paths under
examples/.tmp
./cct examples/config_sqlite_app_20f2.cct
./examples/config_sqlite_app_20f2UDP loopback demo using only project-local host networking.
cct/nethigh-level UDP helperscct/sockettimeout controlcct/optionunwrap flow for datagrams
./cct examples/udp_loopback_demo_20f2.cct
./examples/udp_loopback_demo_20f2# Compile
cct <example.cct>
# Run the compiled executable
./<example>
# Format code
cct fmt <example.cct>
# Lint code
cct lint <example.cct>- hello.cct - Start here
- fluxus_demo.cct - Collections basics
- iterators.cct - Iteration patterns
- option_result.cct - Error handling
- collection_ops_12d2.cct - Functional programming
- ars_magna_showcase.cct - Complete tour
- http_simple_server_20f2.cct + http_json_client_20f2.cct - Local application protocol flow
- config_sqlite_app_20f2.cct - Config + persistence integration
- udp_loopback_demo_20f2.cct - Host networking basics
- lint_showcase_*.cct - Code quality
- Language spec:
docs/spec.md - Standard library:
docs/bibliotheca_canonica.md - Architecture:
docs/architecture.md - Current phase status and next-step planning:
docs/roadmap.md - Historical release packages:
docs/release/