u/Firm_Meeting6350

I guess this is a weird question, but I'm about to "promote" my side project. Nowadays with all the AI slop we all got spammed with great looking projects (at first sight) just to find out quickly that it's.. well... slop. That in turn leads to a kind of fatigue, only looking at a project short-term and then judging it.

My project is pretty complex, powerful, maybe even brutally over-engineered. At least I'd say that it'll take hours to fully understand it and to (hopefully) discover some beauty.

Enough prose: what I'm looking for is some kind of "certified body", like a well-known ts coder with some reputation and trust. Does this kind of thing exist? And to make it clear: payment is independent from outcome. If review says it's slop, it's slop, and amount is due :D

I know everybody hates AI-generated posts but that also means that you have to handle my writing being non-native english and neurodivergent :D

So this is a project I spent most of my free time on in the last 8 months after I started mcp-funnel (https://github.com/chris-schra/mcp-funnel, now rather obsolete) - I was thinking that it should be .. well... helpful at least... to create a "thing" (tooling, framework, ecosystem, no matter how you call it) to connect typical components involved during "AI-assisted engineering". And this led to the Makaio Framework: https://github.com/makaio-ai/makaio-framework.

I'm intentionally posting here in r/typescript first (instead of any AI-related subs) because I'm most interested in your thoughts about the general architecture and abstraction. Note that this is really solely about the architecture - I won't even guarantee that the codebase is runnable in other environments than my machine and CI :D (although I pretty much think so). And it's code-first, no packages published yet.

Here are the "edges" I think that are most relevant for TS devs:

• Schema-first: Zod is the definition layer - Bus subjects, CLI args, tool I/O, storage schemas, extension config... all flow from Zod schemas. Types are z.infer<>, no parallel maintenance. Comparable to tRPC-level type safety, but for a full event bus. (see https://github.com/makaio-ai/makaio-framework/blob/develop/docs/bus/index.md )
• Compiler as architecture guardian: The event/request split, namespace scoping, and local/channel subject routing are encoded in the type system. Wrong usage doesn't compile. (see, for example, https://github.com/makaio-ai/makaio-framework/blob/develop/docs/bus/decoupling.md )
• Multi-tier abstraction with type safety: The adapter contract is three layers deep: AIAdapter<TBus, TConnector, TAgent> → AIAgent<TBus, TConnector> → AIAgentConnector. Each layer is ndependently swappable (new connector for an SDK update, new agent for different orchestration) and TypeScript generics enforce correct composition at compile time. Wiring the wrong connector into the wrong agent is a type error, not a runtime crash. A shared conformance test suite then verifies that the type contracts also hold semantically: consistent streaming, tool approval, and error handling across 9 adapters (Claude, Gemini, Codex, GitHub Copilot, Qwen). Cross-language SDKs (Python, Rust, TS) share wire-level conformance fixtures.
• Maybe you might find the "code policies" interesting - I tried to build some guardrails supporting "AI-first engineering" (while avoiding slop) by creating custom test reports and a custom validation script (token-optimized and - hopefully - AI- and at the same time human-friendly rules) (https://github.com/makaio-ai/makaio-framework/blob/develop/scripts/validate.ts)

Stack:

• Well, Typescript :D Zod (v4), Drizzle (sqlite), Vitest, Node & bun (adopting bun more & more)
• Claude Code for planning, human for "coding the foundations", reviewing and fixing (most of) the slop, Codex (and Coderabbit) for review
• Electrobun for (minimalist) GUI (I like it so far - but still plan to keep feature parity with the parallel Electron GUI.. just in case)
• Starlight with some handmade extras for "website" https://makaio.ai
• Cloudflare Snippet in a desperate experiment (not working yet) to render markdown instead of HTML from docs - I tried rewriting URLs for AI "user-agents" from, e.g. makaio.ai/why to makaio.ai/why.md based on their "Accepts: text/markdown"-header (which they don't seem to send yet, obviously. Narf.)

Seriously, feel free to downvote and share you thoughts (including the negative ones) but PLEASE keep in mind: I really put a lot of effort (and heart & cognitive capacity) into this ;)