Active Work

Status: active Scope: project-wide Type: planning Last reviewed: 2026-05-16

Purpose

This page tracks the current execution picture for Buffalo Wings. It should stay short enough to answer “what should I work on next?” once plan.md has pointed you at the relevant workstream.

Now

  • keep closing the remaining airfoil fit and diagnostic gaps needed for a genuinely stable Phase 0 airfoil foundation

  • keep the public docs aligned with what the code can actually construct, validate, and export

  • keep the design and development docs organized so active planning does not disappear into architecture notes

Next

  1. Fit-quality diagnostics for CST and spline-oriented fitting paths.

  2. Splipy-oriented fit generation and reporting for supported airfoils.

  3. Point-defined airfoil support only insofar as it directly unblocks fitting and downstream wing workflows.

  4. Continued wing-canonical maturation on top of the stabilized airfoil API.

Sensitivity Track

The airfoil sensitivity architecture is still in the design-plus-prototype stage.

Near-term sensitivity work should be:

  1. decide whether the current prototype interface and registry should be kept, revised, or replaced,

  2. define the smallest CST-first vertical slice for public sensitivity support,

  3. document the parameter naming and packed-layout contract before expanding implementation breadth,

  4. avoid scattering one-off sensitivity helpers across families before the shared API is settled.

Documentation Track

  • keep architecture docs focused on active system design

  • keep planning docs short and execution-oriented

  • keep external inspiration and capability inventories under docs/research/

  • archive superseded plans aggressively once the code and active docs have moved on

Recently Finished

  • public camber-curve extraction for constructable airfoils

  • named document-level open curves for airfoil camber, spline, and polyline cases

  • improved documentation structure separating architecture, planning, foundations, and development checklists

  • roadmap update reflecting that the Buffalo Panel handoff is functionally in place

Watch List

  • any remaining Buffalo Panel local shims that should be documented or retired

  • scope creep in the roadmap or architecture docs

  • attempts to start GUI-heavy work before fitting and diagnostics are ready