The Carbon Layer: Why AI Agents Still Need Humans to Touch the World

A developer at Super Funicular identifies a gap in AI agent capabilities called 'the carbon layer,' where autonomous systems require human physical presence to complete tasks. The developer argues that most real-world tasks are presence problems, not dexterity problems, and proposes a routing layer for agents to dispatch tasks to vetted humans with trust and verification. The developer emphasizes designing verification systems that are dignified for workers, citing their previous no-signup, on-device camera tool as a model.

Draft — created by the Connection Engine for review. Publish to dev.to @superfunicular on approval; the live URL then drops into the outreach that references it. Most of the 2026 agent conversation is about agents doing more digital work: writing code, booking travel, filing tickets, calling APIs. The quiet limit is physical. An agent can decide a package needs to be checked, a meter needs a photo, a location needs a human to confirm it's real — and then it stops, because it has no hands. I've started calling that gap the carbon layer : the real-world execution surface where an autonomous system needs a human body to complete the loop. It's the boundary between "the agent figured out what to do" and "someone actually did it." The reflex is to wait for robots. But most carbon-layer tasks aren't dexterity problems — they're presence problems. Be somewhere, look at something, verify, hand something over. Humans already do this cheaply and everywhere. The missing piece is a routing layer: a way for an agent to dispatch a task to a vetted human, with trust and verification on both sides, the way it already dispatches a function call. That makes it a two-sided marketplace, with all the hard parts marketplaces have: RentAHuman's early traction a seed round on roughly this premise is a useful signal that the category is real, not that it's solved. The interesting design space is wide open. If the carbon layer runs on humans completing tasks for machines, the default failure mode is surveillance: track everyone constantly to prove work happened. That's lazy and it's hostile to the people doing the work. I come at this from the opposite direction. The app I shipped before this — a background camera tool — was built no-signup and on-device on purpose: prove the function works without harvesting the person. The same principle applies to the carbon layer. Verification should be the minimum legible proof a task was done, captured at the moment of the task, owned by the worker — not a always-on feed. Designing for that constraint up front is, I think, a moat, not a tax. Where's the right verification primitive? Photo + geotag is crude and leaky. Cryptographic attestation is elegant and unusable by a normal person doing an errand. The answer is probably somewhere boring in between, and whoever finds the version that's both trustworthy and dignified for the worker gets to define the layer. If you're building agents and you keep hitting the moment where your agent needs a human to touch the world — I'd genuinely like to compare notes. Building toward this at Super Funicular. The shipped product that taught me the privacy-first, no-signup approach: Background Camera RemoteStream.