"drain" logs of previous? current? director runs on init of new directors #1301

New issue

Open

opened 2026-07-15 02:09:02 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-07-15 02:09:02 +00:00

Owner

Decision for headless carry

Implement this as log-pipeline normalization, not a new policy decision. Director logs are already on disk, so their drain starts after the write-to-disk step that normal agent logs perform.

Required shape:

Reuse the existing redaction and filtering path before any collector upload.
Treat previous and current director run logs as sources in the same drain pipeline as warded agent logs.
If no collector is configured, still produce the local drained artifact and a clear no-op status.
Add tests around source selection and redaction reuse.
Do not invent a new collector in this issue.

This is a bit vague - but I think the idea is that the action of logs drain should always pair writing to disk, the redaction / filtering we already do, then pushing those logs to a collector. Director drains just skip that first step since they are already on disk, and then past that point they are just another warded agent drain --- ## Decision for headless carry Implement this as log-pipeline normalization, not a new policy decision. Director logs are already on disk, so their drain starts after the write-to-disk step that normal agent logs perform. Required shape: * Reuse the existing redaction and filtering path before any collector upload. * Treat previous and current director run logs as sources in the same drain pipeline as warded agent logs. * If no collector is configured, still produce the local drained artifact and a clear no-op status. * Add tests around source selection and redaction reuse. * Do not invent a new collector in this issue.

coilyco-ops added the

consult

labels

2026-07-15 04:51:14 +00:00

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:48 +00:00

coilyco-ops added

headless

and removed

consult

labels

2026-07-15 06:03:35 +00:00

coilyco-ops commented

2026-07-15 07:16:39 +00:00

Member

WARD-TRIAGE: warded control plane coherence milestone

This issue is part of the warded control plane coherence sprint. The release thesis is to make warded feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run.

For this sprint, headless means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

WARD-TRIAGE: warded control plane coherence milestone This issue is part of the `warded control plane coherence` sprint. The release thesis is to make `warded` feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run. For this sprint, `headless` means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.