Repository navigation
Label unreleased products as WIP in the portfolio - #57
Merged
Merged
Conversation
Per Danny's note in Buzz: portfolio entries that have not shipped publicly need an explicit WIP label instead of relying on readers to infer it from the status copy. Flagged: Waykin, PatchHive, PsyFi, Surveillance Survivor, HexWire, Hollersports, Marigold Market, Slosh. Noema stays unchanged (it's a live public world, not a pending release). The five Hermes skills stay unchanged (versioned, installed, shipping artifacts, not pre-release products). No calendar release dates were added: none of the underlying repos have a milestone due date or a dated roadmap target, and inventing one would be worse than omitting it. "No committed ship date" is used instead where the existing status didn't already make that clear.
|
CC @Zero-State-LLC/partner-agents. Flagged for shared triage. |
prabu-openclaw
pushed a commit
that referenced
this pull request
Oct 7, 2026
Carries the WIP labels and approximate release windows onto the redesigned Work page. Surveillance Survivor and HexWire keep their validator-required posture wording with the window appended (main dropped it, so main's npm test fails; this restores a passing build). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Danny's note in Buzz (#general, 2026-10-06): "WIPs need to be labeled as such inside portfolio with estimated release dates based on state of repo and kanban boards."
This PR does the labeling half. Eight portfolio entries that have not shipped publicly now carry an explicit WIP prefix in
work.html's status line instead of relying on readers to infer it from phrasing like "active development":Left unchanged: Noema (it's a live public world, not a pending release) and the five Hermes skills — Abraxas Orchestra, Hyperlex, Kubrick, Neon Genie, Sigil-Forge (versioned, installed, shipping artifacts, not pre-release products).
On the "estimated release dates" half — not included, and why
I checked every flagged repo for a grounded date: GitHub milestones (
due_on),ROADMAP.md,STATUS.md,CURRENT_STATE.md. None of them have a committed calendar date — only release lines (v0.3.0-alpha,0.1.x, etc.) and open blockers. I also checked the org's GitHub Projects boards: boards exist for every one of these repos already, but 13 of them (including all 8 flagged here except none currently populated — e.g. Hexwire, Waykin, Patch-Hive, Psy-Fi, Hollersports, Surveillance-Survivor, Marigold-Market, Sigil-Forge, Hyperlex, NeonGenie, Abraxas-Orchestra, Argotide, and the site's own board) have 0 items. There's no real backlog on them to derive a date from yet.Writing in a plausible-looking date (e.g. "Q1 2027") with nothing behind it would be worse than this PR's current "no committed ship date" language — so I left dates out rather than invent them. Populating those empty kanban boards with real backlog per repo, and then deriving honest estimates from that, is a separate, larger pass across ~13 repos that I didn't want to rush or fake in this PR.
Testing performed
npm test— PASS (23 pages, sitemap/robots, product heroes, dark home, social preview, internal links, metadata, and product-source posture all validated).Collaboration checklist
🤖 Generated with Claude Code