Mosaic

The description states that Mosaic is a pluggable framework for building multi-agent systems on OpenAI. It includes three agents:

• Luna (interprets raw events)
• Terra (analyzes what is happening)
• Sol (briefs the operator)

These agents feed into a single, live operating picture. The system runs on OpenAI when a key is present, replays banked responses deterministically when not, and falls back to fixtures offline.

It uses:

• Go for backend
• Postgres for event spine
• OpenAI models (with strict structured output)
• Svelte UI
• Docker, Supabase, Cloud Run

The framework is described as not a demo, but a tool others can adapt without fighting over ownership.

Inference Mosaic appears to be a prototype or early-stage framework built for developers or engineers working in high-stakes domains like cybersecurity. It is not a finished product or SaaS offering, but rather an open-source or reusable architecture.

The author positions Mosaic as:

• A framework, not a product
• Designed to supplement humans, not replace them
• Built with safety and observability in mind
• Focused on high-stakes domains (e.g., emergency operations, cybersecurity)

Key claims include:

• AI should "take the noise off our plate" so we can do what only humans can.
• The system ensures no autonomous execution — this is “baked into the architecture.”
• It supports deterministic replay for demos and testing.

Inference The positioning reflects a belief in human-in-the-loop AI systems, especially in domains where errors are costly. This is not a commercial product, but a technical approach or architectural pattern.

The description does not name specific customers or personas. However, the author implies:

• Developers or engineers working with multi-agent systems
• Teams in high-stakes domains (e.g., cybersecurity, emergency response)
• Organizations looking to build safe AI systems that avoid autonomous actions

There is no evidence of a defined ICP beyond these implied use cases.

Inference The target audience likely includes technical teams building AI applications, particularly those in regulated or safety-critical industries. However, the lack of customer data means this remains speculative.

No business model or pricing information is provided in the description. The framework is described as a pluggable system intended for others to use and adapt — not sold directly.

Inference There is no evidence of monetization, licensing, or revenue streams. If Mosaic becomes a product, it would likely be through developer adoption or enterprise licensing, but this is not stated.

The system is built using:

• Go (backend)
• Postgres (event spine)
• OpenAI models
• Svelte UI
• Supabase, Cloud Run for deployment
• Playwright for end-to-end testing

Key technical features include:

• Pluggable architecture with extensibility as a design constraint
• Deterministic replay using cassette layer
• Structured output from OpenAI models
• Support for offline fallbacks and deterministic behavior

Inference The system shows early signs of thoughtful engineering, particularly around pluggability and deterministic execution. However, it is not yet proven in production or at scale.

There is no evidence of:

• Customers
• Revenue
• Product-market fit
• Adoption beyond the author’s own development
• Any form of traction or usage metrics

The project was built solo in four days and submitted to a hackathon. It is described as a framework, not a product.

Inference This is an early-stage prototype with no demonstrated traction or maturity. The author's goal was to build something reusable, but there’s no indication of real-world usage or impact.

The description does not mention competitors or similar tools in the market. It is unclear whether Mosaic is positioned against other multi-agent frameworks, AI orchestration platforms, or decision-support systems.

Inference There is no evidence of a competitive landscape. The project appears to be self-contained and unanchored to existing products or markets.

• No traction or adoption: The framework has not been used by others beyond the author.
• Unproven in production: It is described as a prototype, not a tested system.
• Solo development: Only one person built it; no team or institutional support.
• No commercialization plan: No pricing, licensing, or monetization strategy is evident.
• Limited evidence of real-world relevance: The domain use case (cybersecurity, emergency operations) is mentioned, but not validated.

Inference The project lacks any commercial viability indicators. It may be a useful concept, but there is no evidence it has moved beyond the idea stage or gained traction.

1. What specific high-stakes domains have you tested Mosaic in?
2. Have you had others adopt or adapt the framework? If so, how?
3. Is there a plan to monetize or commercialize this framework?
4. How does Mosaic handle scalability beyond single-agent use cases?
5. What are the key technical limitations of the current architecture?
6. Are there any known issues with OpenAI’s structured output mode that affect reliability?