Milestones

List view

• Direction

  Longer-horizon bets on where ForeFire is most differentiated: European case generation, a browser build, and ensembles as burn probability.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Onboarding: users can build a case

  The gap between "the Aullene demo works" and "my own fire runs". Mostly documentation and small Python tooling; the highest ratio of adoption gained to effort spent.

  No due date

  •2/3 issues closed
  66% complete1 open2 closed

• Security posture

  Hardening the HTTP command server and stating explicitly what exposure ForeFire is and is not designed for.

  No due date
  0% complete0 open0 closed

• Correctness and code health

  Memory safety, physics correctness, warnings, sanitizers and test coverage. The work that keeps the engine trustworthy as the session and free-threading refactors land.

  No due date

  •3/10 issues closed
  30% complete7 open3 closed