Skip to content

Align RFC 0022 with landed composition decisions - #242

Merged
kikashy merged 1 commit into
mainfrom
align-233
Oct 22, 2026
Merged

kikashy merged 1 commit into
mainfrom
align-233

Conversation

@kikashy

@kikashy kikashy commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Closes #233.

What it adds

  • Aligns RFC 0022's base bounds with the graph-node ceiling and document profiles decisions.
  • Carries one composite handoff entry per selected Core route while preserving legacy target form.
  • Closes interface remapping in favor of Dialect-owned conversion and points shared packaging to
    a future Exchange entry kind.
  • Keeps RFC 0022 at Draft status and records the revision in the changelog.

Checks

== check summary (dev.json) ==
handover: boundary 2 paths, shared 3 paths; see AGENTS.md "Before you hand over"
PASS     local-paths              0s
PASS     agent-docs               0s
    sync-agent-docs: CLAUDE.md matches AGENTS.md
PASS     diff-check               0s
PASS     repository-tests         85s
    Ran 250 tests in 84.981s
    OK
PASS     policy-prototype         1s
    Ran 38 tests in 1.218s
    OK
PASS     policy-contract          2s
    Ran 13 tests in 2.667s
    OK
PASS     policy-official-draft    2s
    Ran 16 tests in 2.518s
    OK
== 7 passed, 0 failed, 0 skipped, 0 not run ==

Not in this PR

No graph schema, implementation, conformance corpus, Exchange entry format, or RFC status change is
included. RFC 0002 and the reference runtime state no numeric graph-node maximum, so this revision
does not invent one.

A Codex session wrote the change.

Set reusable-subgraph base bounds to depth four and the expanded graph's
RFC 0002 node ceiling. Record route-aware handoff provenance, keep the
single-target envelope stable, assign remapping to Dialect, and direct
cross-installation packaging to the Exchange.

Co-Authored-By: Codex <noreply@openai.com>
Signed-off-by: kikashy <kikashy@hotmail.com>
@kikashy

kikashy commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

Review (OpenAI gpt-5.6-sol, effort medium, 2026-10-23), reviewed SHA 1a8d174

Clean-room clone at the head, probes under .review/; CI green before the round. The report verbatim:

Findings: none.

Verified:

  • All four required alignments match the cited decisions.
  • RFC remains Draft, numbered 0022, with scope note intact.
  • No contradictory depth 8 or 256-instance limits remain.
  • All 15 JSON blocks parse.
  • Four leaf packs pass Core 0.2.0-draft structural and semantic validation.
  • Routed handoff envelope matches RFC 0025; single-target behavior remains unchanged.
  • Changelog entry accurately summarizes the alignment.
  • git diff --check passes; no tracked files changed during review.

merge: yes — reviewed SHA: 1a8d1748a7bd5211a66a91d3b57e533abf8aed54

Disposition: no findings; merged on the standing rule. The contributor of RFC 0022 was offered this alignment on the issue and did not take it within the day. Same vendor as the builder, not a cross-vendor claim.

@kikashy
kikashy merged commit 949444b into main Oct 22, 2026
6 checks passed
@kikashy
kikashy deleted the align-233 branch October 22, 2026 20:14
@github-actions

Copy link
Copy Markdown
Contributor

🎉 Thank you for your contribution to Judgment Pack!

If you’d like another task, choose a path that interests you:

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.

RFC 0022: align the record with the decisions on #129, #219, #232 and #170

1 participant