docs(rfc): BYOK fail-closed billing model (CTO-refined) #2329
Reference in New Issue
Block a user
Delete Branch "rfc/byok-fail-closed-billing"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The 4 hard requirements: explicit selection→adapter; credential required + validated at CREATE (fail-closed); liveness-validate (not just presence); fail loud, never silent. Spec for feat/byok-create-gate-and-liveness.
SOP Checklist (RFC#351)
SOP-ack (engineers, non-author core-security): verified the PR fills each checklist item.
/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack root-cause
/sop-ack five-axis-review
/sop-ack no-backwards-compat
/sop-ack memory-consulted
qa-review APPROVE (core-qa): checklist testing claims are consistent with the diff; CI / all-required green on head. SOP qa gate satisfied.
security-review APPROVE (core-security): fail-closed / no-silent-skip posture verified for the security surface in this change. SOP security gate satisfied.
/qa-recheck /security-recheck /refire-tier-check
/security-recheck
/refire-tier-check
/security-recheck
/refire-tier-check
APPROVED after independent current-head 5-axis review at
4b3eb5022a.Correctness: the RFC cleanly documents the fail-closed BYOK billing contract: model/provider selection stays registry-derived, BYOK must require a credential at create time, keyed credentials need liveness validation, and failures must be loud instead of silently falling through to platform billing. The current-state audit and scoped gaps line up with the stated implementation target.
Robustness/security: positive design hardening. It distinguishes missing, invalid, rate-limited, provider-5xx, timeout, and OAuth/no-server-surface cases rather than collapsing them into a single path. Performance: docs-only; the RFC calls out probe latency/timeouts. Readability: clear requirements, non-goals, risks, and test plan.
Cross-PR overlap guard: narrowed docs/RFC overlap check found no open sibling touching
docs/architecture/byok-fail-closed-billing.md. No semantic conflict found.APPROVED after independent current-head 5-axis review at
4b3eb5022a.Correctness: the RFC accurately frames the fail-closed BYOK create/provision gaps and keeps implementation scope to documentation.
Robustness: calls out create-time presence, liveness, provision re-checks, timeout/429/5xx handling, and OAuth no-server-surface nuance.
Security: strengthens fail-closed/no-silent-platform-billing posture; no secrets or auth bypass introduced.
Performance: no runtime code path changed; latency risk from future provider probes is explicitly bounded.
Readability: clear requirements, gaps, non-goals, risks, and test plan.
Cross-PR/overlap guard: this PR only adds docs/architecture/byok-fail-closed-billing.md; no open PR in the current sweep touched the same file, and there are no overlapping runtime hunks to reconcile.
5-axis review complete on current head
4b3eb5022a. APPROVED: docs-only RFC, matches current code state (BYOK create-time presence/liveness gaps still exist on main, provision gate is presence-only), no security fail-open introduced, test plan is appropriate, no runtime side effects, and no cross-PR file overlap with the live implementation PR #2328.