FICUS , home
Reflex Lab · Docs

Projects and stages

How a project carries data, sessions, Reflexes, measurements and packages as one evidence chain.

On this page

A project is the evidence container

A project binds an objective, task, target and budgets to dataset versions, preparation settings, sessions, measurements and deployments. It is not just a folder for a model file. That binding lets you answer a practical question: does this accuracy, graph, firmware package and current trace belong to the same decision system?

A dataset version identifies imported bytes and column metadata. A preparation specification records split and feature-processing intent. A session is one named run with settings and results. Selecting a different session changes the result under inspection; it does not rewrite older sessions. Measurements attach to a Reflex identity, while deployments record the selected session and artifact they package.

DataPrepareTrainResultsMeasureDeploy
A project keeps each stage attached to the dataset version and selected session. Completing one stage does not grant the evidence of another.

What each stage owns

StageEngineering question
DataWhich rows, labels, features and independent cohorts do we have?
PrepareWhat split, float32 conversion and signal/window contract will we use?
TrainWhich method and settings produced this session?
ResultsHow does it perform, and which literal path produced an answer?
MeasureWhat was actually built, timed and integrated on the board?
DeployWhich package and evidence should the application consume?

The stages are connected, not interchangeable. Graph node count is not firmware flash. A host compiler receipt is not MCU latency. An uploaded current trace without a firmware/workload binding does not establish a Reflex’s decision charge. An energy budget remains unverified until the relevant measurement is attached.

Train from data, compile compatible source and compose Reflexes have different input requirements. A teacher-import or broad search option may need service capabilities beyond the browser baseline. Do not assume every task selector enables the same local algorithm.

Preserve versions and notice stale evidence

Changing the active dataset or preparation settings can make a session stale. Keep the old session as evidence of its old inputs, then run a new session for the changed contract. Changing a Reflex also means rechecking its package, class map, measurements and field baseline. Do not silently relabel an earlier result as belonging to the new graph.

Projects and dataset metadata are stored locally. Dataset rows and larger graph payloads live in IndexedDB. Clearing site storage, changing browser profiles or exhausting storage can make rows unavailable. A project export records metadata and provenance, not a backup of the raw CSV. Retain the exact input files, holdout and generated package in your own controlled storage.

Service credentials and signing keys do not belong in a portable project. Account access is separate from compiler connectivity: signing in does not by itself make a build lane available. When the service is unavailable, local inspection should remain useful and queued work should not be fabricated.

Coming from Nordic Edge AI Lab

The concepts are familiar even though the names differ. Nordic’s Solution maps to a Reflex Lab Project. A Model training session maps to a Session in Train. Model observability maps to Results for replay and local diagnostics, plus the Field monitor for imported device observations. Both approaches need a consistent input contract and a verified deployment handoff.

Nordic conceptReflex Lab workspace
SolutionProject: objective, data, target and evidence chain.
Model training sessionSession: method, settings, split and candidate result.
Model observabilityResults + Field monitor: graph replay and device-record diagnostics.

For an Instinct, each Reflex keeps its own labels and route. Sharing one library is not permission to merge unrelated output classes. Reflexes sharing an input event must agree on ordered feature meaning and units, not merely the number of columns. Composition savings and checked routing have their own measurement boundary; they cannot inherit individual-Reflex comparator factors.

Last reviewed .

Source of truth: published facts in content/public.ts; CURRENT_MEASURED_RESULTS.md; CONNECTED_BUILD_WORKFLOW.md; standalone C emitter and v3 endpoint contract. Reference examples are not physical-board test receipts.

On this page