Back to tool

Methodology

How StairSolver generates a report

The report is generated from user measurements, stair geometry, explicit baseline rules, and source citations. It is designed to be checked later, not merely believed.

Rule version

irc-baseline-2026-07-01

The rule version is saved with the report so a future report can explain which rule snapshot produced the original result.

1. Normalize the homeowner inputs

The report stores the entered floor height, clear run, width, room width, headroom, opening length, landing, project type, and location note before drawing any conclusion.

2. Calculate stair geometry

The calculator derives riser count, riser height, tread depth, clear run needed, stringer length, cut angle, and straight or turning layout fit.

3. Run explicit baseline rules

Riser height, tread depth, headroom, opening length, stair width, landing depth, and steepness are checked against a versioned baseline rule set.

4. Attach source citations

Each risk points to a source record with code reference, publisher, rule version, official link, and a plain boundary statement.

5. Generate project questions

The report turns each flagged risk into practical questions a homeowner can ask before building, buying materials, or approving a plan.

AI boundary

AI is not the judge

AI can later help read user-uploaded notes or retrieve our source library, but the reference packet should not depend on AI inventing a code answer. The core judgment comes from stored inputs, deterministic geometry, and explicit source-linked rules.

What the report can say

Useful, but bounded

  • Keeps the exact input snapshot that produced the result.
  • Shows which measurements triggered the highest risk warnings.
  • Links warnings to source records and official references.
  • Separates normal stair checks from special stair questions.

What the report cannot claim

Where StairSolver stops