Docs/ecosystem map - #2616
Merged
Merged
Conversation
… agent files Work here routinely spans 4-5 intermingled repos (engine, language-crucible, keyword-rosetta, raw-output, telemetry/analyses) plus local-only directories (the data/ source pool; stale v1-v5/temp/threat_hunter copies of engine files), and nothing mapped it: which repo does what, where each skill lives, how the cross-repo workflows sequence, or that a PR should name its companions. docs/ecosystem.md is now the canonical agent-neutral map (repo table, skills inventory, workflow merge-order table incl. the rosetta draft-until-engine-merges choreography, cross-repo PR body convention, stale-copy warning), and CLAUDE.md / ANTIGRAVITY.md / AGENTS.md each gain a thin synced section pointing at it -- ANTIGRAVITY.md also gains the skills discovery pointer (.agents/skills symlink) it never had, so Antigravity sees the same skill inventory Claude does. Companion PRs add the same thin agent files to keyword-rosetta and language-crucible. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PUfXMUECX4Vq1vqh9mMQqt
…sets; README evidence table gains the missing strands Full org scan surfaced strands the first map draft missed: cobol_to_java_examples (the legacy-modernization showcase -- 10 COBOL repos auto-translated to compiling Spring Boot), the squid-protocol profile README (the public front door), and the whole public-surface inventory -- the ~100-page gh-pages docs site (Museum of Code, cookbook, Legacy Bridge chapter, risk-equation methodology), gitgalaxy.io, PyPI, the demo video, and the three families of auto-regenerating chart assets (rosetta bias SVG, raw-output speed charts, telemetry adoption PNGs) with their raw embed URLs. ecosystem.md also codifies the satellite-README 'constellation section' convention (every repo links its neighbors with a you-are-here marker; the engine README stays governed by how_to_maintain_the_readme.md). README 'Explore the evidence' table: +4 rows (COBOL->Java examples, population analyses, Museum of Code, distribution telemetry+PyPI) -- evidence-shaped one-liners per the five rules, no new superlatives. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PUfXMUECX4Vq1vqh9mMQqt
Contributor
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.
Description
Core Engine Modification Checklist
If your PR changes the core parsing engine (
language_standards.py,detector.py,prism.py), you MUST complete the following validation gauntlet before merging:crucible_check.pyto verify diffs, and rancrucible_check.py --update --yesif the baseline changed due to intentional parsing improvements.python tests/tools/tri_comparison_chart.py --all --cilocally first. If you intentionally improved precision, regenerate the baseline:python tests/tools/tri_comparison_chart.py --regenerate --languages <lang>.python tests/tools/tree_sitter_accuracy_audit.py --ci --all. If ground truth drifted for valid reasons, regenerated the baseline withpython tests/tools/tree_sitter_accuracy_audit.py --regenerate --lang <lang>.