Skip to content

Graph v2: combined C1+C2 typed claims and dynamic component instances - #587

Open
buger wants to merge 1 commit into
mainfrom
poc/exp-0121-native-typed-claim-kernel
Open

Graph v2: combined C1+C2 typed claims and dynamic component instances#587
buger wants to merge 1 commit into
mainfrom
poc/exp-0121-native-typed-claim-kernel

Conversation

@buger

@buger buger commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Combined C1+C2

This PR combines the Graph v2 C1 typed-claim kernel with the C2 dynamic component-instance vertical slice.

Included

  • Human-readable YAML remains the configuration source of truth, with generated schema validation kept in sync.
  • A typed-claim plan, journal, and kernel provide immutable event authority, validation, replay, and exact claim provenance.
  • Dynamic keyed subgraphs use stable component, node, and generation identities while retaining one scheduler, one journal, and one runner.
  • Generated providers receive exact scoped context and declared claims only, including authoritative controller or attempt provenance.
  • Reconciliation evidence covers deterministic replay, reorder reuse, add/remove tombstones, and selective regeneration where unchanged components retain byte-stable identities and outputs.
  • Catalog and generated terminal batches validate fully before append, preserving atomic event order and avoiding partial publication.

Verification and retained failures

  • The configuration generator ran twice and was idempotent; generated source and JSON hashes remained stable.
  • Baseline-relative TypeScript validation completed with zero candidate diagnostics and exactly four pre-existing MCP diagnostics at src/mcp-server.ts lines 931 and 947.
  • The admission record retains the earlier failed TypeScript run and failed focused Jest run. Both were addressed through bounded type-authority and runtime-scheduling fixes without weakening reducers or oracles.
  • The final focused run passed 10 of 10 suites and 107 of 107 tests with zero snapshots.
  • This was a focused ten-suite admission run, not the repository-wide full test suite.

Explicit nonclaims

This PR does not claim support for nested expansion, tombstoned-key reactivation, cancellation, retries, leases, durable or distributed scheduling, or cross-process recovery. It also does not claim Proof or Probe integration, model/profile routing, model calls, or real-provider/project-onboarding quality.

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