bingoss/owned-growth-engine
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Growth Orchestrator runs Weekly Intelligence stages end to end #17

New issue
Closed
opened 2026-05-28 18:14:51 +01:00 by bingoss · 1 comment
bingoss commented 2026-05-28 18:14:51 +01:00
Owner
Copy link

What to build

Type: AFK.

Create the Growth Orchestrator behavior that coordinates a full Weekly Intelligence Run across the required stages, records each stage as completed/skipped/blocked/failed, preserves staged diagnostics, and promotes only passing runs to the Active Weekly Plan.

Acceptance criteria

  • A Weekly Intelligence Run creates or coordinates stage Run Requests for Business/Profile Analysis, Technical Audit, Keyword and Competitor Research, LLM Visibility, Public Listening, Authority Research, Content Planning, and Weekly Summary.
  • Each stage records safe terminal state and diagnostics without hiding failures behind filler output.
  • A passing run promotes to Active Weekly Plan; a failed or incomplete staged run keeps diagnostics without replacing the active plan.
  • Tests are written first for full success, optional stage skipped, required stage failed, and no-active-plan replacement on failure.

Blocked by

## What to build Type: AFK. Create the Growth Orchestrator behavior that coordinates a full Weekly Intelligence Run across the required stages, records each stage as completed/skipped/blocked/failed, preserves staged diagnostics, and promotes only passing runs to the Active Weekly Plan. ## Acceptance criteria - [ ] A Weekly Intelligence Run creates or coordinates stage Run Requests for Business/Profile Analysis, Technical Audit, Keyword and Competitor Research, LLM Visibility, Public Listening, Authority Research, Content Planning, and Weekly Summary. - [ ] Each stage records safe terminal state and diagnostics without hiding failures behind filler output. - [ ] A passing run promotes to Active Weekly Plan; a failed or incomplete staged run keeps diagnostics without replacing the active plan. - [ ] Tests are written first for full success, optional stage skipped, required stage failed, and no-active-plan replacement on failure. ## Blocked by - #1 - #2 - #13 - #14 - #15 - #16
bingoss commented 2026-05-29 00:44:04 +01:00
Author
Owner
Copy link

Issue #17 completion audit

Implemented and verified:

  • Added Growth Orchestrator entrypoint run_growth_orchestrator_once for full Weekly Intelligence runs.
  • Orchestrator coordinates and records terminal run_stages for Business/Profile Analysis, Technical Audit, Keyword and Competitor Research, LLM Visibility, Public Listening, Authority Research, Content Planning, and Weekly Summary.
  • Each stage writes completed/skipped/blocked/failed state with requirement mode, safe output summaries, diagnostics, safe errors, and append-only stage events.
  • Content Planning uses the existing validated Content Planner completion path so plan rows, queue rows, artifacts, and artifact links are written before promotion.
  • Passing runs call the existing Postgres promotion gate and become the Active Weekly Plan.
  • Optional stage skips remain terminal optional stages and do not block promotion.
  • Required stage failures stop orchestration, keep diagnostics, do not write downstream plan rows, and do not promote.
  • Failed or incomplete orchestrated runs preserve any existing Active Weekly Plan.
  • Existing run_weekly_intelligence_worker_once now dispatches orchestrator runs before falling back to stage-specific technical/content dispatch.

Tests run on codex-server:

  • python3 -m unittest tests.test_growth_orchestrator_worker tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_weekly_worker_dispatches_requested_technical_audit_runs
  • Result: OK, 5 tests.
  • Broader verification: python3 -m unittest tests.test_growth_orchestrator_worker tests.test_content_planner_contract 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_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker && git diff --check
  • Result: OK, 165 tests; git diff --check clean.
Issue #17 completion audit Implemented and verified: - Added Growth Orchestrator entrypoint run_growth_orchestrator_once for full Weekly Intelligence runs. - Orchestrator coordinates and records terminal run_stages for Business/Profile Analysis, Technical Audit, Keyword and Competitor Research, LLM Visibility, Public Listening, Authority Research, Content Planning, and Weekly Summary. - Each stage writes completed/skipped/blocked/failed state with requirement mode, safe output summaries, diagnostics, safe errors, and append-only stage events. - Content Planning uses the existing validated Content Planner completion path so plan rows, queue rows, artifacts, and artifact links are written before promotion. - Passing runs call the existing Postgres promotion gate and become the Active Weekly Plan. - Optional stage skips remain terminal optional stages and do not block promotion. - Required stage failures stop orchestration, keep diagnostics, do not write downstream plan rows, and do not promote. - Failed or incomplete orchestrated runs preserve any existing Active Weekly Plan. - Existing run_weekly_intelligence_worker_once now dispatches orchestrator runs before falling back to stage-specific technical/content dispatch. Tests run on codex-server: - python3 -m unittest tests.test_growth_orchestrator_worker tests.test_technical_audit_worker.TechnicalAuditWorkerTests.test_weekly_worker_dispatches_requested_technical_audit_runs - Result: OK, 5 tests. - Broader verification: python3 -m unittest tests.test_growth_orchestrator_worker tests.test_content_planner_contract 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_postgres_dashboard tests.test_postgres_schema tests.test_technical_audit_worker && git diff --check - Result: OK, 165 tests; git diff --check clean.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
codex-token-write-test-1780004082
Temporary token write test; safe to delete.

No labels
codex-token-write-test-1780004082
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#17
No description provided.