Reachable
Homepage, robots.txt, agent.md, and OpenAPI returned 200 to every declared client.
Reference case · Signmos S0 · 27 Aug 2026
Before changing the product, freeze what an agent can reach.
This is the natural Signmos baseline before any public-content, discovery, metadata, or agent-resource intervention. Auditmos operates both Signmos and ProofSurface.
Paths checked11
Successful4
Missing7
Client differences0
Observable facts
The public buyer surface and operational surface were asymmetric.
Missing
Pricing, security, privacy, terms, sitemap, llms.txt, and Agent Card returned 404.
Null result
The planned client-dependent status difference did not appear. All seven declared clients saw the same status pattern.
Interpretation
Operational documentation carried more detail than buyer-facing HTML.
The agent guide and OpenAPI exposed authentication, human review, rate limits, retention eligibility, deletion behavior, and document workflow details. The homepage did not expose public price, operator, legal, privacy, terms, or broad security evidence.
Boundary
Source asymmetry is not yet buyer-agent behavior.
The controlled model runs are still pending. Until they are recorded, the sparse buyer surface supports a source-level interpretation—not a claim about what a named agent retrieved, used, or decided.
Published correction
The earlier 403 observation was not reproduced.
The controlled run returned 200 for the homepage and operational resources and 404 for missing routes. Current evidence cannot attribute the earlier 403s to an active WAF rule or general buyer-agent blocking.
Still unknown
S0 remains open until the evaluation layer is recorded.
- Consumer-product answers, citations, omissions, and repeat stability.
- A pinned API model run with the captured source supplied directly.
- Provider-specific indexing and confirmed third-party crawl or ingestion.
- External platform request logs and the exact Signmos production commit.