LAB. INDEX / 04 / LIVING PORTFOLIO

Four tests.
No certainty.

Collaboration, mobile, generative AI, and game systems at different stages—presented as cases in architecture, trade-offs, and end-to-end delivery.

Read the system map

CATALOG / 202604

EXPERIMENTS
IN MOTION

01 PUBLIC DOOR / 03 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.

L1
Interface & product
Responsive experiences, complex state, and flows that make the domain visible to operators.
- React 19
- Next.js 16
- React Native
- TypeScript
Castle Wars, AI_VTT, NEXO, and Our Home
L2
Services & realtime
APIs, gateways, and isolated processes that protect boundaries and keep interactions synchronized.
- Node.js
- Socket.IO
- Supabase Realtime
- Next.js server
Castle Wars, NEXO, and Our Home synchronization
L3
Data & state
Relational persistence, cache, event series, and authoritative rules designed around each use case.
- PostgreSQL
- Drizzle
- Firebase
- Supabase RLS
four architectures with different state strategies
L4
Integrations & intelligence
Models, voice, generative media, and external APIs treated as capabilities with explicit operational boundaries.
- AI agents
- Voice AI
- Firebase
- external APIs
generative RPG, realtime games, puzzles, and mobile

01 / BOUNDARIES
Explicit boundaries
Fragile integrations stay at the edges; domain, state, and policy remain testable.
02 / SAFE DEFAULTS
Fail safely
Authoritative rules, server-side progression, and per-user isolation are architectural choices.
03 / VERTICAL SLICES
Ship end to end
A first usable flow before the complete platform shortens the path from hypothesis to evidence.
04 / VISIBLE GAPS
Documented gaps
Anything still in memory, conceptual, or awaiting validation appears without launch language.

DIAGNOSTIC MATRIX. 05 × 04 / 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 four experiments.
SYSTEM / DIMENSION	01Castle Wars	02AI_VTT	03Desafio Online	04Our Home
RUNTIMEPrimary runtime	Node + Socket.IO	TypeScript	Next 16 + React 19	Expo + React Native
STATEState and data	Memory / roadmap	PostgreSQL	Postgres + Drizzle	Supabase + Postgres
SIGNALCritical path	lobby → construction	action → narrative	clue → progress	task → synchronization
BOUNDARYSafety boundary	declared gap	authoritative rules	server-side solution	household RLS
SURFACESurface	Realtime prototype	Vertical slice	Playable MVP	iOS 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.

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

DATA VERIFIED / PROVISIONAL COPY / AUG 22 2026

PUBLIC DOOR
INTERNAL LAB

CAPABILITY LENSHighlight by technical challenge

04 highlighted experiments

STRATEGY / GAMEREALTIME PROTOTYPE

IN DEVELOPMENTNot ready for public use yet.

Castle
Wars

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 full case

02VERTICAL SLICE

RPG / GENERATIVE GAME

IN DEVELOPMENTNot ready for public use yet.

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

03PLAYABLE MVP

PUZZLE / SOCIAL GAME

IN DEVELOPMENTNot ready for public use yet.

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

04iOS MVP 1.0

MOBILE / HOUSEHOLD

IN DEVELOPMENTNot ready for public use yet.

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. 004 / 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

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. 002 / WITHOUT LAUNCH FILTERS

The test also shows
what is missing.

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.
LIVE / SIGNALSIGNAL
One test already has a public door.
NEXO is the only experiment with a validated public deployment in this edition of the lab. The remaining cases stay internal and state that limit in the interface itself.

PIPELINE. 04 / 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.

Castle WarsStage PROTOTYPE. Status: REALTIME PROTOTYPE
AI_VTTStage ALPHA. Status: VERTICAL SLICE
Desafio Online / NEXOStage PILOT. Status: PLAYABLE MVP
Our HomeStage PILOT. Status: iOS MVP 1.0

ILLUSTRATIVE POSITIONS / MANUAL UPDATE

BEHIND THE TESTS / A REAL PERSON

Projects change.
The point of origin remains.

Meet Zero

Four tests.No certainty.

One portfolio.Four layers.

Interface & product

Services & realtime

Data & state

Integrations & intelligence

Explicit boundaries

Fail safely

Ship end to end

Documented gaps

Different domains.Comparable problems.

Experimentsin motion.

CastleWars

AI_VTT

Desafio Online

Our Home

The experiment alsobuilds worlds.

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

The treasure is encoded.

Territory before conquest.

One home. One shared version of the routine.

The test also showswhat is missing.

The lobby works. The economy begins.

One test already has a public door.

Everything startsunfinished.

Projects change.The point of origin remains.

Four tests.
No certainty.

One portfolio.
Four layers.

Different domains.
Comparable problems.

Experiments
in motion.

Castle
Wars

The experiment also
builds worlds.

The test also shows
what is missing.

Everything starts
unfinished.

Projects change.
The point of origin remains.