Reconstruct incidents
Read logs, chat messages, memos, generated clues, and reports to infer the facts that existed before the system rewrote them.
about / μ-text
public record
company dossier
Troubleshooting AI-generated software failures after the company has already called them features.
μ-text Systems operates inside a software company where most code is generated, most dashboards are trusted, and most incidents become your problem after everyone else has stopped answering chat.
You play as Andy, a new operator in the Troubleshooting Department. Your job is to reconstruct broken facts from generated logs, corporate messages, incident reports, and quietly contradictory internal tools.
work type
Incident reconstruction
Incident triage, clue reading, contradiction hunting, and workplace unease.
primary console
Corporate terminal suite
Part Slack, part Grafana, part broken enterprise suite nobody is allowed to replace.
mystery layer
Something knows too much
The logs are wrong in useful ways. The archive remembers things the company does not.
operator duties
active
Maintain reconstruction grids
Use structured marks to track certainty, contradictions, and plausible explanations.
Navigate the company
Move through internal archives, operator screens, incident dashboards, and corporate documents that are more revealing than intended.
Follow the unease
Notice when Bob is evasive, when a report contradicts itself, and when the tooling starts behaving like it has a personnel file.
system access
current clearance
available
- Landing dashboard, operator record, incident queue, and lore archive.
- Training incident records with operator marking grids.
- Logs, chat transcripts, status indicators, and incident reports.
restricted
- Solver certification is pending review by Systems Assurance.
- Personnel records remain read-only from this console.
- Ambient terminal channels are listed but unavailable during onboarding.
departments
internal map
Troubleshooting
Where operators reconstruct incidents after automated remediation makes them narratively unstable.
Archive
Where approved company memory is stored, indexed, redacted, and occasionally ahead of schedule.
Continuity
A department that appears in reports more often than it appears in the building directory.
sample company telemetry
sanitized
about::
08:11 brand health dashboard reports "quietly excellent"
about::
08:24 generator renamed three bugs to differentiators
about::
08:37 archive checksum changed without file modification
about::
08:42 onboarding queue assigned Andy J.
about::
09:04 tutorial incident began referring to itself as solved
communications policy
employee-visible
incident language
Internal reports prefer precise nouns, quiet verbs, and a calm refusal to admit when the system has made a new category of problem.
employee morale
Bob's calm delivery is considered a stabilizing resource, despite multiple unresolved requests to define stabilizing.
mystery underneath
The company is not openly sinister. It is organized, documented, monitored, and wrong in ways that keep getting more specific.