rFabric

Documentation

Documentation Overview

This documentation is written for robotics teams evaluating whether rFabric can become the operating system behind their data, model, release, and field workflows. Start with the system shape, then drill into the rules that make it trustworthy.

What Mature Robotics Teams Evaluate

System of record strength

Can the platform connect datasets, curation ruleset, training runs, promoted models, releases, fleets, and field incidents in one queryable graph?

Deployment safety

Can teams govern promotion, staged rollout, rollback, maintenance, and teleoperation with the same policy model and audit trail?

Incremental adoption

Can the platform coexist with ROS, LeRobot, storage systems, visualization tools, and existing training or release infrastructure?

Operating economics

Can teams understand the storage, compute, and fleet cost profile of the workflows they are putting on the platform?

Recommended Reading Order

  1. Read the architecture to understand the stable system shape.
  2. Read principles and lineage to understand what makes that shape trustworthy.
  3. Read the build sequence to understand what exists now versus what deepens next.
  4. Use quickstart, workflow, and integration guides to evaluate adoption fit for your team.