docs(openproject): two-arm pattern + nexgen convergence + knowable_from pin#16
Merged
Merged
Conversation
…om pin Three additions to the OpenProject transcoding doc following discovery of in-flight work in AdaWorldAPI/ruff and AdaWorldAPI/openproject-nexgen-rs: - §10.1: name the two complementary arms (narrow SPO via ruff_spo_triplet + ruff_ruby_spo scaffold; wide OGAR via this doc / ogar-from-ruby). One AST parse fills both; complementary, not competing. - §10.2: nexgen op-surreal-ast (C16a) / op-codegen-projection (C15) convergence as special cases of OGAR Class -> catalog::TableDefinition via Sprint C16b new_for_ddl + with_* builders. No collision. - §10.3: durable interface pin for knowable_from meet-point between ogar-adapter-surrealql (OGAR, queued) and lance-graph-planner:: temporal::classify (runtime session, in flight). Authoritative OGAR-side source until bardioc/CROSS_SESSION_COORDINATION.md mirrors. - §10.4: producer queue ordering (this PR -> ogar-from-elixir scaffold -> ogar-adapter-surrealql -> lance-bind boundary). - §11: cross-references extended with ruff fork, nexgen, surrealdb fork, and temporal-deinterlacing links. Renumbered old §10 Cross-references to §11. Pure docs; no IR change. https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OpenProject companion — two-arm pattern + nexgen convergence + knowable_from pin
Three durable additions to the OpenProject transcoding doc (merged in #14) following discovery of substantial in-flight work elsewhere in the AdaWorldAPI ecosystem. Pure docs, no IR change.
What lands
ruff_spo_tripletcore +ruff_ruby_sposcaffold) and the wide OGAR arm (this doc / futureogar-from-ruby) as complementary. One AST parse fills both; SPO answers "what depends on what" (data-dep DAG, feeds Rubicon'sKausalSpec::Depends), OGAR answers "when fires, guards, commits" (lifecycle FSM). Producer pairs per domain.openproject-nexgen-rsshipsop-surreal-ast(C16a, mirror ofcatalog::*),op-codegen-projection(C15, DDL renderer),op-codegen-pipeline/-bucket. Special cases of OGARClass→surrealdb-core::catalog::TableDefinitionvia Sprint C16bnew_for_ddl+with_*builders. No collision.knowable_frommeet-point pin. The substrate's four interlaced frames (lance/surrealql/ractor/thinking) deinterlace throughlance-graph-planner::temporal::classify. The SurrealQL frame'sknowable_fromis sourced byogar-adapter-surrealql(queue Sprint 3: Action vocab (ActionDef + ActionInvocation) + ogar-adapter + SPO+TeKaMoLo emission #3) and consumed bytemporal::classify. Authoritative OGAR-side pin — should mirror tobardioc/CROSS_SESSION_COORDINATION.md.ogar-from-elixirscaffold →ogar-adapter-surrealql→lance-bind.Why now
Prevents three collisions:
ogar-from-rubyvsruff_ruby_sporeading as duplication when they're complementary.op-surreal-astreading as "already did SurrealQL" when it's OP-specific that OGAR generalizes.knowable_from— without the pin, two consumers could dual-source it.Out of scope
No IR changes; no new crate scaffolds (those are queue items #2 and #3); no changes to bardioc's coord doc (runtime-session-owned; §10.3 documents what to mirror, the mirror is theirs to apply).
https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY