Sole Mat — human test

Zero to “I have a site working.” Nothing here assumes you know how it was built.

pass/fail objective your judgment only you can answer unverified I could not test this

1. Open control.mat.brokerpass/fail

   Expected: a page headed “Give your manuals a proper home” with a “Sign in with Sole Account” button. Verified live at 08:01.

   If this fails: stop and tell me. The product itself is down.

2. Click “Sign in with Sole Account”pass/fail

   Expected: you land on account.sole.computer with a single email field and a “Send magic link” button, and text saying an account will be created for you if you don’t have one. Verified live at 08:01.

   If it dead-ends or errors: stop and tell me what you saw.

3. Type your email, click “Send magic link”pass/fail your judgment

   Expected: a confirmation that mail was sent.
   Judgment, separate from pass/fail: was the wording clear to you as someone arriving with no context?

4. Check your inbox and click the link — within 15 minutesunverified

   I have no inbox, so this is the step most likely to surprise you. Expected: the mail arrives in the inbox, not spam. If it lands in spam, that is itself worth reporting — note it and carry on.

   If no mail after a few minutes: stop and tell me, rather than requesting link after link.

5. You should land back on control.mat.broker, signed inpass/fail unverified

   Expected: a working control panel — some page past the sign-in screen, not an error. I have never seen this page; I hold no session.

   If you get an error, a blank page, or a stuck redirect: stop and tell me exactly what appeared.

6. Find the way to create your own sitepass/fail your judgment unverified

   A brand-new account should land in a create flow, not a claim flow — claiming is for a site made before you signed in, which doesn’t apply starting from zero.
   Expected: you end up owning one site, at its own address under mat.broker. That address will be an unpredictable string of characters, not a name you chose — that is deliberate, not a bug.
   Judgment: is it obvious what just happened, and where your site is?

7. Add a document sourcepass/fail unverified

   The product is built around PDF/manual documents, not hand-written content. Look for a way to point it at a sitemap, a PDF collection page, or a single PDF URL.
   Expected: a document appears, with its own public page.
   No PDF handy? Ask me and I’ll give you a safe public one.

8. Open that document’s public pagepass/fail your judgment unverified

   Expected: a readable page presenting the document, reachable without being signed in — this is what a stranger sees if you send them the link.
   Judgment: does it look like “a proper place to land” for a manual, as the product claims — or does it look generic and unfinished?

9. Change how the site looks, and reload the public pagepass/fail unverified

   Not the document’s content — the site around it. Expected: your change takes effect and is visible on reload, with no separate “publish” step and no waiting.