spec: #93 resolution — OpenAPI generator lands as pxf openapi in protowire - #172
Merged
Conversation
trendvidia
force-pushed
the
rfc001-decision-93
branch
from
July 25, 2026 11:24
0d16a52 to
b13c4f9
Compare
This was referenced Jul 25, 2026
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.
Decision record for docs/RFC-001-issues.md §#80, per the approved workflow (closes the landing-site question on #93).
Landing site:
pxf openapisubcommand in trendvidia/protowire — no new repo. pxfed excluded (deprecated, superseded by goed); standaloneprotowire-openapirejected: the generator is a boundary renderer over artifacts this repo already owns — the lowered image (pxf build, #164/PR #167) and the doc pack (pxf docs build, #170).pxfaccretes the familybuild/docs build/openapi. Records the binding format principle (JSON/YAML at the integration boundary only) and carries the open M8 design gaps (operation surface, visibility tiers, since-derivation) forward to the implementation phase.Refs #93.