Start with a short brief Capability
Your data brief / 01

What does your robot need to learn?

Two answers and your contact details are enough to begin. Add technical requirements only if you’re ready.

If Archive Signal could obtain one type of real-world experience your team cannot efficiently create internally, what would you ask us to capture?

Go straight to your contact details. Technical specifications can follow.

Add research context (optional)
What will this support?
Examples of a useful brief +

“Experienced technicians detecting and recovering from cross-threaded fasteners, with close-up views and final inspection.”

“Intermittent pump failures where the symptom is similar but the root cause differs. Include the tests the expert chooses and the verified repair.”

Download a sample capture brief

Only starred fields are required.
Before a brief becomes a program

Start small.
Scope it together.

What happens after I send a brief?

Drew reviews the capability gap and follows up to clarify the work, sourcing feasibility and a possible small pilot. Collection timing and volume are scoped around the actual workflow, rather than promised before access is understood.

Do human demonstrations provide robot actions?

Not automatically. Observing an expert and collecting robot-action trajectories are different requirements. Use the detailed brief to specify joint states, coordinate frames, embodiment mapping or action alignment when you need them.

Who controls the data, and where is it stored?

For a capture program, permitted uses, ownership, licence terms, worker consent, storage region, access and retention are agreed before collection. Tell us your constraints; an inquiry does not grant a data licence. The form itself stores your inquiry in Archive Signal’s Cloudflare-hosted database, as described in our privacy and intake notice.