Skip to content

CLAUDE.md

Latest commit

 

History

History
61 lines (48 loc) · 2.53 KB

CLAUDE.md

File metadata and controls

61 lines (48 loc) · 2.53 KB
Raw

Ditto Subnet Monorepo

This repository owns the public SN118 product and runtime as one release unit. Use the repository agent skills instead of reconstructing cross-repository context.

Start every substantial task

python3 .agents/skills/ditto-subnet-context/scripts/lookup-context.py "<task>"

Load only the returned anchors and the relevant specialized skill:

  • .agents/skills/ditto-subnet-platform for Platform, migrations, dashboard, and Backroom;
  • .agents/skills/ditto-subnet-benchmark for validator, scoring, DittoBench, datagen, and adapters;
  • .agents/skills/ditto-subnet-release-ops for releases, deployments, screeners, Targon/GCE, GCP, Cloudflare, Terraform, and Ansible;
  • .agents/skills/ditto-subnet-worktree plus .agents/skills/github for isolation and stacked PRs.

Ownership map

Surface Path
Miner CLI, validator, chain client ditto/
Validator Compose and updater docker-compose.yml, scripts/
Platform API, DB, dashboard apps/platform/
Public subnet Backroom apps/backroom/
DittoBench API and adapters services/dittobench-api/
Screener capacity controller services/screener-orchestrator/
Screener worker workers/screener/
Shared screening protocol packages/ditto-screening-protocol/
Benchmark datagen research research/dittobench-datagen/
Miner starter kit miners/dittobench-starter-kit/
Terraform and Ansible infra/
Release ownership graph release/components.toml

Cross-component changes

Change every producer, consumer, generated artifact, migration, test, release selector, and operational contract in one monorepo stack. Do not create a repository dispatch, version-bump PR, or bot sync between directories.

The validator remains stateless; Platform owns durable queues, leases, policy, and persistence. DittoBench owns versioned execution/scoring. Research adapters must use normal score paths. Backroom is the public SN118 operator console and must keep privileged tokens and OAuth state server-side.

Delivery

Conventional commits drive semantic releases for affected components. Platform API changes affect Backroom; dashboard-only changes do not. Application deploys may follow releases automatically. Infrastructure always uses protected Terraform plan/apply. Verify source, CI, merge, release, deployment, migration, and live behavior as separate facts.

Never read or print provider secrets. Use Secret Manager or encrypted provider bindings through consumers that do not return secret values.