flux7.art

Before an agent runs a tool, something decides whether it may. flux7 does that in four steps: a rules engine in under a millisecond, past decisions kept in memory, an arbitration when the rules don't settle it, and a human when it matters.

L0  flux7-mesh        policy engine          <1ms
     |
L1  flux7-memory      3+ past approvals      ~100ms
     |
L1+ flux7-supervisor  rules + LLM            ~2-20s
     |
L2  flux7-console     human UI               minutes
     |
    decisions stored as facts in memory

The same problem, for data instead of agents. Making sure the messages that travel between systems keep the shape everyone agreed on. Schema registries, Kafka, API platforms, and the consulting that goes with them.

// SaaS · Schema Registry · Governance

● live

event7

Schema Registry Governance Platform

Universal governance layer for Schema Registries. Tags, ownership, diff viewer, AsyncAPI, references graph and AI agent — provider-agnostic.

Next.jsFastAPISupabaseConfluentApicurio

Read more GitHub Docs

tap to flip →

4

SR Providers

AI

Schema Agent

SaaS

+ On-Prem

OSS

Apache 2.0

← tap to flip

// SaaS · Staffing · Capacity · Margin

● live

staff7

AI-Native Professional Services Platform

Staffing, capacity and margin platform for consulting firms. Connects skills, assignments, timesheets and financials — with an AI copilot. Multi-tenant · RLS · Edge.

Next.jsSupabaseCloudflareOllamaMCP

Read more Live GitHub

tap to flip →

100%

Multi-tenant RLS

AI

Supabase context

Edge

Cloudflare

EN/FR

i18n

← tap to flip

// Kafka · Proxy · Runtime Governance

● poc

kafka7

Runtime Enforcement for event7

Kafka wire-protocol proxy enforcing event7 governance verdicts at produce time. Schema ID extraction, verdict cache, non-compliant records rejected before the broker — decisions in event7, enforcement in a pure proxy.

KroxyliciousJavaKafkaevent7

GitHub

tap to flip →

producer ──► kafka7 ──► broker
                │
                └──► event7
              PASS · WARN · FAIL

0x00

SR wire format

300s

Verdict cache

FAIL

→ INVALID_RECORD

Go

Phase 2 · kmsg

← tap to flip

Small tools I use every day. MCP servers that let an AI agent draw a diagram, run a local model or cast to a TV, plus three workshops I built for my own image, music and document work.

Three workshops, built the same way. Image, music, documents. Each keeps one source file and produces every format from it. The AI part is a Claude Code session watching a folder, so there is no API key anywhere. Private tools, not products, but write if you want to know how they work.

Playing piano with an AI. It listens to what I play, names the chords and the key, and answers on the instrument. It also reads finished tracks, from the audio file or straight from the Renoise project. The three tools below meet in flux7-audio, the music workshop.