| 00 |
Chapter 00: Welcome to Ricochet |
What Ricochet is, how the guide is organized, and why postfix order matters. |
| 01 |
Chapter 01: Your First Program |
How to run the smallest useful Ricochet script. |
| 02 |
Chapter 02: Running Code and Getting Feedback |
How to use rco run, rco repl, help, and diagnostics. |
| 03 |
Chapter 03: How Postfix Reads |
How to trace postfix code and use the starter stack vocabulary. |
| 04 |
Chapter 04: Values, Literals, and Inspection |
How to recognize and inspect runtime values. |
| 05 |
Chapter 05: Names, Bindings, and Small Data |
How to use bindings, arrays, and maps to keep stack code readable. |
| 06 |
Chapter 06: Numbers, Math, and Truth |
How postfix arithmetic, comparisons, assertions, and conversions work. |
| 07 |
Chapter 07: Strings, JSON, and Regex |
How to process strings, JSON, and regex results. |
| 08 |
Chapter 08: Collections |
How to use arrays, maps, sets, ranges, mutation, and block-based collection words. |
| 09 |
Chapter 09: Results and Errors |
How explicit Result values model success and failure. |
| 10 |
Chapter 10: Making Decisions and Reusing Code |
How conditionals, loops, blocks, and functions shape programs. |
| 11 |
Chapter 11: OOP and Dispatch |
How classes, accessors, methods, and dispatch work. |
| 12 |
Chapter 12: Testing, Linting, and Formatting |
How tests, linting, and formatting create a feedback loop. |
| 13 |
Chapter 13: Introspection And Debug Basics |
Once programs have names, data, functions, and tests, you need tools for seeing what the runtime sees. Introspection and debugging make stack behavior observable instead of mysterious. |
| 14 |
Chapter 14: Date, Time, And Duration |
Dates and durations are common in reminders, logs, packages, sessions, and release workflows. This chapter teaches time as data before you use it inside larger applications. |
| 15 |
Chapter 15: Async And Tasks |
Async work lets a program wait for several things without turning every wait into a blocking pause. The important beginner model is that a task is a value you can start, wait on, and reason about. |
| 16 |
Chapter 16: Capabilities And Sandboxing |
Host capabilities are the safety boundary between Ricochet code and your machine. You should understand that boundary before reading files, calling HTTP, opening sockets, or launching processes. |
| 17 |
Chapter 17: Files, Workspaces, Environment, Config, And Secrets |
Useful scripts often need configuration, files, environment variables, and secrets. Ricochet treats those as explicit host interactions that should be scoped and checked. |
| 18 |
Chapter 18: HTTP And Streams |
HTTP connects Ricochet programs to services. Streams let programs handle data progressively instead of pretending every response is a small string. |
| 19 |
Chapter 19: TCP And WebSocket Sockets |
Raw sockets and WebSockets are lower-level network tools. They are powerful, so this chapter emphasizes explicit hosts, loopback practice, and cleanup. |
| 20 |
Chapter 20: Processes And PTYs |
Process and PTY control lets Ricochet coordinate external tools. This is high-trust host power, so the chapter teaches deliberate opt-ins and clear boundaries. |
| 21 |
Chapter 21: Terminal UI |
Terminal UIs are local applications with visual state. The same stack and collection habits now drive frames, rows, keys, and cleanup. |
| 22 |
Chapter 22: Webview And Desktop GUI |
Desktop GUI work introduces a browser-like surface while keeping your application local. The key model is data flowing between Ricochet and a webview document. |
| 23 |
Chapter 23: MVC First App |
MVC apps are the first large application shape in the guide. Routes, controllers, views, and models are easier when you see them as named layers around the same Ricochet language. |
| 24 |
Chapter 24: Routes, Controllers, And Responses |
Routes turn HTTP requests into controller actions. This chapter teaches how requests become data and how controller methods return responses. |
| 25 |
Chapter 25: Templates, Static Assets, And Uploads |
Templates and assets turn controller data into user-facing pages. Uploads add a host-resource boundary, so the chapter keeps size, path, and cleanup concerns visible. |
| 26 |
Chapter 26: Data, Active Record, And Migrations |
Persistent data requires a stronger mental model than maps in memory. Models, migrations, and records connect Ricochet objects to database state. |
| 27 |
Chapter 27: Sessions, Forms, Auth, And Passwords |
Forms and sessions are where web apps meet user identity. This chapter teaches the flow without hiding password and session safety behind magic. |
| 28 |
Chapter 28: AI Capabilities And The AI Package |
AI features are application boundaries: prompts, providers, transcripts, tool permissions, and fallback behavior. The safest model is explicit capability, explicit provider, explicit result. |
| 29 |
Chapter 29: Packages, Imports, And Dependencies |
Packages let Ricochet projects reuse code. Imports, manifests, locks, verification, and audit commands keep reuse understandable and reproducible. |
| 30 |
Chapter 30: Registries, Publish, Yank, And Mirror |
Registries turn packages into shared artifacts. This chapter teaches local registry practice before public publishing concerns. |
| 31 |
Chapter 31: Macros And Expansion |
Macros generate code before runtime. They are powerful, so the chapter teaches ordinary functions and packages first, then introduces expansion as a deliberate tool. |
| 32 |
Chapter 32: Debugger, DAP, LSP, And Editor Tools |
Large projects need editor feedback, traces, breakpoints, and diagnostics. This chapter shows the professional tooling surface around Ricochet programs. |
| 33 |
Chapter 33: Bytecode, Images, And Source Emission |
Bytecode and images are runtime artifacts. Understanding them helps you separate source, compiled code, saved VM state, and emitted source views. |
| 34 |
Chapter 34: Packaging, Release, And Updates |
Release work turns a working app into something another person can install. Packaging, signatures, metadata, and update channels are part of that handoff. |
| 35 |
Chapter 35: Capstone CLI Tool |
The CLI capstone combines data, results, files, tests, and reporting into a complete command-line tool. |
| 36 |
Chapter 36: Capstone TUI Dashboard |
The TUI capstone combines terminal rendering, data loading, tests, and safe cleanup into a complete local dashboard. |
| 37 |
Chapter 37: Capstone MVC App |
The MVC capstone combines routes, controllers, views, data, migrations, seeds, and tests into a complete web application. |
| 38 |
Chapter 38: Capstone Packaged GUI App |
The final capstone combines GUI state, local data, tests, and packaging into a desktop-style application you can hand to someone else. |