Surface active Oddworks finish lanes#183
Conversation
saagpatel
force-pushed
the
codex/integration-truth-catalog
branch
from
e32d70f to
ac175fd
Compare
saagpatel
force-pushed
the
codex/integration-oddworks
branch
from
013aee2 to
1df58e8
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1920d054b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # remain valid while the default branch is stale (for example, when work is | ||
| # on a release branch or waiting at a human/publication gate), so do not | ||
| # silently collapse it back into the parked pool. | ||
| return "decision-needed" if operating_path == "finish" else "parked" |
There was a problem hiding this comment.
This changes the published derivation of derived.attention_state for stale finish repos from parked to decision-needed, but the snapshot DERIVATION_POLICY_VERSION remains portfolio_attention.v2. Because validate_truth_snapshot accepts snapshots by matching that constant, a pre-patch portfolio-truth-latest.json can still pass validation while carrying the old parked counts for stale finish lanes, defeating the contract/freshness gate for this semantic change.
Useful? React with 👍 / 👎.
| purpose: compact authored supernatural-radio game being finished as an Oddworks release | ||
| lifecycle_state: active | ||
| review_cadence: monthly | ||
| operating_path: maintain | ||
| tool_provenance: claude-code | ||
| criticality: high | ||
| review_cadence: weekly | ||
| operating_path: finish |
There was a problem hiding this comment.
These new finish-lane fields are only under the Phantom Frequencies catalog key, but catalog matching uses exact path/full-name/repo-name keys plus explicit aliases; the project is referenced elsewhere as PhantomFrequencies (docs/ci-coverage-initiative.md:46, config/notion-project-map.json:149) and no catalog alias is added here. When the checkout or repo name is the no-space spelling, this activation falls through to defaults, so that Oddworks lane will not surface as finish/commercial.
Useful? React with 👍 / 👎.
1 participant
Stack 6/7. Applies the bounded Oddworks activation and finish-lane catalog changes. Depends on stack 5.