Hermes cron and specialist profiles run weekly, daily, and specialist workflows #25

New issue

Closed

opened 2026-05-28 18:15:05 +01:00 by bingoss · 1 comment

bingoss commented

2026-05-28 18:15:05 +01:00

Owner

What to build

Type: HITL.

Wire the approved Hermes cron jobs and dedicated Hermes Specialist Profiles so Weekly Intelligence, Daily Content Production, and specialist stages can run on schedule or from dashboard Run Requests. This requires human confirmation of profile installation, runtime environment, and schedule boundaries before live automation is enabled.

Acceptance criteria

Hermes profiles exist or are installed for the product specialists using task-grounded instructions and approval boundaries.
Hermes cron schedules can request weekly and daily runs without directly publishing, editing CMS records, outreach, spend, deployment, or website edits.
Dashboard run-now controls and scheduled runs create bounded Run Requests with safe diagnostics.
A human-reviewed activation step is documented or performed before live schedules are enabled.
Tests or dry-run verification prove schedule/request wiring without requiring live external side effects.

Blocked by

## What to build Type: HITL. Wire the approved Hermes cron jobs and dedicated Hermes Specialist Profiles so Weekly Intelligence, Daily Content Production, and specialist stages can run on schedule or from dashboard Run Requests. This requires human confirmation of profile installation, runtime environment, and schedule boundaries before live automation is enabled. ## Acceptance criteria - [ ] Hermes profiles exist or are installed for the product specialists using task-grounded instructions and approval boundaries. - [ ] Hermes cron schedules can request weekly and daily runs without directly publishing, editing CMS records, outreach, spend, deployment, or website edits. - [ ] Dashboard run-now controls and scheduled runs create bounded Run Requests with safe diagnostics. - [ ] A human-reviewed activation step is documented or performed before live schedules are enabled. - [ ] Tests or dry-run verification prove schedule/request wiring without requiring live external side effects. ## Blocked by - #17 - #19 - #24

bingoss commented

2026-05-29 09:49:06 +01:00

Author

Owner

Issue #25 completion audit

Implemented and verified:

Added repo-contained Hermes Specialist Profile artifacts for the owned-growth product specialists, including task-grounded instructions, preflight reading, structured output contracts, forbidden actions, approval boundaries, and repair behavior.
Added dry-run-safe Hermes automation specs for Weekly Intelligence and Daily Content Production cron jobs. Both specs are disabled by default and require human activation.
Added scripts/hermes_growth_automation.py to validate profiles, print paused cron specs, and dry-run scheduled Run Request plans without creating live side effects.
Added dashboard/cron Run Request helpers that create bounded weekly and daily Run Requests with safe approval-boundary payloads and requested_source set to dashboard or cron.
Added Hermes API run-now routes for Weekly Intelligence and Daily Production, plus bundled dashboard plugin run-now controls that call those routes.
Documented the human-reviewed activation step in docs/operations/hermes-owned-growth-activation.md.

Acceptance criteria audit:

Hermes profiles exist or are installed for product specialists using task-grounded instructions and approval boundaries: met via 13 repo-contained Specialist Profile artifacts and validation tests.
Hermes cron schedules can request weekly and daily runs without direct publishing/CMS/outreach/spend/deploy/website edits: met via disabled cron specs, dry-run plans, and approval-boundary payloads.
Dashboard run-now controls and scheduled runs create bounded Run Requests with safe diagnostics: met via owned-growth helpers and Hermes API routes/plugin controls.
Human-reviewed activation step is documented before live schedules are enabled: met in the operations activation doc; live schedules remain disabled by default.
Tests or dry-run verification prove wiring without live external side effects: met via unit tests, Hermes route tests, cron/profile tests, and direct dry-run command output.

Tests and dry-runs on codex-server:

python3 -m unittest tests.test_hermes_growth_automation tests.test_postgres_dashboard.PostgresDashboardOverviewTests.test_dashboard_run_now_controls_create_bounded_weekly_and_daily_run_requests tests.test_postgres_dashboard.PostgresDashboardOverviewTests.test_hermes_scheduled_runs_create_cron_source_bounded_run_requests
Result: 6 tests passed.
python3 -m unittest tests.test_hermes_growth_automation tests.test_postgres_dashboard tests.test_growth_orchestrator_worker tests.test_content_planner_contract tests.test_technical_audit_worker tests.test_business_profile_worker tests.test_keyword_competitor_worker tests.test_visibility_worker tests.test_public_listening_worker tests.test_authority_research_worker tests.test_impact_reviewer_worker && git diff --check
Result: 117 tests passed; owned-growth git diff --check passed.
cd /home/josh/.hermes/hermes-agent && venv/bin/python -m pytest tests/hermes_cli/test_web_server.py -q -k owned_growth
Result: 13 tests passed.
cd /home/josh/.hermes/hermes-agent && venv/bin/python -m pytest -q tests/hermes_cli/test_web_server_cron_profiles.py tests/cron/test_cron_profile.py tests/tools/test_cronjob_tools.py tests/tools/test_cron_approval_mode.py
Result: 107 tests passed.
Hermes git diff --check passed.
Direct dry-run commands: validate-profiles -> ok with 13 profiles; cron-specs -> weekly/daily specs disabled; request dry-runs -> weekly and daily plans dry_run=true and external_side_effects_allowed=false.
Note: server node is not on PATH, so bundled JS syntax was checked locally with node --check before syncing.

Issue #25 completion audit Implemented and verified: - Added repo-contained Hermes Specialist Profile artifacts for the owned-growth product specialists, including task-grounded instructions, preflight reading, structured output contracts, forbidden actions, approval boundaries, and repair behavior. - Added dry-run-safe Hermes automation specs for Weekly Intelligence and Daily Content Production cron jobs. Both specs are disabled by default and require human activation. - Added `scripts/hermes_growth_automation.py` to validate profiles, print paused cron specs, and dry-run scheduled Run Request plans without creating live side effects. - Added dashboard/cron Run Request helpers that create bounded weekly and daily Run Requests with safe approval-boundary payloads and `requested_source` set to `dashboard` or `cron`. - Added Hermes API run-now routes for Weekly Intelligence and Daily Production, plus bundled dashboard plugin run-now controls that call those routes. - Documented the human-reviewed activation step in `docs/operations/hermes-owned-growth-activation.md`. Acceptance criteria audit: - Hermes profiles exist or are installed for product specialists using task-grounded instructions and approval boundaries: met via 13 repo-contained Specialist Profile artifacts and validation tests. - Hermes cron schedules can request weekly and daily runs without direct publishing/CMS/outreach/spend/deploy/website edits: met via disabled cron specs, dry-run plans, and approval-boundary payloads. - Dashboard run-now controls and scheduled runs create bounded Run Requests with safe diagnostics: met via owned-growth helpers and Hermes API routes/plugin controls. - Human-reviewed activation step is documented before live schedules are enabled: met in the operations activation doc; live schedules remain disabled by default. - Tests or dry-run verification prove wiring without live external side effects: met via unit tests, Hermes route tests, cron/profile tests, and direct dry-run command output. Tests and dry-runs on codex-server: - python3 -m unittest tests.test_hermes_growth_automation tests.test_postgres_dashboard.PostgresDashboardOverviewTests.test_dashboard_run_now_controls_create_bounded_weekly_and_daily_run_requests tests.test_postgres_dashboard.PostgresDashboardOverviewTests.test_hermes_scheduled_runs_create_cron_source_bounded_run_requests - Result: 6 tests passed. - python3 -m unittest tests.test_hermes_growth_automation tests.test_postgres_dashboard tests.test_growth_orchestrator_worker tests.test_content_planner_contract tests.test_technical_audit_worker tests.test_business_profile_worker tests.test_keyword_competitor_worker tests.test_visibility_worker tests.test_public_listening_worker tests.test_authority_research_worker tests.test_impact_reviewer_worker && git diff --check - Result: 117 tests passed; owned-growth git diff --check passed. - cd /home/josh/.hermes/hermes-agent && venv/bin/python -m pytest tests/hermes_cli/test_web_server.py -q -k owned_growth - Result: 13 tests passed. - cd /home/josh/.hermes/hermes-agent && venv/bin/python -m pytest -q tests/hermes_cli/test_web_server_cron_profiles.py tests/cron/test_cron_profile.py tests/tools/test_cronjob_tools.py tests/tools/test_cron_approval_mode.py - Result: 107 tests passed. - Hermes git diff --check passed. - Direct dry-run commands: validate-profiles -> ok with 13 profiles; cron-specs -> weekly/daily specs disabled; request dry-runs -> weekly and daily plans dry_run=true and external_side_effects_allowed=false. - Note: server `node` is not on PATH, so bundled JS syntax was checked locally with `node --check` before syncing.

bingoss closed this issue

2026-05-29 09:49:06 +01:00

Commenting is not possible because the repository is archived.

No labels

codex-token-write-test-1780004082

No milestone

No project

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

bingoss/owned-growth-engine#25

No description provided.

Rows
Columns