dossier / implemented

Pimbas

Friendly table-football matches and tournaments become a clear domain while the architecture reduces runtimes and preserves contracts.

Source reference: mainLicense: Verify in the repository before reuse

Visual summary of Pimbas

01 / Context

I built Pimbas around the real needs of people I know who play table football and needed to organize friendly matches and tournaments. The project was not adopted because I no longer had enough time to maintain it. It records an architectural evolution from Fastify to Next.js without turning intent into a usage outcome.

02 / Architecture map

01
Real need
People organize friendly table-football matches and tournaments.
02
Preserve contracts
The migration keeps the observable boundary stable.
03
Consolidated Next.js
One operational surface, independent domain.
04
Tests and history
Versioned evidence of the transition.

03 / Decisions

Moving the HTTP boundary to Next.js reduces deployment and configuration surfaces.

Matches, rankings, and tournaments remain organized as rules independent from delivery.

Authentication, authorization, and group membership remain separate decisions.

04 / quality

ModifiabilityDomain separated from web delivery.Versioned structure and tests in the repository.

OperabilityFewer runtimes to configure and observe.Fastify → Next.js migration recorded as a decision.

SecurityAuthorization and group isolation at boundaries.Contracts and checks in code.

Evidence

Source codePublic implementation and migration history.
Verification stateLint, types, tests, build, license, and contract differences must be confirmed in the repository before this case is promoted to verified.

Known limits

The project was not adopted because there was not enough time to continue maintaining it.
The source repository license still needs confirmation.
The source commit will be pinned after the pre-publication audit.
Debt and reversible decisions stay explicit rather than being resolved through narrative.