Stack

SYSTEM INVENTORY

What the work runs on.

LAYERS: 03
TARGETS: NATIVE / WEB / SYSTEMS
ARGUMENTS: 03

Tulio Cunha / Computer SystemsINDEX 04 / 08

Full stack. Actual stack.

Three layers, three arguments: what belongs to the platform, what keeps a page coherent, and where to draw the line.

01NATIVE PACKAGE

Native.PKG

APPLE PLATFORMS

The system already owns windowing, persistence, and services. This chapter leaves them owned.

What deserves to belong to the platform?

CHOICE: Build on the platform instead of beside it: system windowing, native persistence, platform services. Tested behaviour arrives free instead of re-implemented.

TRADEOFF: Fidelity costs portability. Every platform behaviour assumed is one to rebuild anywhere else.

COMPOSITION: SwiftUI / AppKit
LANGUAGE: Swift
STATE: App-native stores
PERSISTENCE: SQLite / system services
TOOLCHAIN: SwiftPM / Tuist
TARGETS: macOS / iOS

02WEB PACKAGE

Web.PKG

BROWSER RUNTIME & WEBGPU

This portfolio renders twice from one state. This chapter keeps both renderers honest.

How do interaction, rendering, and content stay coherent?

CHOICE: Feed the canvas and the document from the same record on the same frame clock. This portfolio is the filed evidence: one destination registry, one heartbeat.

TRADEOFF: Coherence costs indirection. Every shared signal is a contract two renderers must honor, tested at the seam.

EVIDENCE: LIQUIDIFY: A WEB DESIGN SYSTEM EXTRACTED FROM NATIVE WORK

LANGUAGE: TypeScript
COMPOSITION: React
ROUTING: TanStack Start
RENDER: Three.js / WebGPU
FRAME: GSAP, one clock
EDGE: Cloudflare Workers

03SYSTEMS PACKAGE

Systems.PKG

SERVER / DISTRIBUTED INFRASTRUCTURE

Nobody sees this half, and it decides whether the rest stays true. This chapter manages it with boundaries.

Where do boundaries make complexity manageable?

CHOICE: Own every resource behind a typed contract. Callers name what they want; they never reach past the boundary for how it is kept.

TRADEOFF: Boundaries cost round-trips. Everything hidden behind a contract is something you cannot reach for in a hurry.

EVIDENCE: BOUTIQUEDB: A SWIFT PERSISTENCE LAYER WITH EXPLICIT BOUNDARIES

LANGUAGES: Rust / Zig / Go
CONCURRENCY: Elixir / OTP
DATA: PostgreSQL
EDGE: Cloudflare / Fly
CONTRACTS: Typed boundaries
RULE: Callers see the contract

SIDE A

SERVICES

Services.

05Five services, one brief

SIDE B

SOURCE

Source.

Open source, libraries, servers and experiments live on GitHub, public as soon as they are ready to be read.

LiqUIdify, BoutiqueDB-Swift and the tools behind this site are filed there.

github.com/tuliopc23

BASE: BRAZIL / REMOTE
LANGUAGES: EN / PT-BR
CLIENTS: WORLDWIDE + BRAZIL
AVAILABILITY: OPEN