UVU v18

The evidence ledger

Prepared 20 September 2026 · A standalone document, re-publishing what is published at uvu.com.tr


Status, stated once. UVU is pre-incorporation. There is no revenue, no customer, no certification and no installed base. The aperture is at laboratory readiness and has never been installed in a real vessel. The signal-processing cores are authored and, until the verification programme publishes, unverified.

The core ledger, graded by evidence

The six-core readiness ledger
CoreReadiness as cataloguedRole in the product
firSource plus testbenchConditioning and decimating the digitised beat or acoustic signal
fftSource plus documentationBeat frequency into range bins; spectral features for vibration
cfarSource plus documentationAdaptive-threshold detection
streaming interconnectSource onlyBack-pressure and instrumentation taps
interface bridgeSource plus documentationTo be re-scoped to an industrial fieldbus
integration top levelSource plus testbenchEnd-to-end chain integration

One of the six is source only. We publish the grading because an inventory that hides its weakest rows is not an inventory.

What does not exist yet

As of our own engineering audit of May 2026: no core had ever been simulated and none had been synthesised. No constraint files existed anywhere. There is therefore no clock frequency, no logic utilisation, no DSP-block count and no power figure for any core. Five defects are logged. Two datasheet figures were found not to be present in the source, and are being corrected.

This is the reason the verification programme exists, and it is why this site has no specifications page. There are no specifications to state yet.

The published defect list

The published defect list
RefItemStatus
BUG-FIR-1Documentation describes a structure the implementation does not matchMarked fixed — unverified
BUG-FIR-2Dead accumulatorMarked fixed — unverified
BUG-FFT-1Illegal declaration inside a case statement — a blocker; the design will not elaborateOpen
BUG-FFT-2Bit-growth sizing; unused parameterOpen
BUG-CFAR-1Leading and lagging sumsMarked fixed — unverified
DOC-1Two datasheet figures not present in the sourceCorrection in progress
REPO-1Two copies of the integration top level divergeResolved in weeks 1–2

The schedule

The verification programme schedule
WeeksDatesWork
1–25 – 18 Oct 2026Toolchain, one-command regression, repository consolidation
3–419 Oct – 1 NovSimulate fir against its golden model; close two defects
5–62 – 15 NovSimulate fft; close the elaboration blocker; correct the datasheet
7–816 – 29 NovSimulate cfar; re-parameterise for an industrial clutter profile
9–1030 Nov – 13 DecEnd-to-end chain bench
11–1214 – 27 DecTiming constraints; synthesise for an AMD Artix-7 XC7A100T; record frequency, utilisation, DSP-block count and power with tool version and settings stated
1328 Dec – 3 Jan 2027Reissue every datasheet, each figure carrying its basis
—by 15 Jan 2027Publish

The rule for every figure

Every published figure carries its basis: the device and its speed grade, the tool and its version, the settings, and whether timing was met and by what margin. A number without its basis is worse than no number, because it invites a question the company cannot answer and turns a technical conversation into a credibility problem. Until a figure can be published with its basis, it is labelled a design target pending test and evaluation — or it is not published. The golden reference models and the testbenches are available for technical due diligence under a non-disclosure agreement.

Every table and paragraph here is published on the site and can be checked page by page: the core ledger and the May 2026 audit at https://uvu.com.tr/en/signal-processing.html, the defect list, the schedule and the rule for every figure at https://uvu.com.tr/en/verification.html. This document contains no claim that is not on the site. Questions, including sceptical ones: engagement@uvu.com.tr