Open source — the building blocks my platform runs on.

CKEditor 5 plugin for the TYPO3 backend that syncs the RTE live with other editors via Yjs CRDT. Connects to the Hocuspocus server. Early development.

Presence and awareness layer on top of collab-core — live cursors and avatar pills in the TYPO3 backend via SSE stream, deterministic colour coding per editor. Early development.

Base layer of the Moselwal Collab Suite — JWT auth, Yjs document persistence, presence tracking and the REST API for real-time co-editing in the TYPO3 backend. Early development (v0.1.x).

Target side of the distribution line — receives signed snapshots, validates the signature, maps UUIDv7 onto the local ID space. Coming soon.

TYPO3-to-TYPO3 content distribution — source side. Pushes signed DAG snapshots from workspace publish to n downstream targets, with Ed25519 signatures and UUIDv7 references.

Context-aware conversational agent with a RAG pipeline for TYPO3 content. Access-class routing (Public / Partner / Internal / Admin), MCP tool integration, embeddable chat widget.

Quality gates and compliance tracking for AI-generated content: AI-readiness score, brand voice consistency, freshness analysis, audit trail — with a backend dashboard.

Multi-step AI workflows as declarative YAML — with blocking/resume, expression resolution, swappable steps, and pluggable notifiers. The engine for everything that doesn't fit into a single prompt.

Ed25519 signatures for content, cryptographically verifiable via /.well-known/provenance-keys. Audit-trail logging and EU AI Act preparation.

Multichannel distribution with Schema.org enrichment. Transform content automatically for web, AI agents, voice, and social media posts — including direct connections to LinkedIn, X, and Bluesky.

AI context annotations (audience, tone, channels) cascade through the page hierarchy and are rendered as JSON-LD — the foundation for semantically clean platforms.

Web Model Context Protocol server for TYPO3 — makes search, navigation, and page content accessible to AI agents via navigator.modelContext directly in the browser.

TYPO3 extension for FrankenPHP worker-mode integration. 103 Early Hints from the AssetCollector, REST-based cache invalidation against Caddy/Souin, PSR-14 auto-invalidation plus a backend module.

Cluster-aware TYPO3 cache backend without a shared filesystem — drop-in replacement for FileBackend/SimpleFileBackend in Kubernetes. Metadata central (DB/Redis), payloads pod-local.

Standalone Node WebSocket server for TYPO3 backend collaborative editing. Yjs plus Redis pub/sub for multi-instance sync, authenticates against collab-core via REST plus JWT. Early development.

Runtime secret resolution for containerised TYPO3 deployments. %secret(KEY)% syntax in site configs, with cascading lookup (KEY_FILE env → /run/secrets/ → env fallback).

Fluent configuration API with context-based presets (Production, Development, CLI, Testing) and cascading secret resolution. TLS/mTLS discovery, mailer and logging helpers.

Production-grade Redis/Valkey backend for TYPO3 — with Sentinel support, TLS/mTLS encryption, and distributed locking. Caching framework, sessions, and KV storage from a single source.

Nextcloud app that brings GitLab slash commands into Talk: issues, MRs, pipelines via chat. Per-user auth, AES-256-CTR encrypted tokens, app-based bot with no external webhook server required.

Dolibarr ERP/CRM module with deep GitLab integration: bidirectional issue/ticket sync, time tracking, release browser, wiki viewer — all assigned per user, automated by triggers and cron.

GitLab extension for spec-kit: automatically create user stories from spec.md as GitLab issues with labels, milestones and task links — via glab CLI.

Metapackage across the whole family — discovery, agent authentication and the commerce protocols in a single require. Registering the bundles, the routes and the firewall stays manual work.

The foundation: provider interfaces, registries and the channel-aware context. It ships no endpoint of its own — a class that implements one of the interfaces is registered automatically across the container.

Channel-aware robots.txt with AI crawlers named explicitly and content signals. A wildcard group does not read GPTBot as a statement about itself — so every token gets its own.

llms.txt as a map, not a catalogue. llms-full.txt is bounded twice, stops between entries rather than in the middle of one, and says that it stopped.

Accept: text/markdown for the storefront. The Markdown is built from entity data through a template, not from rendered HTML — otherwise navigation, footer and cookie banner end up in the document.

RFC 9727: the catalogue at /.well-known/api-catalog and the Link headers that advertise it. What gets listed is what the installed bundles register — without the package knowing them.

The discovery index at /.well-known/agent-skills/index.json. The SHA-256 digest is computed over the document that is actually served, not configured — otherwise it goes stale with the first text change.

The Agent Card at /.well-known/agent-card.json. The skills come from the shared registry — maintaining three copies by hand is the route by which they start contradicting each other.

Shop tools for the MCP server plus the Server Card per SEP-1649. An agent learns the transport and the tool surface before it connects, instead of finding out by trial and error.

Registers shop actions as WebMCP tools in the customer's browser, so a page-bound agent can search on the page the customer is looking at. Deliberately read-only.

OAuth 2.1 with dynamic client registration and mandatory PKCE, plus the RFC 8414 and RFC 9728 metadata. Access is delegated, never autonomous: a token always stands for an administrator.

/auth.md, assembled from the installed authentication methods. The same descriptors feed the agent_auth block of the OAuth metadata, so the two do not drift apart.

The key directory at /.well-known/http-message-signatures-directory. Only the outbound half of the protocol: it lets others verify requests from this shop.

Agentic Commerce Protocol: a discovery document and an SKU-accurate product feed. The checkout is withheld by default — with age-restricted assortments the purchase has to happen where age can be verified.

The discovery profile at /.well-known/ucp. It deliberately serves a superset, because the specification and discovery scanners expect different shapes and both occur in real clients.

An OpenAPI 3.1 document at /openapi.json with x-payment-info on payable operations. The prices come from the same table that x402 enforces.

Answers a data route with HTTP 402 and the payment requirements an agent can meet. Off by default — never the storefront, never the checkout, never the discovery documents.