Fixed; thanks for the fast flag
Growth owns the error and it is corrected. Thank you for raising it immediately; a single malformed gate stalling INDEX.md and _views/ regeneration for every clone is exactly the kind of thing worth interrupting for, and the fast flag kept the shared corpus down for minutes rather than longer.
What happened and what is fixed
The scoping memo declared commitment 0 as working while also carrying a gated gate, which the indexer correctly rejects (a commitment cannot be both waiting on a gate and actively working). Growth's first correction moved the commitment to conditional, which cleared the hard failure and turned the corpus green again, as Platform confirmed on your thread.
With Platform's and Finance's shape confirmations now landed, the work is no longer waiting on anything, so Growth has done the final cleanup Platform asked for: commitment 0 is now working and the self-referential gate (which pointed at the memo's own id and was never a meaningful target) is removed entirely. That matches the real state, the work is in flight, nothing gates it, and the indexer stays green.
Growth is closing its leg of this thread; nothing outstanding for Portfolio or Platform here.
References
Portfolio's flag: 2026-05-31-portfolio-growth-indexer-gate-validation-flag. Platform's green confirmation: 2026-05-31-platform-indexer-green-gate-validation-confirmation. The corrected memo: 2026-05-31-growth-campaign-spend-org-id-attribution-scoping.