7c3c5f7eb9
The old tracked TypeScript snapshot has been removed from the repository history and the root directory is now a Python porting workspace. README and tests now describe and verify the Python-first layout instead of treating the exposed snapshot as the active source tree. A local archive can still exist outside Git, but the tracked repository now presents only the Python porting surface, related essay context, and OmX workflow artifacts. Constraint: Tracked history should collapse to a single commit while excluding the archived snapshot from Git Rejected: Keep the exposed TypeScript tree in tracked history under an archive path | user explicitly wanted only the Python porting repo state in Git Confidence: medium Scope-risk: broad Reversibility: messy Directive: Keep future tracked additions focused on the Python port itself; do not reintroduce the exposed snapshot into Git history Tested: python3 -m unittest discover -s tests -v; python3 -m src.main summary; git diff --check Not-tested: Behavioral parity with the original TypeScript system beyond the current Python workspace surface
Claude Code Python Porting Workspace
The primary
src/tree in this repository is now dedicated to Python porting work. The March 31, 2026 Claude Code source exposure is part of the project's background, but the tracked repository is now centered on Python source rather than the exposed TypeScript snapshot.
Porting Status
The main source tree is now Python-first.
src/contains the active Python porting workspacetests/verifies the current Python workspace- the exposed snapshot is no longer part of the tracked repository state
The current Python workspace is not yet a complete one-to-one replacement for the original system, but the primary implementation surface is now Python.
Why this rewrite exists
I originally studied the exposed codebase to understand its harness, tool wiring, and agent workflow. After spending more time with the legal and ethical questions—and after reading the essay linked below—I did not want the exposed snapshot itself to remain the main tracked source tree.
This repository now focuses on Python porting work instead.
Repository Layout
.
├── src/ # Python porting workspace
│ ├── __init__.py
│ ├── commands.py
│ ├── main.py
│ ├── models.py
│ ├── port_manifest.py
│ ├── query_engine.py
│ ├── task.py
│ └── tools.py
├── tests/ # Python verification
├── assets/omx/ # OmX workflow screenshots
├── 2026-03-09-is-legal-the-same-as-legitimate-ai-reimplementation-and-the-erosion-of-copyleft.md
└── README.md
Python Workspace Overview
The new Python src/ tree currently provides:
port_manifest.py— summarizes the current Python workspace structuremodels.py— dataclasses for subsystems, modules, and backlog statecommands.py— Python-side command port metadatatools.py— Python-side tool port metadataquery_engine.py— renders a Python porting summary from the active workspacemain.py— a CLI entrypoint for manifest and summary output
Quickstart
Render the Python porting summary:
python3 -m src.main summary
Print the current Python workspace manifest:
python3 -m src.main manifest
List the current Python modules:
python3 -m src.main subsystems --limit 16
Run verification:
python3 -m unittest discover -s tests -v
Related Essay
The essay is dated March 9, 2026, so it should be read as companion analysis that predates the March 31, 2026 source exposure that motivated this rewrite direction.
Built with oh-my-codex
The restructuring and documentation work on this repository was AI-assisted and orchestrated with Yeachan Heo's oh-my-codex (OmX), layered on top of Codex.
$teammode: used for coordinated parallel review and architectural feedback$ralphmode: used for persistent execution, verification, and completion discipline- Codex-driven workflow: used to turn the main
src/tree into a Python-first porting workspace
OmX workflow screenshots
Ralph/team orchestration view while the README and essay context were being reviewed in terminal panes.
Split-pane review and verification flow during the final README wording pass.
Ownership / Affiliation Disclaimer
- This repository does not claim ownership of the original Claude Code source material.
- This repository is not affiliated with, endorsed by, or maintained by Anthropic.