Fyso - Agent-Native ERP

Project Vision

An ERP system designed from the ground up to be consumed by AI agents (Agent-Native). It combines:

• Metadata-Driven Architecture: Entities and fields defined as metadata, not hardcoded
• Multi-Tenant: Complete isolation per tenant (schema-per-tenant)
• Auto-Generated MCP Server: Agent tools generated automatically from metadata
• AI UI Engine: UI component generation through AI
• Feature/Plugin System: Extensibility through installable features

Original Documentation

The original design documents can be found in /docs/original/:

File	Description
01-simulacion-ejecucion.md	Full simulation of how the system would work with "Cafe Cosmos"
02-blueprint-arquitectonico.md	3-layer architecture, DDD, EIP patterns, multi-tenancy
03-ui-engine-arquitectura.md	AI-powered UI generation system (Intent-to-Code)
04-simulacion-facturador.md	Complete example of invoice system generation
05-paper-academico.md	Research paper on AI UI Engine
DEPLOYMENT.md	Deployment guide for MVPs

Development Plan

Development is divided into incremental phases:

Phase	Name	Goal
MVP	Core Foundation	Minimum functional system with metadata-driven CRUD
Phase 1	Multi-Tenancy & Auth	Tenant isolation and authentication
Phase 2	MCP Server	AI agent integration
Phase 3	Feature System	Plugin/extension system
Phase 4	AI UI Engine	AI-powered UI generation

See details in /docs/phases/

Proposed Technology Stack

Backend

• Runtime: Node.js / Bun
• Framework: Hono / Express
• Database: PostgreSQL (Supabase)
• ORM: Drizzle / Prisma
• Validation: Zod

Frontend

• Framework: React 19 / Next.js 15
• Styling: Tailwind CSS
• Components: shadcn/ui
• State: TanStack Query

Infrastructure

• Hosting: Vercel / Railway
• Database: Supabase
• Auth: Supabase Auth / Clerk
• Realtime: Supabase Realtime

Architectural Principles

1. AGENT-FIRST PRINCIPLE
   "Every system decision optimizes for AI consumption"

2. METADATA-DRIVEN PRINCIPLE
   "UI and behavior emerge from schema, never hardcoded"

3. EVENT-DRIVEN PRINCIPLE
   "Loose coupling through async messaging"

4. TENANT ISOLATION PRINCIPLE
   "Complete isolation at every layer"

Project Structure (Proposed)

fyso/
├── docs/                    # Documentation
│   ├── original/           # Original design docs
│   ├── phases/             # Phase-by-phase plan
│   └── architecture/       # Architectural decisions
├── packages/
│   ├── core/               # Metadata engine
│   ├── api/                # REST/GraphQL API
│   ├── mcp-server/         # MCP Server
│   ├── web/                # Web frontend
│   └── shared/             # Shared types
├── features/               # Features/Plugins
└── migrations/             # Database migrations