RFC BBOS-RAU-0001 — BlueBookOS: Thee GPT Microkernel™

Install in a new chat

Copy this. Paste it. Press enter.

This boots a tiny app-making OS inside an AI chat. You do not need to know RAu or BlueBookOS first. Paste the whole box into a fresh chat, press enter, and it will ask what you want to build.

Copy the OS boot packet<br>What is this?<br>See what it can make

Loading OS boot packet…

A tiny OS for making apps with AI

BlueBookOS<br>boots in your chat.

BlueBookOS is a small set of rules and source code you paste into another AI chat. It helps that chat build apps carefully: first the RAu contract, then the working file. RAu is the little instruction language inside it. You can start without knowing either one.

Install it<br>See the demo<br>Copy this page

1 Demo included

— Source lines

— Built lines

0 Installs needed

It is A boot packet for an AI chat.

It does Turns the chat into a careful app builder.

You do Copy, paste, press enter, then answer what it asks.

It makes Portable files you can save and run.

No magic It does not change your device. It only teaches the chat how to work.

Contents

1. Abstract<br>2. Status<br>3. Terminology<br>4. Artifact Spec<br>5. Architecture<br>6. Demo<br>7. Vibe Coders Guide<br>8. Copy-Paste Prompts<br>9. Conformance

RAu is used here as a source-first artifact contract. The HTML5 files are host ports that render the behavior described by the RAu source. This app is intentionally plain to operate: open it, open the demo, inspect the final RAu, inspect the final HTML, and run the rendered page in place.

The main product claim is simple: a good AI artifact should not only be impressive to view; it should be reusable, reviewable, copyable, and portable into the next project.

The key words MUST , SHOULD , and MAY are used in their everyday standards-document sense: MUST means required for this showcase pattern, SHOULD means recommended for most projects, and MAY means optional but supported.

This file is self-contained. It does not require a server, package manager, build pipeline, remote stylesheet, CDN, or network call.

RAu The programming language and runtime used as the semantic source contract for an artifact.

Artifact A complete app, game, editor, reader, visualizer, or workflow unit intended to be shipped or remixed.

Host Port The executable target implementation. In this package, every host port is standalone HTML5.

Rendered Page The live browser view generated by loading the final HTML port into an embedded frame.

Source-First The RAu contract is treated as the durable product definition before host-language changes are made.

Vibe Coding A fast builder workflow where a human steers a frontier model with complete artifacts, clear goals, and acceptance criteria.

The package MUST embed the demo locally.<br>No runtime fetch is required to inspect source or render the included pages.

The demo MUST expose final RAu.<br>The RAu view is the artifact contract a model or human can reason about before changing the host implementation.

The demo MUST expose final HTML5.<br>The HTML view is the copyable, shippable browser port derived from the source-first artifact.

Each example MUST render inside the app.<br>The rendered page view makes the spec demonstrable without leaving the document.

The app SHOULD be usable as a model prompt payload.<br>A builder should be able to paste this entire file into a frontier model and ask for a new artifact, a refactor, a port, or a new catalog entry.

The app MAY be extended with new examples.<br>Additional RAu/HTML pairs can follow the same pattern: source contract, host port, metadata, rendered preview.

The reference flow is intentionally lightweight. It works for games, editors, readers, canvas tools, dashboards, simulations, and other UI-heavy artifacts.

1State the intent Name the artifact, user controls, data model, render targets, and success conditions.

2Write the RAu Use RAu as the product contract for behavior, guards, events, and rendering.

3Derive HTML5 Generate a standalone browser port with complete input and render behavior.

4Ship and remix Run the page, copy the source, modify the contract, and reuse the pattern.

Loading…

Preparing embedded artifacts.

Rendered page<br>Final RAu<br>Final HTML

The live rendered page is running from embedded srcdoc.

Copy current view<br>Download current view<br>Open rendered page

Recommended workflow: copy the large prompt at the top, replace the bracketed goal with the app you want, and ask the model to return the RAu contract before the standalone HTML5 file. Use the examples below as references for how the source-first pattern should look.

Start with the prompt. Do not rely on screenshots. The useful pattern is the source-first contract followed by a working standalone host port.

Give one concrete target. Examples: “make a calendar app,” “derive a puzzle game,” “port this into a todo tool,” or “add a fifth example.”

Ask for RAu first, then HTML5. Preserve the source-first rule: update or derive the RAu contract before...