cloudbase-ai opened a new pull request, #7893: URL: https://github.com/apache/shenyu/pull/7893
Refs #7623. The issue explicitly requests design agreement before runtime implementation and Admin registration. Add a repository RFC that turns the proposal into reviewable execution and rollout contracts: - Separate judge assessment from rule policy, with PASS/FLAGGED/BLOCKED/UNAVAILABLE and explicit uninspected/windowed coverage. - Define bounded request replay, both reactive response writer paths, buffered/realtime/final-packet release boundaries, per-direction fail-open passthrough, and resource/cancellation ownership. - Provide a normative failure matrix, score-threshold semantics, finite configuration examples, and admission/buffering/serialized-payload budgets. Audit-only final-packet response behavior explicitly overrides enforcing-mode failure policy. - Identify integration gates: actual Admin sort overrides must preserve decoration order; moderation denials must not trigger model retries/fallback; unsupported protocol refusal framing cannot be advertised as supported. - List maintainer decisions, staged implementation/fixture requirements, mixed-version rollout constraints, and benchmark requirements before recommending numeric production defaults. The source integration observations were checked against `master@69ed0a256`, including `PluginData.sort` precedence, AiProxy's `writeAndFlushWith`, the request rewrite helper's lack of a per-call byte cap, and the response-capture placeholder. The document marks module/API/field/default proposals as unapproved. This PR does not add a plugin, change request processing, or claim the future acceptance tests have run. Validation: - Parsed both fenced JSON examples; checked their positive limits and batch/context budget relationship. - Resolved all eight repository-relative source links; checked Markdown table column consistency and balanced code fences; no TODO/TBD placeholders. - Fresh-reader passes identified and resolved ambiguities in plaintext extraction, response overflow, midstream fail-open byte replay, all-metadata responses, policy versus score results, audit-only failures, and effective plugin ordering. Remaining framing/default choices are explicit implementation gates and maintainer decisions. - `./mvnw -B -ntp -N validate apache-rat:check` passed on the rebased tree; RAT reported zero unapproved/unknown licenses. - `git diff --check` passed. Runtime unit/E2E tests were not run for this documentation-only change. The RFC is a discussion proposal; merging it must not be interpreted as shipping content moderation or establishing classifier accuracy. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
