dimensionalOS / dimensionalOS/dimos
PimSim: task, skill, trace, and promotion contracts
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Make agents and skills pass independently verified physical outcomes rather than successful tool calls.
Acceptance
- Version task, skill execution, intervention, verifier, trace, and artifact schemas
- Keep deployable observations isolated from privileged evaluator truth
- Record progress, timeout, cancellation, failure category, and physical postconditions
- Compare repeated candidates against named baselines
- Define pull-request, scheduled simulation, and hardware-canary gates
Synced from DIM-1386 by pim
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no implementation files, tests, or entry points. Start by mapping the task, skill execution, intervention, verifier, trace, and artifact schemas, then define how observations, evaluator truth, outcomes, baselines, and the three proposed gates satisfy the listed acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100