# Decision-log reference fragment

Reference sample, not CI-built here. `main.c` is an application function, not a standalone complete app. Add it to an nRF Connect SDK application with the real generated C/header. The `ficus_card` stem is an example; use `runtime_name` from your package. Use Deploy's project-specific snippet for the named float32 feature array, manifest counts and class-name table.

The verified standalone exact-ordinal API is `uint16_t <runtime_name>_legal_predict(const float *)`. It returns ONLY a class ID. There is no feature-count macro or path-ID function. The application must validate non-null inputs, width, finiteness and ordered preprocessing before this unchecked call.

The default fragment prints a class-only debug line. That line is deliberately not parseable as a Field monitor path record. To enable the exact `t_ms,class_id,path_id` protocol, implement an independently reviewed graph-trace adapter with a documented stable path map bound to the same card hash, replace the example application-owned adapter declaration with its actual API, compare traced classes with the package predictor, and only then define `FICUS_HAVE_REVIEWED_PATH_ADAPTER`. Never use class ID, node count or a fabricated constant as path ID.

On a dedicated monitor stream emit the CSV header `t_ms,class_id,path_id` once before the rows. Keep the card hash, device/boot identity and mapping with the file. This protocol is distinct from the sensor capture header `# ficus-capture v1 ...`. Do not mix both streams or class-only debug messages in a monitor file. UART serialization, trace adapters and input logging add work: keep them outside a clean C1 PPK2 decision window. Only logs with actual ordered inputs can support input-range analysis; class/path-only logs do not contain those values.
