Daily Dispatcher Real Mode

The ATLAS daily dispatcher has moved from a guarded analysis mode to a real operating mode.

This matters because a security publication that describes evidence, approval, and operational controls should expose its own automation evidence. The daily cycle now attempts the full chain: signal review, editorial decision, web validation, Git publication, Bluesky publication, and operational mail.

What changed

The default dispatcher flags now enable the real path:

• editorial apply
• build validation
• Git publication
• social draft preparation
• Bluesky publication
• operational mail
• external search when a configured command exists

Concept-candidate registry writes remain separate. They still require explicit authorization because turning a daily signal into approved conceptual doctrine is a governance decision, not a publication convenience.

Evidence expected from each run

A complete run should leave:

• a dispatcher JSON and Markdown report under 05-INFORMES/atlas/logs;
• per-job reports under 05-INFORMES/atlas/state/logs;
• daily signal, review, decision, and action files under 05-INFORMES/atlas/state;
• a build log when validation or publication runs;
• publication reports for Git, Bluesky, and mail.

The important test is not that every external service always succeeds. External services can fail. The important test is that each invocation is attempted, bounded, logged, and reviewable without exposing secrets.

Boundary

Real mode does not authorize secret inspection, credential changes, DNS changes, Cloudflare operations, or bulk email. It authorizes the existing daily chain to invoke its configured publication, Bluesky, and mail integrations and to record the outcome.

Real publication test — 2026-07-07

This update records the first controlled full-publication test after the ATLAS automation suite was rechecked on 2026-07-07. The test intentionally exercises the public-action band with validation, Git publication, Bluesky, and operational mail enabled.

The purpose is operational evidence: ATLAS should leave a public content change, a release manifest, channel contracts, and enough audit trail to inspect the result after the run.