FICUS , home
Reflex Lab · Tools & agents
Reflex Lab / Integration bench

Tools & agents

Readable agent skills, firmware references and measurement helpers. Know what you can use now—and what still needs a connected service.

Downloadable does not mean measured.
File sizes describe these checked-in downloads Verified. Firmware and PPK2 helpers are reference samples, not CI-built or physically tested here. New Reflexes do not inherit catalog measurements.

Agent skills

Inspect first · act with approval
AI agent skillAvailable

nRF Connect SDK integration

Teach a coding agent to inspect the actual Reflex package, integrate CMake/Kconfig, preserve feature order, replay probes on the DK and prepare a scoped PPK2 run.

How to use with your coding agent

Download SKILL.md and add it to your agent’s project context. For a skills-aware setup, place it in the agent’s project skills directory as ficus-ncs-integration/SKILL.md. Claude Code commonly uses .claude/skills/. For Cursor or Copilot-style workflows, attach the file explicitly and ask the agent to follow it.

Prompt for your coding agent
Read ficus-ncs-integration/SKILL.md first.
Inspect my SDK version, DK revision and package header.
Use the actual runtime_name and manifest feature order.
Show the changes before flashing. Replay package probes
on the DK, and report unbuilt or unmeasured steps honestly.

The skill is available; SDK installation, generated packages and board verification remain your project’s work.

Review workflowAvailable

Review a Reflex before shipping

Use the exactness and deployment guides as an agent review checklist. Keep source identity, float32 contract, label map and target evidence separate.

Evidence-bound review prompt
Check this Reflex against its matching manifest and receipt.
Report feature order, class map, numeric scope and API.
Distinguish host replay from DK replay and PPK2 charge.
Do not infer production approval or inherit catalog numbers.
List missing probes, target resources and measurements.
Read the review guide

This is a copyable review workflow, not a second installed agent skill.

Browser workspace · no firmware download required.

Firmware

Build locally with nRF Connect SDK
Zephyr sample appReference sample

UART capture firmware

Stream a generic Zephyr temperature sensor, or an explicitly named synthetic signal when none is ready. Default target intent: nRF54LM20 DK; UART at 115200 baud.

Build command — verify your board qualifier first
west boards
west build -b nrf54lm20dk/nrf54lm20b/cpuapp ./capture-firmware
# Read README and authorize overwriting the app before west flash.

Exact browser capture protocol: optional # ficus-capture v1 channels=… rate_hz=…, then t_ms,v0,v1,…. Read the README before choosing a sensor or flashing.

Zephyr integration fragmentReference sample

Decision-log firmware fragment

Publish a real class and, only with a reviewed graph-trace adapter, a real path ID for the Field monitor. This is distinct from the sensor capture stream.

Field log row — requires actual path mapping
/* After a reviewed trace adapter supplies the path ID: */
printk("%lld,%u,%u\n", (long long)k_uptime_get(),
       (unsigned)class_id, (unsigned)path_id);
/* Header: t_ms,class_id,path_id. Log outside C1 timing. */

The standalone C API returns only a class. No path-ID function is exported; path logging stays disabled until the application provides one. Use Deploy for project-specific float32 arrays and class tables.

Measurement

Charge first · voltage qualified
Python reference outlineReference sample

PPK2 decision-window runner

Capture current and a GPIO marker with the open-source ppk2-api package. Integrate complete windows and divide charge by the declared number of decisions.

Reference invocation — inspect wiring and README first
python3 -m pip install ppk2-api
python3 measure.py --port /dev/ttyACM1 \
  --calls-per-window 10000 --marker-channel 0 \
  --sample-rate-hz 100000 --voltage-v 3.0 \
  --voltage-evidence assumed --output capture-001

Batch short calls. The sample rate argument does not configure the PPK2. Charge is integrated from current; energy uses an assumed constant 3.0 V unless a separate constant-rail record is supplied. No physical validation is claimed.

Preflight checklistAvailable

Measurement readiness

Use before attaching a trace to a project. These checks are a planning aid, not a readiness certificate. Checkboxes are not persisted.

Read C1 method & caveats

C1: processed float features in RAM → published class, CPU only. Acquisition, DSP, radio and verbose logs are outside that boundary.

Browser workspace · no firmware download required.

Browser tools

Local inspection · rows stay here
Data → CaptureAvailable

Device capture

Record a permitted serial device into a local project, label the recording and save a dataset version. Requires Web Serial support and a secure context or localhost.

No editable local project yet. Create one, then open Data → Capture.

Create or open a project

Rows stay in the browser unless you explicitly authorize a transfer.

Browser workspace · no firmware download required.

Reflex catalogAvailable

Receipt & exact replay

Inspect a public Reflex’s provenance and follow its literal decision path on finite float32 inputs. Replay verifies the recorded graph, not real-world accuracy or fresh board timing.

Open Reflex catalogWhat “exact” means

Browser workspace · no firmware download required.

Local decision diagnosticsAvailable

Field monitor

Import device logs to inspect class and path distributions. Range checks require logged inputs. An unlabeled shift is not an accuracy measurement; remote fleet ingest needs service.

Open Field monitorDecision log contract

Browser workspace · no firmware download required.

CLI & API

Needs service
Planned interfaceNeeds service

FICUS CLI

Planned commands mapped to the v3 endpoint registry. The CLI is not shipped or installed here; these commands are not currently executable.

Planned commands — not an installed CLI
ficus capabilities
ficus session create --request reviewed-session.json
ficus session status SESSION_ID
ficus package create --request package.json
ficus package download PACKAGE_ID
ficus monitor ingest --request decision-records.json
ficus capabilitiesGET /v1/capabilities
ficus session create --request reviewed-session.jsonPOST /v1/sessions
ficus session status SESSION_IDGET /v1/sessions/{session_id}
ficus package create --request package.jsonPOST /v1/packages
ficus package download PACKAGE_IDGET /v1/packages/{package_id}/download
ficus monitor ingest --request decision-records.jsonPOST /v1/monitor/ingest
Read service & API docs

No executable or service artifact available from this tile.

Service integrationNeeds service

REST API contract

The contract defines consent-bound sessions, verified packages, size reports, board requests and remote ingest. An endpoint registry is not evidence that those services are deployed.

Planned same-origin capabilities request
# When the service is connected, from your Lab origin:
curl "$LAB_ORIGIN/api/lab/svc/v1/capabilities"
# GET is public in the contract; feature availability is authoritative.
# Do not place tokens in URLs or invent a service origin.

Private build workflows exist in the repository. The unified v3 service is being connected; hosted board queues and remote monitoring are separate dependencies.

Endpoint registry & release limits

No executable or service artifact available from this tile.

Reviewed 6 November 2026 · Skills and references are inspectable artifacts, not autonomous approval to install, flash or upload data.