Patryk Porebski

Robotics | AI | Full-Stack. Building: at @fdotinc

[Patryk Porebski @pporebski]

Impress your girlfriend, show her your gbrain setup

[Patryk Porebski @pporebski]

Yes. A lot of robotics software pain is not in the model. It is in the middleware, data plumbing, and the long chain of brittle handoffs between collection, processing, labeling, training, and deployment.

Coding models can clearly reduce the cost of writing that glue. That helps. But we still need the underlying workflow and interfaces to be explicit, repeatable, and operable when sensors, schemas, and hardware change.

That is the part I think robotics is still missing. Not just faster script generation, but shared infrastructure for the boring path from robot data to deployed updates.

[Patryk Porebski @pporebski]

@arian_ghashghai Arguable.

Claiming that building software for hardware is a terrible idea right now is like claiming that the phone was only about telephony, not software.

The irony here is that it is exactly software that will enable actual robot deployments at scale.

[Patryk Porebski @pporebski]

@garrytan @demishassabis Literally yesterday I finished building my own voice layer over GBrain, because I needed it so much. Glad it’s now built in natively!

[wildiris @wildiris19]

Regarding humanoid form-factor robots:
• A critical issue, completely lost in the current hype and rush to market, is that the people who will be selling, operating, servicing and maintaining field-deployed robots in the future, will by necessity be the same people that are doing those jobs now as regards to farm, construction, marine, oil-field, logging, or mining equipment.
• In other words, any robotic system deployed in the field, that requires the additional technical support of a team of Stanford University engineering graduate students, is a commercial nonstarter.
• Or to put it another way, the current crop of humanoid robots are completely neglecting the questions of design for manufacturing, operation, service, and maintenance. All absolutely critical elements for any robotic system to ultimately be commercially viable in the field.
• What a field-deployed robot needs to be is modular. Its mechanical construction needs to be based on interchangeable subassemblies.
• And its computational architecture should come in the form of pre-programmed bricks or modules connected together using a single shared serial interface to form a system of distributed intelligence.
• This form of construction allows for easy manufacture, easy maintenance, and easy service. Programming is not part of this paradigm. If one wants to change some functionality in a robot, just swap in a different module.
• The upside of this kind of construction is that this is the level of service, maintenance, and rebuild competency that already exists within the workforce currently employed in the industries of farming, construction, marine, oil-field, logging, and mining.

[Patryk Porebski @pporebski]

That's exactly right. A robot that needs Stanford grads to operate is research. A robot that a field crew can operate, repair, calibrate, and maintain is a product.

Few people are thinking about this now. Most are focused on making the thing work, not how to operate it at scale.

https://t.co/b0th1OvAdq

[Patryk Porebski @pporebski]

Introducing rFabric.

Most robotics teams spend 80% of their time rebuilding internal tools and brittle data pipelines.

We’re changing that.

rFabric is the control plane for robot fleets. One platform for connectivity, telemetry, remote operation, and the end-to-end data-to-deployment loop.

Focus on robot behavior, not infrastructure.

[Patryk Porebski @pporebski]

@KuphDev @fdotinc Appreciate it! I’ll definitely share more soon - already have something interesting that I can’t wait to show.

[Patryk Porebski @pporebski]

I'm attacking robot fleets, at scale @fdotinc

https://t.co/iFFulibqUF

[Patryk Porebski @pporebski]

Introducing rFabric.

Most robotics teams spend 80% of their time rebuilding internal tools and brittle data pipelines.

We’re changing that.

rFabric is the control plane for robot fleets. One platform for connectivity, telemetry, remote operation, and the end-to-end data-to-deployment loop.

Focus on robot behavior, not infrastructure.

[Patryk Porebski @pporebski]

@pruthvigeedh_ @Neuracore_AI There is soooo sooo much to do in this space, isn't it?

[Patryk Porebski @pporebski]

Introducing rFabric.

Most robotics teams spend 80% of their time rebuilding internal tools and brittle data pipelines.

We’re changing that.

rFabric is the control plane for robot fleets. One platform for connectivity, telemetry, remote operation, and the end-to-end data-to-deployment loop.

Focus on robot behavior, not infrastructure.

[Patryk Porebski @pporebski]

@humblelee71 Maybe not the biggest, but important for sure…

[Patryk Porebski @pporebski]

We help companies like Lucen Robotics to focus on what matters the most - robot behavior.

[Linyan Fu @Linyan_Fu]

Introducing Lucen.

Autonomous Retail Shop Robot for EVERY grocery store.

Restocking shelves & Picking online orders are done by robots🤖.

Building @fdotinc

[Patryk Porebski @pporebski]

DevOps -> MLOps -> RobotOps

[Patryk Porebski @pporebski]

RobotOps!

[Patryk Porebski @pporebski]

@the_smart_ape You can just make your life easier (no wasted tokens for html generation):

https://t.co/Pq4vetqIM2

[Patryk Porebski @pporebski]

Just dropped this nice little thing: mdshelf.

Turn any folder of Markdown files into a fast, beautiful, browsable site.

Point it at OpenClaw, Hermes, GBrain, wikis, notes, docs, whatever - mount each one under its own private URL and consume them anywhere.

[Patryk Porebski @pporebski]

@itsolelehmann Add this to your stack. You will not regret it.

https://t.co/Pq4vetqIM2

[Patryk Porebski @pporebski]

Just dropped this nice little thing: mdshelf.

Turn any folder of Markdown files into a fast, beautiful, browsable site.

Point it at OpenClaw, Hermes, GBrain, wikis, notes, docs, whatever - mount each one under its own private URL and consume them anywhere.

[Patryk Porebski @pporebski]

@KSimback No need to waste tokens to generate html files on existing md.

https://t.co/Pq4vetqIM2

[Patryk Porebski @pporebski]

Just dropped this nice little thing: mdshelf.

Turn any folder of Markdown files into a fast, beautiful, browsable site.

Point it at OpenClaw, Hermes, GBrain, wikis, notes, docs, whatever - mount each one under its own private URL and consume them anywhere.

[Patryk Porebski @pporebski]

@trq212 Markdown output is optimal for a reason. You may try some middle ground solution (I created it for myself, anyone free to use):

https://t.co/Pq4vetqIM2

[Patryk Porebski @pporebski]

Just dropped this nice little thing: mdshelf.

Turn any folder of Markdown files into a fast, beautiful, browsable site.

Point it at OpenClaw, Hermes, GBrain, wikis, notes, docs, whatever - mount each one under its own private URL and consume them anywhere.

[Patryk Porebski @pporebski]

@chesterzelaya great, congrats! I'm curious what's the tech stack behind controling them all from single machine?

[Patryk Porebski @pporebski]

@pham_blnh @livekit for sure! I already have full monitoring, telemetry and remote robot operation implemented as part of rFabric. Fully remote, over public network, 30ms latency. Insane. Stay tuned!