Glossary51 terms

The Launch Pad — the organisation that owns, builds, and operates all the projects described in this dashboard.

TLP's name for the unified ecosystem of all its projects, services, and infrastructure — the goal is for everything to eventually feel like one connected whole.

TLP's family of native Mac and iOS apps — including FLOU, Arc, Lamigra, and others — all built with Apple's Swift language and designed for Apple devices.

TLP's flagship creative platform — nicknamed "The Digital Apex" — a dual-aesthetic website where users publish and discover raw creative work.

TLP's editorial briefing site — a polished publication-style web app used for internal communications, creative briefings, and editorial content.

The parent service that hosts Glasshouse — it's TLP's general-purpose hosting platform for web apps that don't belong to the rawrnot project.

The nickname for TLP's external hard drive where all the OpenClaw native app projects live locally during development — the "D" stands for "Drive."

A summary file placed in every project that describes exactly where things stand — written so the next developer (or AI agent) can pick up seamlessly without a verbal briefing.

An instructions file that tells Claude how to work in a specific project — conventions to follow, tools to use, and behaviours to always (or never) do.

Google's collection of cloud services — servers, databases, storage, networking, and more — that TLP rents instead of owning physical hardware.

Google's managed database service — instead of maintaining a database server yourself, you rent one that Google keeps running, backed up, and up to date.

A defined way for two programs to talk to each other — like a waiter who takes your order to the kitchen and brings back your food without you going in yourself.

A "robot user" created in Google Cloud that automated systems log in as so they can perform tasks on your behalf, without using a real person's login.

The credential file (like a password on a USB stick) that proves a service account is who it says it is when connecting to Google Cloud.

Google's secure digital vault where passwords, API keys, and other sensitive values are stored so they never appear in plain text inside the code.

Google Cloud's permission system — it controls exactly who (or what automated system) is allowed to do what inside your cloud account.

A live, publicly accessible web service running on Google's infrastructure that automatically handles more traffic when busy and costs nothing when idle.

The physical location on the map where your cloud server actually lives — for example, europe-west1 means the server is in a Google data centre in Belgium.

An automatic safety check that runs every time someone saves code, making sure nothing is broken before it goes any further.

The automatic process that takes code which passed its safety checks and pushes it live to the internet without anyone having to do it manually.

Publishing code so it is live and accessible to real users — think of it as flipping the switch from "in progress" to "out in the world."

The step where the computer takes your raw code and assembles it into a finished, runnable program, the same way a factory takes parts and assembles a product.

A series of automatic steps that code travels through — tests, safety checks, assembly, and publishing — before it reaches real users.

A way of packaging an app and everything it needs to run into one self-contained box, so it behaves identically on any computer or server.

Google's hosting service that takes a packaged app and runs it on the internet automatically, turning itself off when nobody is using it to save money.

Google's private storage locker for packaged apps — before an app can be deployed it gets stored here, like a backstage area before going on stage.

The JavaScript library TLP uses to build interactive web pages — it breaks the page into reusable pieces (components) that update automatically when data changes.

A development tool that makes building React apps dramatically faster — it reloads changes in the browser almost instantly while you're working.

A CSS toolkit that lets developers style web pages by adding short descriptive words directly in the code, instead of writing separate style sheets.

A stricter version of JavaScript that checks for obvious mistakes while you're writing code — like spell-check but for logic — so fewer bugs reach users.

A runtime that lets JavaScript — normally only used inside web browsers — run on a server, so the same language can power both the front end and back end.

Apple's programming language for building apps on Mac, iPhone, and iPad — fast, safe, and designed specifically for Apple devices.

Apple's modern framework for describing what a Mac or iPhone app's interface looks like and how it behaves, using straightforward, readable code.

A web server framework written in Swift — it lets TLP's back-end services be built in the same language as the Mac apps, keeping the team's expertise unified.

A powerful open-source database that stores all structured data — user accounts, records, relationships — and is known for being reliable and feature-rich.

A framework built on top of React that adds server-side features — it can pre-render pages for speed, handle back-end logic, and manage routing all in one project.

A TypeScript tool that acts as a translator between your code and the database — you write normal TypeScript, and Drizzle converts it into database instructions.

The website where all of TLP's code is stored, tracked, and shared — every change is recorded so you can always go back to an earlier version.

A project's code folder that also contains the complete history of every single change ever made to it, like a document with infinite undo.

A saved snapshot of the code at a specific moment, with a message explaining what changed — like a checkpoint in a video game you can always return to.

A separate copy of the code where you can work on a new feature or fix without affecting the version everyone else is using.

A formal request to add your branch's changes into the main codebase, giving the team a chance to review and discuss the work before it goes live.

Combining the changes from one branch into another — the final step that brings completed work into the main codebase.

The primary, production-ready version of the code — what gets deployed to real users and what every other branch is eventually merged back into.

Anthropic's standard plug-and-play system for connecting AI assistants to outside tools and services, so Claude can search the web, read files, send messages, and more.

A small bridge program that gives an AI assistant the ability to use one specific tool or service — for example, the GitHub MCP server lets Claude read and write code.

Anthropic's AI assistant — the one writing this glossary — used across TLP for coding, writing, research, and running automated agent tasks.

A tool that can control a web browser programmatically — TLP uses it to let AI assistants visit websites, click buttons, and extract information automatically.

The AI brain behind assistants like Claude, ChatGPT, and Gemini — a very large model trained on enormous amounts of text that can read, write, and reason about almost anything.

The tiny unit of text that an AI processes — roughly a word or part of a word — and also the "currency" that determines how much an AI interaction costs.

The amount of text an AI can hold in its "working memory" at once during a conversation — once the limit is reached, earlier parts of the chat start to fade.