Skip to content

fix(portfolio): classify fable campaign workspaces#167

Merged
saagpatel merged 1 commit into
mainfrom
codex/classify-fable-campaign-workspaces
Jul 8, 2026
Merged

fix(portfolio): classify fable campaign workspaces#167
saagpatel merged 1 commit into
mainfrom
codex/classify-fable-campaign-workspaces

Conversation

@saagpatel

Copy link
Copy Markdown
Owner

What

  • Classify the three newer Fable campaign control-room folders in the portfolio catalog.
  • Keep them in the non-default experiment attention lane instead of surfacing them as operator decisions.

Why

  • The latest portfolio truth refresh promoted these packet/output campaign workspaces to decision-needed only because they lacked catalog posture.
  • Their local READMEs show they are campaign control rooms, not active product or infrastructure delivery lanes.

How

  • Added catalog entries for fable-corpus-campaign, fable-estate-campaign, and fable-rigor-campaign matching the existing Fable campaign pattern.

Testing

  • uv run operator-os-seam-linter --truth output/portfolio-truth-latest.json --json passed.
  • uv run pytest -q tests/test_portfolio_catalog.py tests/test_portfolio_truth.py passed: 78 tests.
  • uv run ruff check . passed.

Risk / Notes

  • Low risk; catalog-only posture correction. Local generated portfolio truth showed decision-needed drops to empty after refresh with Notion context preserved.

@saagpatel saagpatel merged commit 3af2667 into main Jul 8, 2026
4 checks passed
@saagpatel saagpatel deleted the codex/classify-fable-campaign-workspaces branch July 8, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant