Use Case•Built & Tested
Incident Triage Automation
Turn production exceptions into evidence-backed GitHub issues with verified release blame.
Pipeline Sequence
Error Payload
Release Blame
Diff Context
Bounded AI
Human Review
Triage Execution Steps
01
Error Ingestion
Telemetry webhook or project DSN arrives with stack trace, release SHA, and event count.
02
Release Blame
GraphQL blame queries the deployed release commit for the in-app failing line.
03
Bounded Synthesis
LLM receives diff context and formulates a technical hypothesis and 3 verification checks.
04
Human Approval
Engineer reviews draft in dashboard cockpit and confirms issue creation.
Honest Boundaries & Limitations
In adherence to our strict transparency principles, review the operational caveats of this workflow:
- •Blame identifies the author who last touched the line, which may not be the root cause.
- •Large refactors, reformatting commits, and squash merges can obscure true fault.
- •Confidence is expressed only as high or low; it is not a statistical probability.
- •Ichnois never edits code or modifies repository branches.