Skip to content

Home

The landing page is the public front door. It states what ai_stp is, offers the catalog, and copies the one supported install command. It does not run that command, create an account, or write a harness.

URLs and who can see them

Projection URL Who can see it
Human /{locale}/ anyone
Machine /{locale}/ai/ anyone

{locale} is en or ru. The same facts are on both projections. Signed-in visitors still see Home; the Sign-in button is hidden for them (SignedOutOnly). There is no extra landing for an authenticated session.

What this screen is for

Use Home to:

  • read the product sentence: a setup registry, not a skill dump;
  • copy uv tool install ai-stp-cli exactly;
  • open the catalog;
  • open Sign-in when you have no session.

Home does not:

  • assemble a setup;
  • detect your harness;
  • store a model key (the product never needs one);
  • start OAuth by itself (Sign-in is a separate page);
  • show personalized objects.

The workflow preview behind the hero is decorative. It is not a live status of your machine.

What is on the screen

A full-viewport hero, dark even when the rest of the site is light.

Control Label What it does
Heading The AI setup registry, not just a skill catalog product claim
Subtitle Find, verify, install, and earn on AI components. short pitch
Primary button Browse catalog goes to /{locale}/catalog
Secondary button Sign in goes to /{locale}/login; hidden when signed in
Install panel Install the CLI copies uv tool install ai-stp-cli
Copy Copy / Copied writes that string to the clipboard
Prerequisites uv, python>=3.12 what the command expects

The install hint says: run the command as written; do not assemble it yourself. The executable is ai-stp. The PyPI distribution is ai-stp-cli. uv tool install ai-stp installs a different package this project does not publish.

The Human / Machine switch stays at the bottom of the viewport. Machine Home is a short Markdown document: the title, the subtitle, a catalog link, a Documentation link, the install heading, the CLI install command, and the everyday initialize start. Documentation there points at AI_STP_USER_DOCS_URL when the presenter is given it; it is not the API OpenAPI page.

Header and footer are the shared chrome described in Web. Header Documentation is the external MkDocs host.

Keyboard:

Shortcut Action
C Contact, when saas_public_pages is on
P Account or Sign-in
Ctrl/Cmd K catalog search, on the catalog page

Matching CLI commands

Install the CLI, then start first-run discoverability:

uv tool install ai-stp-cli
ai-stp task start --intent initialize --idempotency-key initialize-session-01 --json

Expert inspect of the installed binary:

ai-stp version --json
ai-stp doctor --json
ai-stp capabilities --json
ai-stp registry search --json

version reports the running build. doctor is a read: it does not create a device. capabilities says which surfaces this build can talk to. registry search reads the public catalog without an account.

After the tool is on PATH, the next local identities are created in the CLI, not on this page:

ai-stp device init --json
ai-stp passport developer init --json

Those commands are documented in Device and Passports. Home never runs them.

Dead-ends

What you see What it means What to do
Sign-in button missing you already have a session open Account from the header
Copy does nothing the browser blocked the clipboard select the <code> block and copy it
ai-stp not found after install uv tools are not on PATH see Troubleshooting
Catalog button works, install fails Home only copies a string fix uv / Python locally
Machine view looks sparse that is the projection facts match; chrome is Markdown
Contact missing from the header self-hosted profile expected; Catalog still works

Home itself does not 404. A wrong locale prefix 404s the site shell.

If the API is down, Home still renders: it is static chrome plus the install string. The catalog behind Browse catalog may then show The service is temporarily unavailable.

What happens after install

The landing command only puts ai-stp on the machine. A setup is still selected and applied in the CLI:

Home copy → uv tool install ai-stp-cli
         → task intents --json
         → task start --intent initialize|install|…
         → follow continuations

Nothing in that chain is a website POST except later sign-in, likes, reports, and publication confirm.

Do not invent the install line

The string on the card is uv tool install ai-stp-cli. Changing the distribution name, adding a pip extra, or wrapping it in a curl one-liner is a different product.