Task
Pick a tabletop cube and release it fully inside a declared target region.
Applications open
REPRODUCTION SPRINT-01
Reproduce one policy.
Publish what happens.
Join a focused two-week collaboration around a pinned ACT policy for SO-101. Successful, failed, blocked, and unsafe attempts all improve the shared record.
ArtifactACT SO-101 Pick-and-PlaceImmutable upstream revision
You contributeOne bounded roleRun, independently review, or coordinate
You receiveAttributable public creditReviewed evidence and a durable contributor record
CommitmentTwo weeksShared protocol, async updates, and published outcome
READINESS · ONE HONEST STATUS
Recruiting before kickoff
Applications are open. An application is private and does not become a public commitment until the participant, configuration, protocol, reviewer, and event lead are confirmed.
0/3minimum teams confirmed
0/2independent reviewers confirmed
Openevent lead
Kickoff remains provisional.
KnownRobot will only confirm kickoff after the minimum roster, physical setups, reviewers, lead, and matching protocol consent are documented.
Machine-readable operating record →01 / PINNED ARTIFACT
ACT SO-101 Pick-and-Place
Everyone works from the same immutable revision. The upstream publisher has not endorsed this sprint, and the artifact is not treated as compatible until evidence is contributed.
- Revision
19b56a188f1c9ec578ddd07c058b12dd980b23ff- Framework
- ACT / LeRobot
- Target
- SO-101 tabletop pick-and-place
02 / SHARED PROTOCOL
Agree before counted trials.
Consent binds the exact policy revision, protocol, schedule, and declared configuration. Teams publish every counted outcome; physical and simulated results remain separate.
Protocol digest: b93300ff3f40c336b4cdc1732e35b4e3011380e6e10978770758232679e83aa6
Success
Cube released fully inside the target before the declared timeout, without human contact, emergency stop, or safety violation.
Reset
Publish cube dimensions, target dimensions, start pose and reset procedure before counted trials. Restore that declared start state for each trial.
Trials
Declare timeout and at least ten planned trials before running. Record every counted attempt, success, intervention, exclusion, deviation and first decisive failure. Blocked or unsafe attempts may complete zero trials.
Configuration
Before trials, commit robot, gripper, cameras, calibration method, compute, framework and dependency versions, observation/action shapes and control rate beside robot-skill.yaml. Link immutable revisions. Changes require a separately labeled cohort, never pooled counts.
Safety
Each team owns its risk assessment, safe operating envelope and emergency stop. No people in the envelope. Stop unexpected or uncertain motion; never bypass limits or safety controls.
Comparison
Compatibility study, not a leaderboard or physical safety certification. Preserve failed and withdrawn attempts; separate simulation from physical results. Review grants no registry verification status.
03 / PROVISIONAL SCHEDULE · AMERICA/DENVER
Every milestone has an accountable gate.
- Applications openTracked in the public operating record.
- Applications closeTracked in the public operating record.
- Roster + protocol freezeOnly proceeds after the readiness gate passes.
- Kickoff — only if readyOnly proceeds after the readiness gate passes.
- Every team outcome dueTracked in the public operating record.
- Independent review dueTracked in the public operating record.
- Public results sessionTracked in the public operating record.
- Joint report + improvementsTracked in the public operating record.
04 / NATIVE APPLICATION
Choose one useful role.
Apply without leaving KnownRobot. Applications remain private during review. Accepted participants explicitly approve the configuration and profile details that become public.
- Team: run and document a physical or simulated attempt.
- Reviewer: independently inspect another team's protocol and evidence.
- Event lead: coordinate gates, dates, and the public results loop.
Sign in to apply
Your account keeps the application attributable and lets you return to its status. Application details remain private unless you are accepted and consent to publication.
Sign in and continue →New to KnownRobot? Create an account.
05 / COMPLETE THE LOOP
Every outcome becomes useful evidence.
Accepted teams document their exact setup, trials, interventions, failures, and safety stops. Independent reviewers assess the record before KnownRobot publishes the joint report.