PortfolioCase study · 02Open fictional demo

Personal execution system · Live fictional demo

Primordial
Portal

A calm execution layer that turns scattered plans into one reliable next action.

Role
Product designer & full-stack developer
Core idea
One obvious action with less re-finding
Delivery
Private target + isolated live showcase
LIVE UI / DAILYFICTIONAL DATA · PORTAL.PRIMORDIAL.MY
The live Primordial Portal fictional guest workspace showing capture, the next action, agenda, and focus
The daily surface

The quiet Daily surface keeps capture, the Inbox reminder, the next action, and Stopwatch in view without turning into a dashboard.

The personal problem

I could save a task. I still could not begin it without finding it again.

My plans lived across tasks, calendar events, notes, and self-hosted services. The information existed, but the transition from “I should do this” to “I am doing this now” carried too much friction.

The first Portal version reproduced that problem: capture succeeded, then starting the exact task required another search. That failure became the product direction. Every important action now preserves context and offers the smallest useful next step.

The execution loop

One identity from intention to evidence.

The task, calendar block, timer, focus record, and recovery state stay linked so the interface can move forward without asking the user to rebuild context. A typed timer title becomes a real Today task and starts immediately; a taskless Stopwatch is still allowed when naming the work would become its own obstacle.

  1. 01

    Capture

    Get the thought out without deciding everything.

  2. 02

    Start now

    Type once to create a Today task and begin.

  3. 03

    Schedule

    Manipulate or reuse one linked calendar block.

  4. 04

    Focus

    Count real elapsed time with Stopwatch by default.

  5. 05

    Record

    Keep notes and evidence without forcing completion.

  6. 06

    Recover

    Treat a missed block as information, not failure.

PRIVACY_BOUNDARY / SAME PRIVATE CODEBASEENFORCED

Private mode · deployment target

Personal system

  • Single administrator authentication
  • Persistent personal SQLite volume
  • Encrypted OAuth and integration credentials
  • Real calendar, notes, music, books, and services

portal.primordial.my · live fictional demo

Public showcase

  • Instant signed guest session
  • Per-visitor in-memory SQLite workspace
  • Deterministic fictional adapters
  • No OAuth, exports, private volume, or outbound calls

Focus and planning

Track real work. Change the plan directly.

Stopwatch is the default because real work does not always fit a preset interval. Pomodoro remains available when structure helps. Planner owns direct calendar manipulation; Daily stays quiet.

02LIVE UI / FULLSCREEN FOCUS · FICTIONAL DATA
The live fullscreen focus view with a running Stopwatch, session note, recent-session evidence, and next-task control

Evidence, not pressure.

Fullscreen focus keeps the timer, session note, recent evidence, completion, recovery, and the next task together. Notes also become calendar descriptions; statistics use actual focused time.

03LIVE UI / PLANNER · FICTIONAL DATA
The live Primordial Portal week Planner with fictional linked focus blocks, a task rail, and current work

Plan by touching the calendar.

Day and Week views support click and range creation, drag, resize, task drops, calendar colors, descriptions, and a fast anchored editor. Inbox tasks promote to Today when scheduled.

Engineering decisions

A small stack with deliberate boundaries.

Fastify owns one browser origin and proxies every private integration, keeping credentials away from the client and avoiding cross-origin fragility. SQLite carries tasks, focus, links, encrypted tokens, and preferences without adding operational weight.

Calendar create, update, and delete operations use a durable queue. Repeated edits coalesce, optimistic local blocks remain usable during outages, and successful replay attaches the Google identity without duplicating an event. Pagination keeps busy calendars complete.

The public build uses the same domain logic through an isolated database provider. Tests open two guest sessions, mutate one, and prove the other remains unchanged; any showcase outbound request is a test failure.

INTERFACE / server HTML + ES modules + FullCalendarEXECUTION / capture + calendar + Stopwatch + evidence + recoveryRESILIENCE / optimistic blocks + durable create/update/delete queueBOUNDARY / auth + CSRF + encrypted adapters + explicit statesDATA / persistent private SQLite or ephemeral guest SQLite

Context without surveillance

Useful signals stay close; judgment stays out.

A collapsed personal dock can surface Navidrome now-playing, Audiobookshelf progress, and Today or Week completion and focused minutes. There are no streaks, productivity scores, or shame-based comparisons. Time boundaries and weather use Africa/Algiers.

Operationally, readiness is separate from liveness, proxy trust is bounded, guest allocation and reset are rate-limited, private SQLite backups are restore-verified, and GitHub Actions runs typecheck, tests, build, Compose validation, and a clean production audit.

Verification

130automated tests across 24 files
2strictly separated modes
0outbound calls permitted in showcase mode

Built around a real personal constraint. Opened through a safe public boundary.

Less friction between
intention and action.

Try the fictional demo Return to portfolio