Incident Leaderboard
Help observe a living system. Report what breaks, confuses, or behaves strangely; verified findings earn points.
Report an incident, or reach me urgently.
Found something broken, confusing, unexpected, or simply strange? Log it. If it truly cannot wait, ping me directly.
SGA.OS shows its own wiring. Pick your level, or ignore it: everyone gets the real tools, not a watered-down version. Investigate. Play. Break things. Order is just chaos you learned to read.
No jargon: what a good report needs, in plain language.
- What happened, in one sentence.
- What you expected instead.
- The steps to reproduce it (if you know them).
- Your environment (the snapshot below collects it).
- When it happened and whether it repeats.
Plain-language glossary
Browser console: a hidden log where the page writes errors and messages (F12).
500 error: the server failed to produce the response (the site's fault, not yours).
Latency: how long a response takes to arrive, in milliseconds.
Header: lines of metadata that ride along every response (e.g. the security ones).
Non-sensitive info from your own browser. Shown here first: nothing is sent automatically.
Here you can tinker and fail without fear: everything is local, no network, no records, no alerts.
Flip the checks and watch the aggregate: it is the SAME rule the real status page uses (unknown is neutral).
See what a test report would look like, without sending it.
Just want to play? the lab games
No verified findings yet. Report something; once it is verified it appears here with points.
No release notes yet.
Part of this is open.
Selected component logic, how the pieces fit together, with private data removed. Security-sensitive spots carry clearly marked review notes, because a second pair of eyes never hurts.