Current build priorities.
Veldarium is early and active. This log keeps the public posture honest: what is being developed next, what is still illustrative, and where partner or backer alignment could accelerate the work.
These are public build priorities and planned proof objects. They are not customer wins, shipped production claims, or promises of availability.
Why it matters / Retired old route sprawl and rebuilt the public surface around the four-system company thesis. Old URLs permanently redirect to current thesis pages.
Next / Hold the line: no surface re-introduces a services framing.
Why it matters / The preview now shows intake, workflow object, risk flags, a human gate, proof artifact, audit trail, and next action for each system.
Next / Replace synthetic boards with a pilot operator's real workflow.
Why it matters / First proof object: intake flags, household fit, placement risk, and follow-up in one reviewable record. This is the wedge that earns the rest of placement operations.
Next / Validate fields and risk language with a shelter or rescue partner.
Why it matters / Batch + SOP-drift control is the wedge for licensed operators where a missed drift becomes a failed test or an inspection finding.
Next / Pin the SOP-band and packet model with a licensed operator.
Why it matters / Supplier variance is invisible margin loss. The exception board quantifies impact and routes a recovery action for buyer approval.
Next / Scope a variance pilot with one purchasing-heavy operator.
Why it matters / Blocked work tied to material, inspection, crew impact, and next owner. Public language stays bounded until yard workflow scope is validated.
Next / Pressure-test the blocker model with yard execution input.