Skip to content

Repository files navigation

Operation Prometheus

Operation Prometheus is a software-engineering trajectory forge.

The project extracts high-signal engineering artifacts from public repositories and transforms them into structured training datasets for local coding assistants, research agents, and future neuromorphic experiments.

Instead of treating source code as the primary training signal, Operation Prometheus focuses on engineering trajectories:

Issue
↓
Implementation
↓
Review
↓
Fix
↓
Validation
↓
Merge

These trajectories capture the reasoning, debugging, validation, and repair process behind software engineering.

Initial Goals

  • Extract trajectory datasets from GitHub repositories
  • Build Rust repair and autocomplete datasets
  • Build Julia engineering datasets
  • Create review-comment → patch training pairs
  • Create bug-prediction and validation datasets
  • Support future SAAQ(Spiking Adaptive Activity Quantization) and Spikenaut research

Data Sources

Initial repositories include:

  • corinth-canal
  • xai-dissect
  • grok-ozempic
  • myelin-accelerator
  • Surrogate_Viz.jl
  • XAIDissect_Viz.jl
  • agoge-forger
  • Dioscuri-Cloud
  • magere-brug
  • Future Limen-Neural projects

Repository Layout

  • docs/ — documentation and guides (including data-policy.md)
  • schemas/ — data and trajectory schemas (JSON Schema v0 draft)
  • providers/ — thin clients, adapters and config for external model / inference providers (no weights or large artifacts)
  • scripts/ — extraction, transformation, and validation scripts
  • datasets/ — local dataset outputs (raw data under datasets/raw/ is gitignored; only small curated examples, cards, and manifests may be committed — see datasets/README.md)
  • evals/ — evaluation assets and prompts

See datasets/README.md for rules on what may be committed.

Schemas and Data Policy

  • Schema v0 (initial draft, not final): schemas/pr_trajectory.schema.json. Implements GitHub #2. See the tiny example in datasets/examples/.
  • Data policy & hygiene: docs/data-policy.md. Implements GitHub #3. Covers allowed public sources, excluded material, manual inspection requirement, and the distinction between public engineering history vs. raw chat log scraping.

Extraction Shortlists

Collect and normalize (read-only)

Requires public GitHub access. A token is optional but strongly recommended for rate limits.

python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt

export GITHUB_TOKEN=...   # optional; higher rate limits

# Optional: large raw dumps outside the git tree (issue #14).
# When set and --out-dir is omitted, collector writes to $PROMETHEUS_DATA_ROOT/raw/<owner_repo>/.
# export PROMETHEUS_DATA_ROOT=~/rmems/prometheus-data

# Issue #5 — collect raw PR records (default: datasets/raw/<owner_repo>/, or DATA_ROOT)
python scripts/collect_pr_records.py \
  --repo rmems/corinth-canal \
  --pr 82,89,91,94,95,96

# Explicit in-tree path (overrides PROMETHEUS_DATA_ROOT):
#   --out-dir datasets/raw/corinth-canal

# Issue #6 — normalize to schema-compliant JSONL
python scripts/build_trajectory_jsonl.py \
  --raw-dir datasets/raw/corinth-canal \
  --card datasets/cards/corinth-canal-v0.json \
  --out datasets/jsonl/corinth-canal-v0.jsonl

# Validate (schema + optional policy hygiene)
python scripts/validate_jsonl.py --strict-policy datasets/jsonl/corinth-canal-v0.jsonl

The collector performs no write operations to GitHub. Raw dumps must stay out of git (datasets/raw/ is ignored).

About

Engineering trajectory forge: public GitHub issue→review→patch→validation history as JSONL datasets for local coding agents and research.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages