Fill in what your project can answer and what it needs to know, and this page
writes .podshl/agent.yaml and one file per solution. Press
Check with the mirror and the files are judged by the same code
that ingests them — not a copy of the rules in this page — so what passes here is
what the mirror takes.
Your draft stays in this browser. Checking sends the files to
/validate, which reads them and keeps nothing: no copy, no log line.
When they pass, put them under .podshl/ where your project is served,
and prove control at /register.
Choose your agent.yaml and the solution files it lists, all
at once. They are read by the same parser the mirror uses, and whatever this form
has no field for is kept exactly as you wrote it.
Where .podshl/ will sit — the location you prove you
control. The endpoint has to lie under it.
English is the one obligation. A reader in another language gets your words through their own model, marked as a translation.
Problem classes: one name for each kind of problem, like
pip.install.wheel-missing. A client offers these to a person, so a
solution for a class you do not list can never be reached.
Each is a fact your solutions can decide on. A reading is taken from the person's machine, with their consent, by the client — only operations from the published vocabulary, checked when your file arrives. A question is asked of the person; give it choices, or the answer never reaches you.
One file each. It answers one problem class, when the facts you name have the values you give — and all of them must hold. The text below is what a person reads; write it in English.
A feature or a file format that looks like an ordinary word. The reader's model is never shown these, so it cannot translate them.
How you may reply