Claude Code hooks plugin for structured context compression (/clear-safe persistent memory)
MCP server that exposes a design system manifest as conversational primitives for Throughline.
A competent, brand-neutral reference design system demonstrating contract compliance for Throughline.
Scaffolder for new Throughline projects (Payload CMS + MCP servers + Inngest workflows).
Policy-gated publishing server for Throughline. Wraps Payload's update operation with composition, accessibility, required-field, embargo, and approval gating.
Composable Inngest function factories for the Throughline framework — revalidation, scheduled publishing, approval expiration, audit fan-out, healthcheck.
Transactional email system for the Throughline framework. Resend wrapper, themeable React Email templates, and Inngest functions that subscribe to the approval-workflow notification events.
Read-only MCP query tools over the Throughline audit log. Pairs with core's auditPlugin (which writes records).
Core plumbing for Throughline: audit log, MCP authentication and handler, event taxonomy + Inngest client factory, env handling, logger, shared utilities.
The contract every AI-ready design system satisfies to be consumable by Throughline.
Conversational approval workflow server for Throughline. Provides the approval resolver the publishing server consumes plus MCP tools for requesting and responding to approvals.
Plugin architecture for connecting Throughline-powered Payload sites to external systems. Ships the Integration contract, registry, collection, MCP tools, and a generic outbound-webhook integration as the first concrete example.
Policy-aware forms layer for the Throughline framework. Wraps Payload's Form Builder with privacy notices, consent, honeypot spam protection, IP rate limiting, a destination allowlist, and submitter confirmation. Six MCP tools for Claude-driven form manag
Shared plugin and MCP contract types and the cross-plugin registry for @forumone/throughline core packages.
The cross-machine cognitive bus for AI agents. Your Dropbox/Drive is the only backend — no server, no database. Append-only JSONL that any filesystem-capable AI can read and append.