Repository navigation
Conversation
Mirror the website's project directory in the org profile README: core projects (moca, cortex, eventing-lab, autobench, state-lab), context & governance (context-guru, aiac, lab-data-governance, context-service), and automation & repo maintenance (automation, repoman). The rossoctl and .github repos stay listed under platform & docs. Drops the stale Kubernetes-platform framing, the A2A/MCP standards block, and the deprecated or experimental repos (operator, examples, agent-skills, workload-harness, capture-the-flag, mcp-gateway) from the org front page. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
✅ Deploy Preview for animated-crumble-fb8862 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…le list Conflict resolution for #136: main added an install-stats link to the cortex entry (#133) while this branch rewrote the repository list. Keep the branch's new categorization and carry the install-stats link onto the rewritten cortex entry. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
aslom
left a comment
aslom
left a comment
There was a problem hiding this comment.
Review: align the org profile repository list with the current focus
Approving. The list matches the website directory from #135, and dropping the
superseded repos from the org's front door is clearly right. Two accuracy notes below
— both small, neither a reason to hold the merge.
Verified independently against the live API:
- all 13 linked repos exist, are public, and are un-archived (200 each)
- the dropped repos are genuinely on the way out:
operator,examplesand
workload-harnessall carry⚠️ DEPRECATED — archiving 2026-11-02descriptions
(that is today), andcapture-the-flagwas last pushed in August mcp-gatewaycorrectly leaves with them — it lives under theKuadrantorg, not
this one- the core-project one-liners are byte-identical to those added in
rossoctl/rossoctl#2662, so the two PRs will not drift profile/README.mdis indeed outside the Docusaurus build, so no site impact — and
note the repo's link checker only runs onpushtomainplus a weekly cron
against the built site, so nothing in CI validated these links on this PR. That
is the reason I checked all 13 by hand rather than trusting the green checks.
Findings: one language annotation looks inverted (moca), and rossoctl-cli is
dropped without being named in the PR description's list of removals. Details inline.
| - **[automation](https://github.com/rossoctl/automation)** - Automated org maintenance tooling using a scanner/fixer pattern (Shell) | ||
| - **[agent-skills](https://github.com/rossoctl/agent-skills)** - Reusable agent skills for org automation, such as link-health, automated pull request reviewing, and dependency scanning (Shell) | ||
| - **[rossoctl-cli](https://github.com/rossoctl/rossoctl-cli)** - Command-line interface for Rossoctl (Go) | ||
| - **[moca](https://github.com/rossoctl/moca)** - Dense, warm process-manager runtime for stateful AI coding agents — sessions resume exactly where they left off (Go) |
There was a problem hiding this comment.
[medium] The (Go) annotation on moca looks inverted. The PR description says
"language annotations match each repo's dominant language", but GitHub reports
TypeScript as moca's dominant language, by a wide margin:
TypeScript 5,327,793 bytes <- dominant
Go 1,892,769
Shell 1,828,730
The repo layout agrees: there is no root go.mod (only gen/go/go.mod and
remote-worker/go.mod), while package.json appears at the root and in 12 more
places (harness/, packages/mocactl/, packages/supervisor/, …). Go is a real but
secondary part of the stack.
Since this list is the org's front page, (TypeScript) — or (TypeScript/Go) if you
want to signal both — would be more accurate.
The same (Go) annotation is duplicated in rossoctl/rossoctl#2662 (README.md:18),
so this wants fixing in both places to keep the two lists identical.
| #### Platform & docs | ||
|
|
||
| - **[rossoctl](https://github.com/rossoctl/rossoctl)** - Installer, web console, and documentation (Python) | ||
| - **[.github](https://github.com/rossoctl/.github)** - Project website and documentation (Docusaurus) |
There was a problem hiding this comment.
[low] Two small notes on this block:
.github is annotated (Docusaurus) while every other entry carries a
language (Python, Go, Shell). GitHub reports TypeScript as this repo's dominant
language. Docusaurus is more useful to a reader than "TypeScript" here, so this may
well be deliberate — just flagging the inconsistency in kind, since the description
frames all of these as language annotations.
rossoctl-cli is dropped but not accounted for. The PR description lists the
removals as "operator, examples, agent-skills, workload-harness, capture-the-flag,
mcp-gateway" — rossoctl-cli is also being removed from the list but is not named.
Unlike the others it carries no deprecation marker: it is public, un-archived, and
its description is still a plain "A CLI (command line interface) for rossoctl" (last
push 2026-09-07).
It may be genuinely superseded, in which case dropping it is right and the repo
description should probably get the same ⚠️ DEPRECATED treatment the others got.
Worth confirming the omission was intentional rather than incidental.
Summary
Updates the org profile README — the landing page at https://github.com/rossoctl — to mirror the project directory introduced on the website (companion to #135):
Each entry carries the one-line essence used on the website plus its primary language. The stale "agentic platform on Kubernetes" framing and the A2A/MCP standards block are dropped, along with the deprecated or superseded repos (operator, examples, agent-skills, workload-harness, capture-the-flag, mcp-gateway) — none of them should front the org anymore.
rossoctl-cliis also dropped from the list: it is not part of the current focus set, though the repo itself is not deprecated.The "Get involved" section (CONTRIBUTING, maintainers, rossoctl.dev, Slack) is unchanged.
Verification
profile/README.mdis outside the Docusaurus build (org profile only), so no site build impactAssisted-By: Claude Code