Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
38 changes: 38 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
name: CI

on:
pull_request:
push:
branches:
- main

permissions:
contents: read

concurrency:
group: ci-${{ github.ref }}
cancel-in-progress: true

jobs:
test-and-pack:
name: Test and pack check
runs-on: ubuntu-latest
timeout-minutes: 10

steps:
- name: Check out repository
uses: actions/checkout@v4

- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: 20

- name: Install dependencies
run: npm ci

- name: Run tests
run: npm test

- name: Check npm package contents
run: npm pack --dry-run
35 changes: 35 additions & 0 deletions .github/workflows/release-check.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
name: Release Check

on:
workflow_dispatch:

permissions:
contents: read

concurrency:
group: release-check-${{ github.ref }}
cancel-in-progress: true

jobs:
verify-release-candidate:
name: Verify release candidate
runs-on: ubuntu-latest
timeout-minutes: 10

steps:
- name: Check out repository
uses: actions/checkout@v4

- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: 20

- name: Install dependencies
run: npm ci

- name: Run tests
run: npm test

- name: Check npm package contents
run: npm pack --dry-run
9 changes: 9 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
node_modules/
.erdos/
.clawdad/
output/
tmp/
dist/
*.tgz
.DS_Store
research/frontier-engine/build/
research/frontier-engine/src/*.egg-info/
research/frontier-engine/artifacts/
research/frontier-engine/experiments/**/live-frontier-sync/
packs/number-theory/problems/848/EXACT_SMALL_N_1_*_CERTIFICATE.md
packs/number-theory/problems/848/EXACT_SMALL_N_1_*_RESULTS.json
21 changes: 21 additions & 0 deletions .npmignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
.clawdad/
.erdos/
output/
tmp/
dist/
*.tgz
.DS_Store

# Local/generated frontier-engine run products. Keep source, docs, schemas, and
# compact benchmark profiles in npm; leave raw run bundles in the repo workspace.
research/frontier-engine/artifacts/
research/frontier-engine/build/
research/frontier-engine/src/*.egg-info/
research/frontier-engine/experiments/**/live-frontier-sync/

# Exact small-N scan result packets can be very large. The npm package carries
# the scanner and curated proof-facing summaries, not every raw rollout product.
packs/number-theory/problems/848/EXACT_SMALL_N_1_*_RESULTS.json
packs/number-theory/problems/848/EXACT_SMALL_N_1_*_CERTIFICATE.md
!packs/number-theory/problems/848/EXACT_SMALL_N_1_10000_CERTIFICATE.md
packs/number-theory/problems/848/SPLIT_ATOM_PACKETS/
34 changes: 33 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ A short example from the first minute:
- separate surfaces for public status, local route state, and verification records
- pack-specific views where this repo already has enough structure to support them
- an ORP-based workflow for claims, checkpoints, and run artifacts
- an integrated research stack surface that ties canonical imports, ORP, theorem loops, compute lanes, and writeback commands together
- a paper writer bundle mode for public-safe, citation-safe, agent-friendly drafting

## Repo, npm, and External Imports
Expand All @@ -49,7 +50,8 @@ A short example from the first minute:
- `erdos import show` reports whether you are using the bundled import snapshot or a workspace-local refreshed import snapshot
- `erdos import sync` currently refreshes an external atlas import snapshot from `teorth/erdosproblems` without mutating the canonical local dossier layer
- `erdos import sync --write-package-snapshot` is the maintainer path for intentionally updating the bundled import snapshot in this repo
- repo-only deep-research directories such as `research/`, `formal/`, `paper/`, `imports/`, and `analysis/` are intentionally kept out of npm by staying outside the `package.json` `files` list
- most deep-research directories such as `formal/`, `paper/`, `imports/`, and `analysis/` remain repo-only and are intentionally kept out of npm
- `research/frontier-engine` is the current exception: it ships as an optional bundled subsystem so users can opt into GPU-oriented frontier search without making base npm install heavier
- repo-only public research can live in this GitHub repo without shipping in the npm tarball; see the contribution guide: https://github.com/SproutSeeds/erdos-problems/blob/main/CONTRIBUTING.md

## Start In 60 Seconds
Expand All @@ -69,6 +71,36 @@ erdos sunflower ready 857
erdos workspace show --json
```

If you want the optional frontier-engine runtime, keep it explicit:

```bash
erdos frontier doctor
erdos frontier setup --base
erdos frontier setup --cpu
erdos frontier setup --cuda --torch-index-url <url>
erdos frontier create-brev erdos-h100 --gpu-name H100 --dry-run
erdos frontier create-brev-fleet erdos-h100x2 --type hyperstack_H100 --count 2 --dry-run
erdos frontier attach-brev --instance <name> --apply
erdos frontier sync-fleet erdos-h100x2 --lane p848_anchor_ladder --apply
erdos number-theory dispatch-fleet 848 --fleet erdos-h100x2 --apply --action gpu_profile_sweep --strategy ladder_cover_v1
```

The Brev path is meant to be a native frontier rung: preview hardware with `create-brev --dry-run`, then create, attach, and sync a lane into the same SSH-backed frontier loop used by local and fixed remote boxes.

To see how the whole stack connects for the active problem:

```bash
erdos workspace show
erdos preflight
```

Those views now summarize:
- canonical source and import provenance
- ORP/checkpoint workflow
- theorem-loop entry and refresh commands
- compute entrypoints and hardware setup
- canonical writeback surfaces

If you want to start from a new local seed:

```bash
Expand Down
1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@
"docs",
"packs",
"problems",
"research",
"src",
"templates"
],
Expand Down
157 changes: 157 additions & 0 deletions packs/graph-theory/problems/1008/CLAIM_LOOP.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,157 @@
{
"schema": "erdos.problem_claim_loop/1",
"generatedAt": "2026-04-10T08:11:06.262Z",
"problemId": "1008",
"displayName": "Erdos Problem #1008",
"title": "C4-Free Subgraph Density Problem",
"cluster": "graph-theory",
"sourceKind": "theorem_loop_only",
"claimLoopMode": "baseline",
"currentClaimSurface": "route_scaffolding",
"currentState": {
"theoremLoopMode": "baseline",
"activeRoute": "c4_free_lean_archive",
"nextHonestMove": "Record the best public/formalization hook and checkpoint the archive packet.",
"routeSummary": "Keep the solved `C_4`-free density record explicit and preserve the Lean-facing archive posture.",
"sourceRefresh": null
},
"featureExtractors": [
{
"extractor_id": "pack_route_state",
"kind": "pack_context",
"scope": "all_problems",
"status": "ready",
"note": "Reads pack route, ticket, and atom state as the baseline theorem-search context."
},
{
"extractor_id": "theorem_loop_snapshot",
"kind": "theorem_loop",
"scope": "all_problems",
"status": "ready",
"note": "Uses the canonical theorem-loop as the current claim-surface ledger."
},
{
"extractor_id": "cluster_graph_theory_features",
"kind": "cluster_adapter",
"scope": "graph_theory",
"status": "ready",
"note": "Exposes graph-theory archive or theorem-state context to the claim loop."
}
],
"claimGenerators": [
{
"generator_id": "baseline_route_claims",
"kind": "route_state",
"scope": "all_problems",
"status": "ready",
"note": "Promotes active routes, ready atoms, and next-honest-move records into candidate claims."
},
{
"generator_id": "theorem_agenda_claims",
"kind": "agenda_projection",
"scope": "all_problems",
"status": "ready",
"note": "Turns theorem agenda items into explicit candidate claim tickets."
}
],
"claimFalsifiers": [
{
"falsifier_id": "theorem_loop_consistency_check",
"kind": "ledger_consistency",
"scope": "all_problems",
"status": "ready",
"note": "Rejects claims that overstate the current theorem-loop claim surface."
},
{
"falsifier_id": "artifact_boundary_check",
"kind": "artifact_boundary",
"scope": "all_problems",
"status": "ready",
"note": "Rejects claims unsupported by canonical artifacts already present in the pack."
}
],
"verifierAdapters": [
{
"adapter_id": "canonical_artifact_reader",
"kind": "artifact_reader",
"scope": "all_problems",
"status": "ready",
"note": "Reads theorem-loop, route, and pack artifacts as verifier-facing evidence."
}
],
"candidateClaims": [
{
"claim_id": "promote_ready_atom",
"status": "ready",
"source": "theorem_agenda",
"summary": "Turn ready atom `G1008.G1.A1` into the next theorem-facing checkpoint.",
"why": "Record the best public/formalization hook and checkpoint the archive packet.",
"support": [
"active_route_recorded",
"ready_atom_present",
"frontier_note_present"
]
},
{
"claim_id": "tighten_active_route_claim",
"status": "ready",
"source": "theorem_agenda",
"summary": "Compress the active route `c4_free_lean_archive` into the next honest theorem-facing claim unit.",
"why": "Record the best public/formalization hook and checkpoint the archive packet.",
"support": [
"active_route_recorded",
"ready_atom_present",
"frontier_note_present"
]
}
],
"theoremHooks": [
{
"hook_id": "active_route_recorded",
"status": "supported",
"note": "The pack records an active route, currently `c4_free_lean_archive`."
},
{
"hook_id": "ready_atom_present",
"status": "supported",
"note": "The live route already has a ready atom, `G1008.G1.A1`, which can feed the theorem lane."
},
{
"hook_id": "frontier_note_present",
"status": "supported",
"note": "The pack already carries a frontier note that can anchor theorem-facing updates."
}
],
"theoremAgenda": [
{
"item_id": "promote_ready_atom",
"status": "ready",
"task": "Turn ready atom `G1008.G1.A1` into the next theorem-facing checkpoint.",
"why": "Record the best public/formalization hook and checkpoint the archive packet."
},
{
"item_id": "tighten_active_route_claim",
"status": "ready",
"task": "Compress the active route `c4_free_lean_archive` into the next honest theorem-facing claim unit.",
"why": "Record the best public/formalization hook and checkpoint the archive packet."
}
],
"commands": {
"problemShow": "erdos problem show 1008",
"problemArtifacts": "erdos problem artifacts 1008",
"theoremLoop": "erdos problem theorem-loop 1008",
"theoremLoopRefresh": "erdos problem theorem-loop-refresh 1008",
"claimLoop": "erdos problem claim-loop 1008",
"claimLoopRefresh": "erdos problem claim-loop-refresh 1008",
"sourceRefresh": null
},
"sources": {
"claimLoopJsonPath": "/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/CLAIM_LOOP.json",
"claimLoopMarkdownPath": "/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/CLAIM_LOOP.md",
"theoremLoopJsonPath": "/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/THEOREM_LOOP.json",
"theoremLoopMarkdownPath": "/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/THEOREM_LOOP.md",
"legacyBridgeJsonPath": null,
"legacyBridgeMarkdownPath": null,
"packProblemDir": "/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008"
}
}
53 changes: 53 additions & 0 deletions packs/graph-theory/problems/1008/CLAIM_LOOP.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Erdos Problem #1008 Claim Loop

This claim loop generalizes theorem-search-verification work directly from the canonical theorem loop, even when no richer bridge is present yet.

## Current State

- Claim loop mode: `baseline`.
- Current claim surface: `route_scaffolding`.
- Active route: `c4_free_lean_archive`.
- Route summary: Keep the solved `C_4`-free density record explicit and preserve the Lean-facing archive posture.
- Next honest move: Record the best public/formalization hook and checkpoint the archive packet.

## Feature Extractors

- `pack_route_state`: ready | Reads pack route, ticket, and atom state as the baseline theorem-search context.
- `theorem_loop_snapshot`: ready | Uses the canonical theorem-loop as the current claim-surface ledger.
- `cluster_graph_theory_features`: ready | Exposes graph-theory archive or theorem-state context to the claim loop.

## Claim Generators

- `baseline_route_claims`: ready | Promotes active routes, ready atoms, and next-honest-move records into candidate claims.
- `theorem_agenda_claims`: ready | Turns theorem agenda items into explicit candidate claim tickets.

## Claim Falsifiers

- `theorem_loop_consistency_check`: ready | Rejects claims that overstate the current theorem-loop claim surface.
- `artifact_boundary_check`: ready | Rejects claims unsupported by canonical artifacts already present in the pack.

## Verifier Adapters

- `canonical_artifact_reader`: ready | Reads theorem-loop, route, and pack artifacts as verifier-facing evidence.

## Candidate Claims

- `promote_ready_atom`: ready | Turn ready atom `G1008.G1.A1` into the next theorem-facing checkpoint. | Record the best public/formalization hook and checkpoint the archive packet.
- `tighten_active_route_claim`: ready | Compress the active route `c4_free_lean_archive` into the next honest theorem-facing claim unit. | Record the best public/formalization hook and checkpoint the archive packet.

## Commands

- Problem surface: `erdos problem show 1008`
- Problem artifacts: `erdos problem artifacts 1008`
- Theorem loop: `erdos problem theorem-loop 1008`
- Theorem refresh: `erdos problem theorem-loop-refresh 1008`
- Claim loop: `erdos problem claim-loop 1008`
- Claim refresh: `erdos problem claim-loop-refresh 1008`

## Sources

- claimLoopJsonPath: `/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/CLAIM_LOOP.json`
- claimLoopMarkdownPath: `/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/CLAIM_LOOP.md`
- theoremLoopJsonPath: `/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/THEOREM_LOOP.json`
- theoremLoopMarkdownPath: `/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008/THEOREM_LOOP.md`
- packProblemDir: `/Volumes/Code_2TB/code/erdos-problems/packs/graph-theory/problems/1008`
Loading
Loading