Module content 

What the front page says, as data.

The heading, the line on how for each system, the prompt for each system, the guide the prompt sends an agent to (served at /agent.txt), the Studio frame’s shelf, the comparison, what comes with LOGOS and the FAQ live here rather than in the markup, so they read and review in one place and every line that states a fact about LOGOS carries the suites that prove it. landing_page in logicaffeine_tests holds every suite to existing, every command in the guide to the released largo and to this tree’s, every address to a file or page the site serves, and the page to showing exactly the text the copy button copies.

Modules

said

What the page says only once the reader acts.

Structs

Card

One card of the comparison: a kind of work, what it is usually done with, and what LOGOS does there.

Claim

One sentence the page states, and what backs it.

Faq

A question the front page answers.

LibraryFigures

The standard library’s figures: the prelude’s module count, read from the loader, and the parity ledger’s correctness figures and upstream languages, read from the ledger as it is checked in (benchmarks/parity/PARITY_LEDGER.md), so the page can never say a number the ledger does not.

Usually

A tool a kind of work usually reaches for, named as its own site names it, and the page where it says so (shown nowhere on the page).

Enums

Evidence

What backs a line of the page./// What backs a line of the page.

Install

How largo installs: the shell script on macOS, Linux and every phone’s agent, PowerShell on Windows.

Line

One line of the agent instructions.

Status

Where what a card says stands: in the released largo, in the Studio, in part, or in the next release (this tree, ahead of the release a reader installs today).

System

A system a reader copies the prompt for: one button each, with the system’s mark. macOS and Linux share the shell install; Windows has PowerShell’s.

Uses

What a card’s line leans on in largo: a command, or a target of largo emit.

Constants

AGENT_GUIDE_URL

The guide the prompt sends an agent to before it writes: the instructions, served whole (public/agent.txt, which landing_page holds to instructions_text byte for byte).

CLONE_SOURCE

The command that clones the source, with its examples and docs, for an agent to read.

COMPARE_HEADING

COPY_LABEL

The button below the heading, which copies the instructions.

CRATES_URL

The page that lists the crates the language is built from, one per part.

HEADING

The heading: the promise, then the two things that come with it. The user’s words (2026-10-01).

INSTALL_HEADING

The box above the buttons for a reader who installs largo by hand: its heading and the command for each kind of system, as the pricing page states them.

INSTRUCTIONS_ID

The element that shows the instructions, which the copy button names.

LIBRARY_HEADING

SERVE_URL

Where largo serve puts the site: its default port, on the reader’s own machine.

SYNTAX_MATRIX

The language on one page: the forms an agent writes, one construct a line, drawn from the quickguide’s tables (teach_parity holds the guide to the lessons, doc_examples runs the docs). The guide carries it under step 4, and the heal worker’s prompt carries the same lines (services/heal/src/primer.js, held equal by landing_page), so the model that mends a program knows the language it mends (the user, 2026-11-02).

Functions

compare

The comparison: eight kinds of work, each with what it is usually done with and what LOGOS does there as of 0.11.0, every line proven by the suites it names, and no claim of a win over anything. A card tagged for the next release leans on a command or an emit target the released largo lacks; as of 0.11.0, none does.

compare_lead

The line under the comparison’s heading: what the cards are.

every_claim

Every line the page states with its evidence: the guide’s sentences and rules, the line on how for each system, the comparison’s lead and cards, the library’s lines and features, and the FAQ’s answers.

faq

features

What 0.11.0 brings, a line each, ten words or fewer, each proven by the suites it names.

how

The one line below the heading on how to use LOGOS: the whole of what the page tells a reader to do, since the prompt itself only copies (the user, 2026-10-31).

install_commands

instructions

The guide the prompt sends an agent through: install, a website on the reader’s screen inside a few minutes, then the language, the site, programs, logic, math and hardware, each where it lives in the released largo, and how the two of them work (Tristen, 2026-11-01, DAT-105: get them up, running and building, with a starter site, and point them at the source). Every command runs on the release the install script installs.

instructions_text

The instructions as one text: what the page shows and what the copy button copies.

library

The standard library in two lines, each with the figures it quotes.

library_figures

prompt

The five lines a person pastes into their coding agent, for install: what this is, the source on GitHub first, the install that runs on the reader’s system, and the guide to follow, which ends with a site running. Plain and agent agnostic (Tristen and the user, 2026-11-01, DAT-105).

prompt_text

The prompt as one text: what the page shows and what the copy button copies.

shelf

The front page’s Studio frame: one shipped example for each kind of work the comparison names, in the Studio’s own folders, opened on the website in a website (the user, 2026-10-01). The Logic example is a theorem with its givens, so a first visit’s Prove has something to prove from (the user, 2026-11-01).