admin343/run
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify live relay run logging

Browse Source
This commit is contained in:
npc0-hue
2026-09-01 14:23:58 +08:00
parent c8f5213954
commit 65da73eff0
8 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
protocol/artifact.md
+4 -4
View File
@@ -1,6 +1,6 @@
# Run Artifact Contract
Artifacts move files and large payloads between platform and run without blocking logs or control.
Artifacts move files and large payloads between platform and run without blocking current live logs or control.
## Implemented Routes
@@ -34,9 +34,9 @@ Run stores unacknowledged `ArtifactChunkUploadRequest` payloads in the local art
- Transfers must be resumable.
- Transfers must be checksummed.
- Artifact concurrency must be limited.
- Artifact transfer must not block control heartbeat, job ack/result, or log upload.
- Artifact transfer is lower priority than control, job lifecycle metadata, and durable log ingest.
- Slow or retrying artifact chunks must not prevent log spool acknowledgement cleanup or terminal job result submission.
- Artifact transfer must not block control heartbeat, job ack/result, or current live log relay.
- Artifact transfer is lower priority than control, job lifecycle metadata, and current live log relay.
- Slow or retrying artifact chunks must not delay live log relay or terminal job result submission.
- Control, job, and log routes must reject artifact chunk payloads or transport details rather than accepting them through lightweight channel payloads.
Run artifact queues use owner-only atomic JSON entries and retain chunks until an exact transfer/artifact/index acknowledgement covers them. A low-priority uploader retries pending chunks independently of control, jobs, and logs.