rollback
shallowru.layero/layero · Verify this server
Put the previous working build back on the live address. CHANGES WHAT VISITORS SEE — ask the person before calling unless they asked for a rollback explicitly. The action is reversible (you can roll forward again), but the time visitors spent on the wrong version cannot be taken back. ⚠️ For apps (`ssr_next`, `node_web`, `python_web`, `streamlit`, `gradio`, `flask`) a rollback works differently from static sites and is often impossible: an app has no ready artifact to simply switch to. If the platform refuses, explain that to the person plainly and suggest rebuilding the earlier commit — do not repeat the call.
1 trials · measured 15 days ago
rollback scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against ru.layero/layero, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-09-23 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/31c6af5d-4337-48f2-b577-e9e996882ec1)