Skip to content

Graph Climbing v0.3: standalone public core - #1

Merged
mj-deving merged 3 commits into
mainfrom
mj-graph-v03-standalone
Aug 13, 2026
Merged

mj-deving merged 3 commits into
mainfrom
mj-graph-v03-standalone

Conversation

@mj-deving

@mj-deving mj-deving commented Aug 13, 2026 •

Copy link
Copy Markdown
Owner

What changes

This makes Graph Climbing v0.3 a portability and clarity release candidate with one obvious standalone path:

one durable spec + tests and Git + one capable coding agent
  • rewrites the README, canonical protocol, and starter prompt around a five-minute serial workflow;
  • removes the two origin-project case studies, dated reviewer histories, origin-system-specific diagrams, and image-generation residue from the live tree;
  • preserves that historical material through the immutable v0.2.0 tag and a concise EVIDENCE.md boundary;
  • moves the unchanged durable-runtime and multi-worker contracts under advanced/;
  • moves optional harness bindings and the portable skill/checker under adapters/;
  • preserves the legacy skills/graph-climbing entrypoint as a zero-copy compatibility symlink to the adapter;
  • adds deterministic checks for named-system independence, serial frontier derivation, canonical-surface wording, legacy skill resolution, and every relative Markdown link.

Why

The previous tree truthfully described a runtime-neutral protocol, but its default inventory mixed the small serial kernel with the private origin project's case studies, tool-specific bindings, and advanced worker machinery. An outside adopter should not need to understand that system before running one climb.

The removed reports were useful origin evidence, but neither was independent replication. Keeping them in the current tree made the public surface look more mature and more system-dependent than the evidence supports.

Compatibility

The checker and multi-worker logic are relocated without logic changes. In Git checkouts that preserve repository symlinks, existing installations targeting skills/graph-climbing continue to resolve the exact adapter content through a relative symlink; there is no duplicated skill tree. All 79 pre-curation tests remain present; five new public-surface tests bring the total to 84. The frozen durable-worker contract retains its existing SHA-256 assertion.

The default path requires no private system, named model vendor, task tracker, skill loader, hook, or durable runtime. Bun remains optional for the reference checker; the README includes a manual frontier rule when Bun is unavailable.

Verification

  • bun test — 84 passed, 0 failed
  • bun run graph-check starter/SPEC.md — valid claim frontier
  • bun run graph-check examples/notes-cli/SPEC.md — valid vertical frontier
  • installed-entrypoint behavior check from an unrelated directory — skill readable and reference checker executable
  • isolated clean-directory behavior check — copied starter kit contained no named private dependency; valid spec derived only C-2; missing-probe spec failed nonzero
  • git diff --check

Evidence boundary

This PR does not claim independent replication, general productivity improvement, release publication, or maturity beyond an experimental reference implementation. The PR itself does not create a v0.3 tag or update the separate Gist. If merged, the planned release step is to tag the exact merge as v0.3.0 and synchronize the Gist to the tagged GRAPH-CLIMBING.md; the repository remains authoritative.

Reviewer focus

Please check that the serial path is genuinely sufficient for a cold adopter, that the legacy skill alias resolves without duplication, and that relocating advanced material has not weakened the preserved multi-worker contract or made any public links unreachable.

@mj-deving
mj-deving merged commit dfbca65 into main Aug 13, 2026
2 checks passed
@mj-deving
mj-deving deleted the mj-graph-v03-standalone branch August 13, 2026 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant