Available
The homepage and three technical files were available in all seven checks.
Verification package
Signmos reference case
One product, documented in stages. This navigation keeps the current stage and its published artifacts together.
The measurement report expires. The summary and public JSON digest remain as the durable record.
Signmos before changes.The first public record.
We recorded the public state of Signmos before making changes. Auditmos operates Signmos and this test. This checks the method; it is not independent proof of demand.
See the resultPlaces checked11
Available4
Missing7
Result differences0
Result
Four resources were available. Seven were missing.
Missing
We found no pricing, security, privacy, or terms pages. The sitemap and two agent files were also missing.
Same result
Each of the seven ways of checking the site showed the same result.
What it means
Buyer information was incomplete.
The technical files said more than the product page. Price, operator details, and pages about security, privacy, and terms were still missing.
What it does not prove
We do not yet know what an AI agent will do.
This test checked whether public resources were available. It does not prove that an agent found, understood, or used them.
Correction
We did not confirm the earlier blocking result.
In the repeated test, the available resources responded in all seven checks. We have no evidence that Signmos broadly blocks buyer agents.
See the full record and the next test plan
Public evidence record
You can check the result without opening the code repository.
This page is the permanent record for people. The public JSON file keeps the time, observers, page results, hashes, rendered-view evidence, hypothesis status, unknowns, and key limits.
- Record
- Signmos S0 / 20260829T094225Z
- Captured
- 29 Aug 2026 · 09:42:25 UTC
- Observer
- Website check 0.4.0 + Browser Run · Cloudflare · WAW
- Method
- surface-snapshot/0.4.0 + visual-capture/0.2.0
- Evidence ceiling
- Reachable
- Ownership
- Auditmos operates this program and Signmos
The service report and its rendered images stay online until 28 Sep 2026. This page and the public JSON digest remain the permanent record.
S0 work status
What we proved, what comes next, and what cannot start yet.
Each stage has a clear status. Capturing the site does not complete the AI tests or prove that a planned change worked.
- 01Complete
S0 public pages recorded
We recorded eleven resource concepts, including bounded buyer-page searches, before changing Signmos.
- 02Complete
Result and correction published
The latest 0.4 run recorded four reachable and seven missing concepts plus six rendered views.
- 03Pending
Planned buyer-agent tests
We still need full, saved tests from named AI products and one fixed API model.
- 04Gated
Make the suggested changes
Do not link a Signmos content change to this method until the AI tests are fixed and recorded. If a test is missing, state that choice.
- 05Waiting
Repeat after deployment
We will publish a result only after we confirm the changed version and repeat the same test.
Before → recommendation → after
Keep the starting record. Do not replace it with a promise.
The left side shows what S0 found. The middle lists the suggested change. The right side stays Pending until we deploy the change and repeat the same test.
| Area | S0 · observed | Suggested change | After the change · measured |
|---|---|---|---|
| AreaBuyer information | S0 · observedNone of four bounded searches found a reachable buyer page. They tried 10 pricing, 7 security, 8 privacy, and 8 terms candidates. | Suggested changePublish standard web pages for the offer, price, security limits, privacy, and terms. | After the change · measuredPending — we have not measured a Signmos change. |
| AreaDiscovery | S0 · observedrobots.txt worked. sitemap.xml was missing. The homepage exposed no same-origin buyer-page links in the captured metadata. | Suggested changeAdd a sitemap, canonical URLs, accurate social data, and internal links before testing agent files. | After the change · measuredPending — confirm page access and outside platform requests separately. |
| AreaProduct fit | S0 · observedThe homepage gave four tasks equal weight. It did not name one target customer, a price, or key limits. | Suggested changeLead with one buyer need, honest limits, the operator's identity, and one clear next step. | After the change · measuredPending — repeat the same vendor test. |
| AreaOperational evidence | S0 · observedagent.md and OpenAPI had more detail than the buyer pages. | Suggested changeLink technical facts to clear buyer pages. Do not treat a working API as proof that the product is ready to buy. | After the change · measuredPending — test whether answers cite more supported facts. |
| AreaAgent behavior | S0 · observedUnknown: S0 model evaluations are not complete. | Suggested changeRun and save the planned AI product and fixed-model tests before changing Signmos. | After the change · measuredNot ready — without this step, we cannot link later results to the change. |
Still unknown
The agent tests still need to be recorded.
- Answers, citations, missing facts, and repeat consistency in named AI products.
- A fixed API model tested with the saved sources supplied directly.
- Whether each provider indexed the pages or requested them from Signmos.
- Outside platform request logs and the exact Signmos production commit.
Connected article
The explanation and the evidence link to each other.The article explains why buyer agents need a chain of evidence. This case shows the first real record. The protocol explains how we will run the missing AI tests.