Production Smoke
This is the fastest “is the system actually live” check after deploying:
- universalmanifest.net (standards/spec/docs)
- myum.net resolver (resolver contract)
The command examples below use the reference tooling in this repository. Teams may use equivalent tooling if they verify the same contract conditions and keep auditable output.
Continuous monitoring reference (repo policy + workflow):
docs/operations/SYNTHETIC-MONITORING-SLO-POLICY.md.github/workflows/synthetic-monitoring.ymldocs/operations/INCIDENT-REPORT-TEMPLATE.md
One command (recommended)
Section titled “One command (recommended)”From the TS helper package:
cd packages/universal-manifest && npm run smoke:endpoints:prod
Staging check (recommended before production promotion)
Section titled “Staging check (recommended before production promotion)”cd packages/universal-manifest && npm run smoke:endpoints:staging
This checks:
- docs site endpoints including Sandbox and Resolver + 404 page
- published spec artifact URL(s), e.g. v0.1 context
- resolver health endpoint and well-known endpoint
- resolver
ETag+ 304 revalidate semantics - resolver headers per contract (incl. exposed headers for browser tooling)
If production doesn’t have the default UMID seeded
Section titled “If production doesn’t have the default UMID seeded”The smoke script defaults to:
urn:uuid:11111111-1111-4111-8111-111111111111
If your production resolver does not serve that UMID, pass a known UMID:
cd packages/universal-manifest && node scripts/smoke-endpoints.mjs --mode prod --docs-base https://universalmanifest.net --resolver-base https://myum.net --umid 'urn:uuid:YOUR-UMID-HERE'