docs(commercial): separate USD 20B quality from contract readiness

[seonghobae]

Fixes #161 only when this candidate reaches protected main.

Product-contract repair

Wardnet had one misleading historical filename, docs/commercial/20b-krw-sale-readiness.md, even though the runtime contract and document body define a 2B KRW customer-contract readiness predicate. That naming defect made it too easy to conflate a customer field with the standing USD 20 billion software-sale quality ambition.

This slice keeps the two authorities separate without changing runtime pricing or readiness behavior:

• docs/commercial/2b-krw-customer-contract-readiness.md is the canonical customer-contract/readiness document and retains the existing 2_000_000_000 KRW predicate;
• docs/commercial/usd-20b-product-quality-bar.md defines the USD 20 billion ambition as a buyer-visible product/security/operability/release/integration quality bar, never as tenant pricing, billing, ARR, accounting, or annual_contract_value_krw;
• the old 20b-krw path becomes a compatibility shim because protected-main evidence manifests currently publish that path;
• README and CLAUDE guidance point to the canonical 2B customer-contract document plus the separate USD 20B quality document;
• the repository integration test rejects remapping TARGET_SALE_VALUE_KRW to 20B KRW and keeps customer/readiness, product-quality, and compatibility authorities explicit.

TDD / single-writer history

RED 6adb83af0be136ae96c95132fa625bf752f24642 added the executable authority-boundary contract before the canonical documents existed. GREEN lineage 007146411f4585ae8ee2410e4a54d44ff65e3cbd → 299ccbd124d8a74243c6a6a50d6e1ff97ca28806 → 2de85e45bf99225561728b45914182e9d2fed901, followed by formatting/reference repairs, supplies the separated authorities and compatibility shim.

A later gap-ledger attempt was removed after fresh inventory proved PR #130 already owns docs/product-technical-gap-baseline.md. Current effective delta does not touch that single-writer path. The runtime constant remains TARGET_SALE_VALUE_KRW = 2_000_000_000; this PR does not assert that 2B KRW is a product valuation and does not create billing/accounting authority.

Fresh protected-main adoption — 2026-09-08 KST

Protected/default main advanced from the previously adopted 5829a0f08d78de464dd24393ce5d0f25fba9d126 through merged #171 to exact a52ccd0a24a727d9349bb32def7713882d8cad1e. Fresh comparison of predecessor c5ee24d5ddcf2031decb21869410aef51cdda6fa against current protected main proved the only effective candidate delta remained the six commercial-authority paths listed below; #171's protected-only ADR delta did not overlap them.

The branch therefore adopted exact protected main non-destructively with two-parent merge commit 81a1705c04dd3cae4ea4e6466ae09b9c956517d6, preserving predecessor c5ee24d5... as first parent and exact protected a52ccd0... as second parent. The merge tree is exact protected-main tree plus the six previously reviewed blobs. No force push, destructive rebase, broad source reconstruction, or foreign-owner state was introduced.

Fresh compare is behind_by=0, merge base exactly a52ccd0..., and the full protected-main-relative delta remains exactly:

• CLAUDE.md;
• README.md;
• docs/commercial/20b-krw-sale-readiness.md;
• docs/commercial/2b-krw-customer-contract-readiness.md;
• docs/commercial/usd-20b-product-quality-bar.md;
• tests/commercial_authority_architecture.rs.

Exact-current evidence

Current exact head is 81a1705c04dd3cae4ea4e6466ae09b9c956517d6. All predecessor workflow/review conclusions are historical after the real ancestry movement.

• CI 34169428002 — SUCCESS;
• Security Scan 34169428030 — SUCCESS;
• SAST Semgrep 34169428023 — SUCCESS;
• CodeQL PR 34169428031 — FAILURE at the central delegated terminal-receipt boundary, not a commercial-authority source finding.

This unchanged head is already consumer evidence for canonical central owner issue .github#1929. The active repair is .github#1902; because its head is mutable until protected, this product PR does not pin a stale central candidate or consume it as authority. Re-read that owner path live before integration. Wardnet leaves this clean source head unchanged rather than manufacturing a redispatch.

Live organization ruleset 18156473 still requires one generic approving review with no named/code-owner/last-push reviewer and exposes OrganizationAdmin/always bypass. .github#772 owns the solo-maintainer governance repair. Self/model approval and routine administrator bypass remain forbidden.

Keep Draft until one unchanged exact head has terminal then-live repository/security/coverage/package/SBOM/provenance/review/thread/governance evidence and fresh protected-base compatibility. No gate weakening, force push, destructive rebase, mutable foreign authority, source copy, cross-service SQL, or predecessor-evidence transfer.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}