Active Tags 1.0 Is Production-Worthy — And It Powers the M7 Front Door

By The Grim Scalper · Tags: lab , active-tags , m7.js , v1.0 , Frontend , Production

Status: Production track (v1.0)
Repo: github.com/linearblade/m7-js-lib-app-active-tags
Product page: www.m7.org/tools/js/activetags

Active Tags 1.0 is not a demo library. It is the production workflow runtime M7 uses on its own web surfaces — SPA navigation, session-aware shells, forms, and member tooling — and it is the recommended path for teams who need medium-to-high complexity browser behavior without adopting a platform-owning UI framework.

What it is

Active Tags is a compile-first workflow orchestration runtime for DOM components.

You declare semantic roots in markup (data-activetag, at-name, config pointers). The runtime:

  1. Discovers roots and compiles per-job schema
  2. Registers events, intervals, observers, and related controllers as enqueue sources only
  3. Executes work as tickets through Engine → Tick → VM
  4. Normalizes stage outcomes (ok, wait, error, complete) with explicit run/error pipelines
  5. Exposes hooks and traces so behavior stays operable under load and churn

Philosophy in one line:

Declare behavior in DOM/config. Execute deterministically in one runtime.

What it is good for

  • SPA-like flows on mixed or legacy stacks (including PHP-hosted pages)
  • Multi-step UI workflows: collect → validate → request → patch → error dump
  • Replacing handler spaghetti with staged pipelines and builtins (form, http, dom, buffer, target, error, and related surfaces)
  • Teams that need inspectable UI state governance more than framework fashion

What ships with 1.0

Piece Role
Standalone bundle Active Tags + m7.js + required primitive installers in one artifact
m7.js Normalization-first utility core and service registry
Builtins Form, HTTP, DOM/target/buffer, error, confirm, popstate helpers
DSL v1.0 Compact pipeline syntax with expression injection
Docs + contracts Architecture overview, API contracts, tutorial example, LLM handbook

Recommended integration path: ship the versioned standalone minified bundle, install({ conf }), start(), enable DOM observe / events / intervals as needed.

Production posture

On M7 properties, Active Tags is already in the critical path for session shells, SPA link handling, cold-load recovery, and form flows. That is the bar we mean by production-worthy: real product surfaces, not brochure samples.

You still own domain design and backend contracts. Active Tags solves the UI state-governance and workflow layer — not your entire architecture.

Try it

  • Product: Active Tags
  • Quick start and tutorial: see the repository docs/ and examples/tutorial/
  • Companion library: m7-js-lib

Licensing follows MTL-10 (free for teams ≤10 users of the software; commercial terms above that or for resale/SaaS redistribution). Contact legal@m7.org for commercial licensing.

— M7 Lab