TestaAí
ZERO_OS / QUICK ACCESS

Navigate the lab.

10 results. Selected: Manifesto.

LAB. INDEX / 07 / LIVING PORTFOLIO

Seven tests.
No certainty.

Operations systems, quantitative research, automation, and games at different stages—presented as cases in architecture, trade-offs, and end-to-end delivery.

Read the system map
CATALOG / 202607

EXPERIMENTS
IN MOTION

02 PUBLIC DOORS / 05 LABS

SYSTEM MAP. 04 / HOW THE PORTFOLIO CONNECTS

One portfolio.
Four layers.

The products cross domains but reveal the same capability: turning a hypothesis into an operable interface, service, state, and integration.

  1. L1

    Interface & product

    Responsive experiences, complex state, and flows that make the domain visible to operators.

    • React 19
    • Next.js 16
    • React Native
    • Vite
    • TypeScript
    ERP, Auto Whats, AI_VTT, NEXO, Castle Wars, and Our Home
  2. L2

    Services & realtime

    APIs, gateways, and isolated processes that protect boundaries and keep interactions synchronized.

    • ASP.NET Core
    • Fastify
    • Node.js
    • Socket.IO
    • Supabase Realtime
    Renaissance, Auto Whats, Castle Wars, and Our Home
  3. L3

    Data & state

    Relational persistence, cache, event series, and authoritative rules designed around each use case.

    • PostgreSQL
    • Redis
    • ClickHouse
    • Firebase
    • Supabase RLS
    seven architectures with different state strategies
  4. L4

    Integrations & intelligence

    Models, voice, messaging, payments, and external APIs treated as capabilities with explicit limits.

    • AI agents
    • Baileys
    • Asaas
    • ZapSign
    • ProfitDLL
    automation, generative RPG, fintech, and SaaS operations
  1. 01 / BOUNDARIES

    Explicit boundaries

    Fragile integrations stay at the edges; domain, state, and policy remain testable.

  2. 02 / SAFE DEFAULTS

    Fail safely

    Blocked financial execution, human handoff, and authoritative rules are architectural choices.

  3. 03 / VERTICAL SLICES

    Ship end to end

    A first usable flow before the complete platform shortens the path from hypothesis to evidence.

  4. 04 / VISIBLE GAPS

    Documented gaps

    Anything still in memory, conceptual, or awaiting validation appears without launch language.

DIAGNOSTIC MATRIX. 05 × 07 / TECHNICAL COMPARISON

Different domains.
Comparable problems.

A quick view of runtime, state, critical path, and boundaries for each experiment. Scroll horizontally on smaller screens.

Technical comparison of runtime, data, flow, safety, and stage across seven experiments.
SYSTEM / DIMENSION01Project Renaissance02ERP03Castle Wars04Auto Whats05AI_VTT06Desafio Online07Our Home
RUNTIMEPrimary runtime.NET 10React + FirebaseNode + Socket.IONext + FastifyTypeScriptNext 16 + React 19Expo + React Native
STATEState and dataPostgres + ClickHouseFirebaseMemory / roadmapPostgres + RedisPostgreSQLPostgres + DrizzleSupabase + Postgres
SIGNALCritical pathtick → orderenrollment → billinglobby → constructionchat → handoffaction → narrativeclue → progresstask → synchronization
BOUNDARYSafety boundaryOMS / Risk gatesexternal adaptersdeclared gaphuman in the loopauthoritative rulesserver-side solutionhousehold RLS
SURFACESurfaceShadow + paperOperational baseRealtime prototypeSaaS onlineVertical slicePlayable MVPiOS MVP 1.0

* “Memory / roadmap” is a deliberately visible gap in Castle Wars, not a claim that persistence is complete.

LAB. INDEX / LIVING PORTFOLIO

Experiments
in motion.

7 ideas at different stages. No promise of success—only a commitment to testing.

  • PUBLIC DOOR
  • INTERNAL LAB
  • SAFETY GATE
CAPABILITY LENSHighlight by technical challenge

07 highlighted experiments

02OPERATIONAL BASE
OPERATIONS / SAAS

ERP

[ name in progress ]

Management for schools, fitness studios, and sports operations: students, enrollments, contracts, and billing. It connects signatures, payments, and WhatsApp in one flow.

  • React
  • Vite
  • Firebase
  • Asaas
  • ZapSign
TEST QUESTION

Can a fragmented operation fit into one coherent workflow?

Open technical case file
  • React + Vite + Firebase
  • Asaas + ZapSign
  • WhatsApp + AI
  • Operations for dance and sports
ARCHITECTURE
Operational SPA → Firebase services → billing, signature, and WhatsApp adapters.
CHALLENGE
Unify enrollment, contract, and billing journeys without coupling the operation to each provider's details.
DECISION
Model the business flow first and treat payments, signatures, and communication as replaceable integrations.
NEXT SIGNAL
Consolidate the audit trail, role-based permissions, and cross-provider failure handling.
CORE
STUDENTS + ENROLLMENT
INTEGRATIONS
PAY + SIGN
Open case
03REALTIME PROTOTYPE
STRATEGY / GAME

Castle Wars

build. ally. conquer.

A multiplayer strategy game inspired by Tribal Wars 2. The prototype covers authentication, lobby, worlds, realtime, and the first resource-and-construction loop.

  • React
  • Node.js
  • Socket.IO
  • Firebase Auth
TEST QUESTION

Can synchronization and an initial economy sustain a fun multiplayer match?

Open technical case file
  • React + Node / Express + Socket.IO
  • Firebase Auth
  • Resources + first construction queue
  • In-memory state; persistence on the roadmap
  • Independent project, unaffiliated with the reference game
ARCHITECTURE
React client → Socket.IO gateway → Node.js world loop → Firebase authentication.
CHALLENGE
Synchronize lobby, resources, and construction at low latency before investing in the complete game economy.
DECISION
Validate the realtime loop in memory and declare persistence as a gap instead of pretending the infrastructure is ready.
NEXT SIGNAL
Persist world state, add reconciliation, and test simultaneous command conflicts.
FLOW
LOBBY → MATCH
LOOP
RESOURCES + BUILD
Open case
04SAAS ONLINE
AUTOMATION / AI

Auto Whats

conversation becomes operation.

Connects WhatsApp by QR code, organizes the CRM, and uses business-aware AI to respond, qualify leads, schedule, follow up, and hand conversations to people.

  • Next.js
  • Fastify
  • PostgreSQL
  • Redis
  • Baileys
TEST QUESTION

Can AI speed up service without hiding the human transition?

Open technical case file
  • Next.js + Fastify
  • PostgreSQL + Redis
  • Baileys + Firebase
  • Human support handoff
ARCHITECTURE
Web console → Fastify API → Redis/PostgreSQL queues and state → WhatsApp session through Baileys.
CHALLENGE
Automate conversations without losing commercial context or hiding when AI should step aside.
DECISION
Treat AI as a per-conversation controllable mode and keep human handoff as a first-class product path.
NEXT SIGNAL
Expand quality metrics, context recovery, and operational guarantees for connected sessions.
CONNECTION
QR + REALTIME
OPERATIONS
CRM + AI
Open case OPEN AUTOWHATS
05VERTICAL SLICE
RPG / GENERATIVE GAME

AI_VTT

The Ashglass Signal.

A solo or two-player virtual tabletop with a persistent lobby, exploration, and combat. The AI game master works through text or voice without controlling the rules.

  • TypeScript
  • PostgreSQL
  • Voice AI
  • Rules engine
TEST QUESTION

Can an AI run the story without taking over the rules?

Open technical case file
  • TypeScript + PostgreSQL
  • Game master by text or voice
  • Solo and two-player campaigns
  • Authoritative rules outside the AI
ARCHITECTURE
Shared tabletop → rules and state engine → narrative context → AI game master by text or voice.
CHALLENGE
Enable narrative improvisation without letting the model alter rules, movement, or authoritative campaign state.
DECISION
Separate probabilistic narration from deterministic resolution; AI proposes fiction and the system validates actions.
NEXT SIGNAL
Test long-running campaign recovery, voice latency, and narrative consistency in two-player sessions.
TABLE
SOLO + DUO
CAMPAIGN
ASHGLASS SIGNAL
Open case
06PLAYABLE MVP
PUZZLE / SOCIAL GAME

Desafio Online

NEXO / The Impossible Map.

A platform for pairs and groups with teams, invitations, and persistent expeditions. The Impossible Map combines clues, timed hints, and shared progress.

  • Next.js 16
  • React 19
  • PostgreSQL
  • Drizzle
  • Firebase Auth
TEST QUESTION

Can different clues become a memorable social competition?

Open technical case file
  • Next.js 16 + React 19
  • PostgreSQL + Drizzle
  • Firebase Authentication
  • Hackathons + treasure hunts
ARCHITECTURE
Expedition interface → server-side team actions → persistent PostgreSQL progress → Firebase identity.
CHALLENGE
Keep teams synchronized, hints timed, and progress shared without exposing answers to the client.
DECISION
Keep solutions and progression authoritative on the server; the browser receives only the state required for the current stage.
NEXT SIGNAL
Instrument clue difficulty and completion rankings, then build editorial tools for new expeditions.
FORMAT
PAIRS + GROUPS
EXPEDITION
IMPOSSIBLE MAP
Open case OPEN NEXO
07iOS MVP 1.0
MOBILE / HOUSEHOLD

Our Home

one home, one shared routine.

An iPhone app where couples and families share shopping, recurring tasks, and responsibilities with real-time synchronization.

  • Expo SDK 57
  • React Native
  • TypeScript
  • Supabase
  • PostgreSQL
TEST QUESTION

Does routine feel lighter when shopping, tasks, and context live in one place?

Open technical case file
  • Expo SDK 57 + React Native
  • Supabase Auth, Postgres + Realtime
  • Shared shopping and tasks
  • Recurrence + status history
  • RLS + in-app account deletion
  • Version 1.0 prepared for iPhone
ARCHITECTURE
React Native app → Supabase commands and channels → PostgreSQL with RLS, RPCs, and triggers → synchronized household projection.
CHALLENGE
Synchronize several residents' routines without losing authorship, recurrence, or household-level data isolation.
DECISION
Keep authorization and critical transitions close to the database; the app sends intents and reconciles the projection through Realtime.
NEXT SIGNAL
Validate version 1.0 on physical iPhones before adding notifications and a shared calendar.
ROUTINE
SHOPPING + TASKS
SYNC
REALTIME + RLS
Open case

* Features were verified in the repositories. Some hypotheses, metrics, working names, and stages remain editorial until public validation.

ARTIFACTS. 005 / BUILD + CONCEPT

The experiment also
builds worlds.

Four builds and one concept—clear provenance, no pretend product.

Four people play a fantasy tabletop RPG with miniatures, dice, and teal lighting.

ASHGLASS / WORLD BUILDING

The campaign already has a face, map, and rules.

Lobby, exploration, combat, and recovery in The Ashglass Signal. AI narrates; rules, movement, and state remain authoritative.

View experiment
NEXO poster: an encoded-treasure message beside a map with a route and puzzle symbols.

NEXO / PLAYABLE MVP

The treasure is encoded.

Invite-only teams, readiness, persistent progress, and timed hints in a shared expedition.

View experiment
Auto Whats dashboard with CRM, demonstration conversations, and global AI controls.

AUTOWHATS / BUILD

AI joins in. People stay in control.

Real capture: global or per-chat AI, CRM, and support. Displayed contacts are demonstration data.

View experiment
Nighttime medieval map with castles, settlements, and green strategic routes.

CASTLE WARS / CONCEPT FRAME

Territory before conquest.

A concept for fortresses, settlements, and routes. This is not a prototype capture.

View experiment
Our Home demo on an iPhone with a summary and shared household task cards.

OUR HOME / IOS MVP

One home. One shared version of the routine.

Real demo-mode capture: recurring tasks, assignees, status, and authorship without exposing personal data.

View experiment

FIELD NOTES. 003 / WITHOUT LAUNCH FILTERS

The test also shows
what is missing.

  1. RNS / SAFETYDECISION

    Execution is opt-in, never a shortcut.

    Orders are blocked by default: every intent passes through OMS/Risk, and execution requires enablement and a checklist. This is not investment advice.

  2. CW / GAPLIMIT

    The lobby works. The economy begins.

    Castle Wars synchronizes entry, matches, resources, and the first construction. State remains in memory; map, combat, and persistence are on the roadmap.

  3. LIVE / SIGNALSIGNAL

    Two tests already have a public door.

    Auto Whats and NEXO are the only experiments with validated public deployments in this edition of the lab.

PIPELINE. 07 / TEST STATUS

Everything starts
unfinished.

The portfolio is not a collection of launches. It is a living view of what is being discovered, prototyped, and placed in front of real people.

  1. Castle WarsStage PROTOTYPE. Status: REALTIME PROTOTYPE
  2. AI_VTTStage ALPHA. Status: VERTICAL SLICE
  3. Project RenaissanceStage ALPHA. Status: V1 / SHADOW + PAPER
  4. ERP / unnamedStage PILOT. Status: OPERATIONAL BASE
  5. Desafio Online / NEXOStage PILOT. Status: PLAYABLE MVP
  6. Our HomeStage PILOT. Status: iOS MVP 1.0
  7. Auto WhatsStage PILOT. Status: SAAS ONLINE
ILLUSTRATIVE POSITIONS / MANUAL UPDATE

BEHIND THE TESTS / A REAL PERSON

Projects change.
The point of origin remains.

Meet Zero