Business/Profile Analysis Specialist writes required evidence #1

Closed
opened 2026-05-28 18:12:01 +01:00 by bingoss · 1 comment
Owner

What to build

Create the Business/Profile Analysis slice of Weekly Intelligence. A Run Request for this stage should produce reviewable, structured evidence for Mestra positioning, offers, audiences, proof points, competitors, constraints, and claim boundaries so downstream Content Planning can use it without guessing.

Acceptance criteria

  • A Business/Profile Analysis run records a completed, blocked, or failed run stage with safe diagnostics and append-only events.
  • Successful output includes structured evidence references for positioning, audience, offers, competitors, proof points, constraints, and claim boundaries.
  • The dashboard exposes the latest stage state and artifact links without raw provider payloads, secrets, or long bodies.
  • Missing or unsafe source evidence blocks or fails closed instead of creating filler evidence.
  • Tests are written first and cover success, missing evidence, and safe-error behavior.

Blocked by

None - can start immediately

## What to build Create the Business/Profile Analysis slice of Weekly Intelligence. A Run Request for this stage should produce reviewable, structured evidence for Mestra positioning, offers, audiences, proof points, competitors, constraints, and claim boundaries so downstream Content Planning can use it without guessing. ## Acceptance criteria - [ ] A Business/Profile Analysis run records a completed, blocked, or failed run stage with safe diagnostics and append-only events. - [ ] Successful output includes structured evidence references for positioning, audience, offers, competitors, proof points, constraints, and claim boundaries. - [ ] The dashboard exposes the latest stage state and artifact links without raw provider payloads, secrets, or long bodies. - [ ] Missing or unsafe source evidence blocks or fails closed instead of creating filler evidence. - [ ] Tests are written first and cover success, missing evidence, and safe-error behavior. ## Blocked by None - can start immediately
Author
Owner

Issue #1 completion audit

Implemented and verified:

  • Business/Profile Analysis run requests are claimed through a dedicated worker and recorded as completed, blocked, or failed stages with safe diagnostics and append-only events.
  • Successful runs now write normalized business_profile_evidence rows for positioning, audience, offers, competitors, proof points, constraints, and claim boundaries, with structured source_reference data and no filler rows.
  • Raw source payloads are retained only in raw_provider_payloads; dashboard output exposes latest stage state, safe evidence summaries, counts, and artifact links without raw provider payload bodies.
  • Missing required categories and unsafe/high-risk source evidence block the stage and fail the run closed without persisting partial normalized evidence.
  • Source exceptions fail safely with exception class only and do not leak provider exception bodies into result/dashboard output.
  • Canonical and idempotent evidence migrations plus schema docs were updated for the new evidence table and evidence_type.

Tests run on codex-server:

  • python3 -m unittest tests.test_business_profile_worker tests.test_postgres_schema.SliceOnePostgresSchemaTests.test_enum_values_match_schema_contract tests.test_postgres_schema.SliceFiveEvidenceAndMeasurementSchemaTests.test_incremental_evidence_migration_restores_missing_evidence_tables_on_partial_schema tests.test_postgres_schema.SliceFiveEvidenceAndMeasurementSchemaTests.test_incremental_evidence_migration_is_idempotent_after_canonical_schema
  • Result: OK, 7 tests.
Issue #1 completion audit Implemented and verified: - Business/Profile Analysis run requests are claimed through a dedicated worker and recorded as completed, blocked, or failed stages with safe diagnostics and append-only events. - Successful runs now write normalized business_profile_evidence rows for positioning, audience, offers, competitors, proof points, constraints, and claim boundaries, with structured source_reference data and no filler rows. - Raw source payloads are retained only in raw_provider_payloads; dashboard output exposes latest stage state, safe evidence summaries, counts, and artifact links without raw provider payload bodies. - Missing required categories and unsafe/high-risk source evidence block the stage and fail the run closed without persisting partial normalized evidence. - Source exceptions fail safely with exception class only and do not leak provider exception bodies into result/dashboard output. - Canonical and idempotent evidence migrations plus schema docs were updated for the new evidence table and evidence_type. Tests run on codex-server: - python3 -m unittest tests.test_business_profile_worker tests.test_postgres_schema.SliceOnePostgresSchemaTests.test_enum_values_match_schema_contract tests.test_postgres_schema.SliceFiveEvidenceAndMeasurementSchemaTests.test_incremental_evidence_migration_restores_missing_evidence_tables_on_partial_schema tests.test_postgres_schema.SliceFiveEvidenceAndMeasurementSchemaTests.test_incremental_evidence_migration_is_idempotent_after_canonical_schema - Result: OK, 7 tests.
Commenting is not possible because the repository is archived.
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#1
No description provided.