Separate software-sale quality bar from customer contract-value readiness

[seonghobae]

Problem

Wardnet has two distinct commercial concepts that must never share one numeric authority:

1. the standing USD 20 billion software-sale quality ambition used as a product/security/operability/release quality bar; and
2. tenant/customer commercial metadata, including annual_contract_value_krw and the protected runtime TARGET_SALE_VALUE_KRW = 2_000_000_000 readiness predicate.

The protected runtime value remains 2B KRW. The USD 20B quality ambition is not customer pricing, ARR, accounting truth, or a reason to multiply the tenant contract threshold.

Protected/default source truth is main@5829a0f08d78de464dd24393ce5d0f25fba9d126 through #159.

Current owning candidate — 2026-09-05

PR #162, docs(commercial): separate USD 20B quality from contract readiness, is the bounded product-contract/documentation owner at exact c5ee24d5ddcf2031decb21869410aef51cdda6fa. It was non-force integrated with current protected main; fresh comparison recorded behind_by=0. Its effective protected-main-relative delta is exactly six paths:

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

The branch keeps TARGET_SALE_VALUE_KRW = 2_000_000_000 unchanged and makes the old misleading 20b-krw filename a compatibility shim rather than silently breaking existing evidence manifests. The executable architecture regression rejects remapping the USD 20B ambition onto tenant contract value.

PR #130 remains the sole writer for docs/product-technical-gap-baseline.md; #162 does not compete for that path. Broader product rename #114 touches the compatibility document only for name/path substitutions and must reconcile against whichever protected truth lands first rather than overwrite the commercial authority split.

RED → GREEN contract retained

• RED 6adb83af0be136ae96c95132fa625bf752f24642 established the authority-boundary regression before the canonical documents existed.
• Subsequent GREEN lineage created the distinct 2B KRW customer-contract document, the USD 20B quality-bar document, compatibility shim and matching references/tests.
• The runtime threshold remains 2B KRW; no billing/accounting bounded context is changed.

Current exact-head gate

Exact c5ee24d5... has materialized but non-passing current runs recorded on the owning PR:

• CI 33907112694 — queued;
• Security Scan 33907112695 — queued;
• SAST Semgrep 33907112712 — queued;
• CodeQL PR 33907112611 — queued.

All predecessor evidence is historical after protected-main integration. Queue/runner acquisition remains .github#712; solo-maintainer review-policy repair remains .github#772 / owner-plane successor #1644. Neither authorizes bypass or fabricated approval.

Completion gate

Close only after #162 or a verified successor carrying every unique authority/document/test delta reaches protected main, the protected runtime still preserves the accepted 2B KRW customer predicate unless independently changed by an accepted product contract, and one unchanged exact integration candidate has terminal current repository/security/coverage/package/SBOM/provenance/review/thread/governance evidence. No self/model approval, routine administrator bypass, force push, gate weakening, no-op dispatch commit, or predecessor-evidence reuse.

[seonghobae]

Active bounded repair is Draft PR #162, exact head 3b5aa81664ed8f2fd8b29438418be920f43f93e0 on protected main@cc15cc2c34daf8c104eeb83d52a6a66f3cd6e128. It preserves the existing 2B KRW customer-contract readiness predicate, separates the USD 20 billion software-quality ambition into its own buyer-evidence authority, and retains the misleading historical 20b-krw document path only as a compatibility shim while published evidence-manifest references still depend on it. RED 6adb83af0be136ae96c95132fa625bf752f24642 established the authority-separation contract before the canonical documents existed; the current lineage also repairs README/CLAUDE references. PR #154 is now closed without merge and carries no remaining source delta, so it is not an alternative authority. #162 remains Draft because its exact-head CI/security/SAST/OSV/Scorecard lanes are queued/non-passing; predecessor evidence does not transfer and no bypass applies.

[seonghobae]

PR #162 continues to own the commercial-authority separation, but a fresh concurrent-lane inventory corrected one attempted extension. The initial RED/GREEN 05d5da8436047799d6b91054abece70775fc43c7 → 0c9ea796a0b450222e205df0f7e615d5211930e3 was based on the protected-main absence of docs/product-technical-gap-baseline.md; live PR #130 already owns that exact file and explicitly tracks #161/#162. Keeping a second copy in #162 would violate the same-repository single-writer/path boundary. Forward-only repair e0ea22ed1fe278af331f0e47d11a291f18aaca85 removes the duplicate fitness requirement and current head bd41d8430b269cbd9b440d225e1d53b28a4fe817 removes the duplicate file. PR #130 remains the sole product/technical-gap baseline lane; #162 is again limited to the 2B KRW customer-contract vs USD 20B product-quality authority documents and their executable separation contract. The runtime 2B KRW threshold is unchanged. Exact-current-head CI/security evidence for #162 must be reacquired; no predecessor evidence transfers.