docs(azure): Kimi-only crosscheck routing with visible fallback, and R10 Slack team exposure - #259
Merged
Merged
Conversation
…R10 Slack team exposure Two further owner directives on 2026-08-19, recorded as a second amendment in the requirements section: All crosscheck routes through the Kimi lane for every author family. One reviewer family outside both author families satisfies the paradigm everywhere, unbinds review capacity from the pi-codex subscription profiles that no-mistakes and the author fleet consume, and makes the lane scalable for firstmate and for engineers' on-demand use. pi-codex stays as a dormant fallback behind a config flip, never deleted, with lane identity named in every review and a status read showing what is serving, so a silent fallback is impossible. R6 work and acceptance updated to match; R7's stale claude-via- codex line corrected. New R10: Slack v1 team exposure. Engineers tag the bot with a PR link, the Kimi lane reviews, findings return as a thread reply. Socket Mode (no public inbound endpoint), org-allowlisted repositories only, per-submitter daily metering under C3, lane named in every reply, Bugbot coexists on engineers' PRs. Builds after R6; order-of-work notes it can be pulled forward.
… degradation, stale claims The review caught the requirement clause still saying bidirectionality while the standing design is one-way into one outside family; the amendment and the R6 title now state the actual requirement (no author reviewed by its own family). The fallback path is recorded honestly: flipping to pi-codex includes crosscheck-same-model on and accepts same-family review of codex-authored work as a loud, recorded degradation, in the routing paragraph, the Work list, and the acceptance. R5 now names the pi roster as the dormant fallback rather than claiming crosscheck is done on it; C3 owns R10's per-submitter metering and listener cost and its stale four-slots state line is refreshed to record the 2026-08-19 surrender cleanup; R10 uses the doc's status vocabulary.
… stale after the cleanup
The C3 state refresh left R4 still asserting one stranded work disk on the
subscription; that disk was deleted by owner direction on 2026-08-19 after no
cell record could be found for the sanctioned close. R4 now records the
deletion and that only the unfixed root cause remains. Also aligns the
amendment's requirement phrasing with R6's ('reviewed only by its own model
family') and rewraps two long lines.
…ne with the custody trade recorded The owner revised the model pick from Kimi-K2.7-Code to GLM-5.2 on quality and accepted the Fireworks custody shape after verification: Microsoft disclaims data handling for the lane, the zero-data-retention promise is Fireworks' own policy (volatile memory, no logging by default, chat completions only - the Responses API and its 30-day store default are forbidden here), and billing lands as Azure consumption with startup-credit coverage for pay-per-token Data Zone Standard, to be confirmed by a small live decrement before volume. The 15-day retirement notice on Fireworks pay-per-token models is recorded as an accepted operational risk and a standing reason the pi-codex fallback stays armed. Work list gains the feature registration, the credit-decrement check, the reasoning_effort passthrough smoke, and the chat-completions pin.
…it the C3 cleanup attribution
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.
What
Records the owner's two further 2026-08-19 directives in docs/azure-requirements.md:
Both amendments are recorded in the requirements section itself so the historical quotes stay visibly historical.
Verification
Docs-only. No em dashes, no bold; the static contract's asserted sentences (withdraw line, 'Release remains the only exit') are untouched.