DropBoxMini
DropBoxMini is the artifact distribution service within the Oryvin ecosystem.
It provides a small, reliable boundary for storing and serving derived artifacts such as delivery-patch, screenshot, and test-result outputs.
DropBoxMini is intentionally narrow in scope. It does not coordinate workflows, define operational intent, or act as a source system.
Role in the architecture
DropBoxMini sits on the derived artifact side of the system.
Typical uses include:
- storing delivery patches or result bundles prepared from source-derived work
- storing screenshots and validation evidence produced by Looker
- serving those artifacts back to operators, automation, or other consumers
Design goals
Simplicity
Artifact distribution is its job. The service remains small and focused.
Predictable storage
Artifacts are stored with enough structure and metadata to be located and retrieved consistently.
Clear service boundary
DropBoxMini separates execution from distribution. Producers generate artifacts. DropBoxMini stores and serves them.
Secure ingest
Protected artifact operations use API key based access.
What DropBoxMini is not
DropBoxMini is not:
- the source of truth
- the packaging system
- the orchestration engine
- the system that decides what should be deployed
The source of truth remains hg. Origin and other controlled flows prepare source-derived material. DropBoxMini distributes resulting artifacts.
Relationship to other components
- Origin prepares source-derived bundles
- Looker uploads evidence artifacts
- Orchestrator may publish results or consume stored outputs
- Infrastructure and operators retrieve artifacts when needed