Skip to content

docs: j30 storage respect (robotics owns edge disk) - #56

Merged
ajwharton merged 1 commit into
mainfrom
docs/j30-storage-respect
Jul 30, 2026
Merged

ajwharton merged 1 commit into
mainfrom
docs/j30-storage-respect

Conversation

@ajwharton

Copy link
Copy Markdown
Owner

Summary

Anvil must not treat the j30 as a training/log sink.

  • Robotics owns j30 ops and on-device retention
  • Anvil path = capped pull → lab pack → lab train → small export back
  • Red line in start.md; notes in edge-export, datasets-robotics, models, handoff, converter + jetson backend docstrings

Ops note (not in repo)

Session live_pull/ left during prior Anvil capture was removed from the device.

Test plan

  • Docs/scripts only; CI should stay green
  • After merge: Anvil agents default to pull-off, not grow ~/vision/out

Codify that the house robot is ops-owned by robotics: no Anvil log dump,
capped rsync snapshots, lab-side packs/train only. Clean policy in start,
edge-export, datasets-robotics, and j30 converter docstring.
@ajwharton
ajwharton merged commit a5c8c96 into main Jul 30, 2026
1 check passed
@ajwharton
ajwharton deleted the docs/j30-storage-respect branch July 30, 2026 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant