Artifact Publish Workflow

This document defines how Orchestrator publishes artifacts to DropBoxMini.

The workflow converts automation outputs into standardized artifacts that can be delivered, stored, and retrieved through the DropBoxMini delivery service.

This workflow implements the artifact contract defined in:

Architecture → Artifact Contract

Purpose

The publish workflow exists to:

standardize how artifacts are produced
ensure consistent delivery to DropBoxMini
reduce custom delivery logic inside automation tasks
record artifact publication results

This allows Orchestrator to focus on workflow coordination while DropBoxMini handles artifact transport and storage.

High-level workflow

The publish sequence is:

generate output
↓
package artifact
↓
generate manifest
↓
publish to DropBoxMini
↓
record result

Flow representation:

Orchestrator
↓
artifact generation
↓
manifest creation
↓
upload to DropBoxMini
↓
artifact stored

Publish command model

The canonical publish command should resemble:

orchestrator artifact publish
--system weic
--type patch
--version 0358
--path build/weic_patch_0358.zip

Arguments:

system
owning system producing the artifact

type
artifact category (patch, build, doc, config)

version
artifact version or patch number

path
local file or bundle to upload

Optional fields may include:

description
human readable description

metadata
additional structured metadata

Artifact packaging

Artifacts should be packaged as a single zip bundle containing:

artifact.zip
├ manifest.json
└ payload/

Payload contains the files produced by the workflow.

The manifest provides metadata describing the artifact.

This structure simplifies transport and storage.

Manifest generation

Before upload, Orchestrator generates a manifest file.

Example:

{ "artifact_id": "20260315-001", "type": "patch", "system": "weic", "producer": "orchestrator", "created_utc": "2026-03-15T18:12:00Z", "description": "WEIC patch 0358", "version": "0358", "files": [ "payload/weic-api.patch" ] }

Fields:

artifact_id
unique identifier

system
producing system

type
artifact category

producer
typically orchestrator

created_utc
timestamp of creation

version
patch or build identifier

files
list of payload files

Upload transaction

Artifacts are uploaded to DropBoxMini using:

POST /api/artifacts

Headers:

X-API-Key

Body:

multipart/form-data

Parts:

manifest
artifact bundle

Example request:

POST /api/artifacts X-API-Key:

multipart/form-data manifest = manifest.json artifact = artifact.zip

Response handling

DropBoxMini returns a response describing the storage result.

Example:

{ "status": "stored", "artifact_id": "20260315-001", "path": "/dropbox/weic/patches/0358" }

Orchestrator should record:

artifact_id
storage path
timestamp
publish status

This information should be written to the workflow execution log.

Failure handling

Possible failure conditions include:

authentication failure
invalid manifest
missing payload
unsupported artifact type
storage failure

Orchestrator should record failure details and mark the workflow as failed.

Retry behavior should be configurable but should not automatically repeat indefinitely.

Logging

Each publish operation should log:

workflow id
artifact id
artifact type
target system
upload status
response path

This provides traceability for automation operations.

Responsibilities

Orchestrator responsibilities:

create artifacts
generate manifest metadata
package bundles
publish artifacts
record publication results

DropBoxMini responsibilities:

validate upload requests
store artifacts
expose retrieval paths
return storage status

This separation keeps workflow coordination and artifact transport independent.

Relationship to the Oryvin system

This workflow is a core integration point in the Oryvin architecture.

Documentation and intent ↓ Orchestrator workflow ↓ artifact generation ↓ DropBoxMini delivery ↓ target system consumption

This pipeline enables Oryvin to move from documentation-driven intent toward automated operational change.

Architecture → Artifact Contract
Architecture → Component Map
Infrastructure
WEIC
DropBoxMini