---
language:
- en
- es
license: mit
task_categories:
- text-generation
tags:
- totaljs
- javascript
- code
---

# Totem Total.js reference corpus

This dataset contains pinned, source-backed text for retrieval while building Total.js applications. It is **not** an instruction-tuning dataset and does not establish that a model has learned these APIs.

Each JSONL record has `id`, repository, Git revision, relative path, layer, source role, license, SHA-256 and source text. `manifest.json` records repository origins, revisions, license evidence hashes, counts and exclusions. The `LICENSES/` folder preserves source notices and license evidence. Files were selected from Git-tracked paths; generated bundles, minified files, tests, binary files, large files and suspicious secrets were excluded.

The snapshot includes Total.js 5, jComponent v20, compatible Componentator components, conventions, CMS and widgets, Flow v11, the active `components/*.html` FlowStream components, LessCode, OpenPlatform, Todomator, three querybuilder packages and the MIT-licensed Totem application from `totaljs-es`. Totem is the only community application included and has the role `community-example`: it teaches how a substantial Total.js 5 application is assembled, but it is not canonical framework behavior. Generated bundles, runtime data, tests and sensitive files are excluded. The corpus also excludes Flowee, the Total.js 4 Code app, archived FlowStream components and the FlowStream components test harness. The HTML components are source examples; their behavior in a particular Flow release must still be verified. Todomator declares MIT in `package.json` but lacks a standalone license file; the [Total.js platform license](https://www.totaljs.com/license/) also describes its apps as MIT. The Todomator package metadata is preserved in `LICENSES/`. `components` uses the repository MIT license; its component metadata links to the same platform license, which also describes UI components as MIT. Check source revisions and current docs before use.

Do not randomly split individual files into training and test sets: related files from the same feature can leak answers. Build and validate task-level examples separately, holding out whole features or applications. Do not put tokens, user data or private application content into this dataset.

The public `totaljs/actions` repository contributes guides and examples, not private action implementations. `aicontext` and `guidelines` are listed for passage-level review in the manifest but their raw text is excluded: some guidance conflicts with current code or with itself. Older MySQL and SQL Server adapter README examples are also excluded because their package names or examples are stale; their implementation and package metadata remain. Where instructions conflict, use the current framework source and project-specific conventions; verify the behavior in the target app. The source repositories and their exact revisions are listed in `manifest.json`. This snapshot will age as the projects change.