Spaces:
Running
Running
|
Download README.md from SrihariV/stack-failure-drill: direct link, hf CLI and curl.
- Browser
- Download file 997 Bytes
-
https://huggingface.co/spaces/SrihariV/stack-failure-drill/resolve/main/README.md
- Command line
-
hf download hf://spaces/SrihariV/stack-failure-drill/README.md
-
curl -L -o README.md https://huggingface.co/spaces/SrihariV/stack-failure-drill/resolve/main/README.md
997 Bytes
| title: "Stack Failure Drill: break your revenue stack safely" | |
| emoji: 🚦 | |
| colorFrom: red | |
| colorTo: gray | |
| sdk: static | |
| app_file: index.html | |
| pinned: false | |
| license: mit | |
| short_description: Fail a tool in your GTM stack and watch the leads queue | |
| tags: | |
| - revops | |
| - simulation | |
| - resilience | |
| - gtm | |
| # Stack Failure Drill | |
| A fire drill for your revenue stack. Draw your go-to-market stack as a metro map (or pick a company size from startup to mega-corp, up to 250 tools), fail one tool for a few hours, and watch the leads queue. You'll see which departments get cut off, which service targets break, and how much pipeline is at risk. | |
| - Runs entirely in your browser. Nothing is uploaded. | |
| - Discrete-event simulation validated against closed-form queueing results (M/M/1, M/M/2, M/D/1 within 5%). | |
| - Printable incident report, runbook (Markdown) and Slack digest. | |
| Main demo: https://iamsrihari.com/projects/stack-failure-drill/demo · Code: https://github.com/MayaDispeler/stack-failure-drill | |