Decision: Argus Dedicated CI Agent

Context

The CI pipeline is now mechanically automated through Hermes cron, but the daily and weekly jobs still run in no-agent mode and deliver stdout through the default Athena Telegram gateway. That keeps the system functional, but it does not satisfy the operating model: Athena is CEO and supervisor, not the daily CI analyst.

Arijit wants a separate male CI agent with its own personality, expertise, workspace, and future Telegram bot/channel.

Decision

Create Argus as the dedicated Competitive Intelligence agent.

Argus owns the CI operating loop. Athena supervises Argus and receives quality/escalation signals. Arijit will create the dedicated Telegram bot, and the bot name should match the agent name.

Why Argus

Argus is short, memorable, vigilant, and fits a competitive-intelligence watchtower role without sounding like a generic SaaS feature name.

Runtime Status

• Hermes profile slug: argus.
• Workspace: Competitive Intelligence.
• Skill: competitive-research.
• Dedicated Telegram bot: pending token from Arijit.
• Current cron mode: keep existing no-agent jobs active until the dedicated bot token exists.

Boundary

Do not pause or migrate the working daily/weekly cron delivery until the dedicated Argus bot token is configured and smoke-tested. Current delivery is operational and should not be broken just to satisfy structure.

Activation Sequence

1. Create Argus profile and soul.
2. Update CI workspace docs and skill docs to name Argus as owner.
3. Verify Argus can answer through the Hermes profile.
4. Keep current daily and weekly cron jobs active.
5. When Arijit provides Argus bot token: - add token to the argus profile env, - start Argus Telegram gateway, - create or migrate daily/weekly cron jobs under the Argus profile/channel, - smoke-test Telegram delivery, - pause default Athena-delivered CI cron only after Argus delivery succeeds.

Quality Loop

After every scheduled run, Argus should validate:

• Was the run scheduled?
• Did provider preflight pass?
• Did collection run?
• Did synthesis run?
• Were Markdown/HTML artifacts written?
• Did dashboard publish run?
• Did Telegram delivery happen?
• Were weak raw-change findings suppressed?
• Did the output answer what happened, why it matters, evidence, owner, and next action?

Failures become action items or Athena escalations, not silent fallback text.

Consequences

• CI now has a named operator and voice.
• Athena's CEO role is protected.
• The working cron stays stable until bot token setup.
• The next structural gap is Telegram/channel activation for Argus.