Repository navigation
Separate software-sale quality bar from customer contract-value readiness #161
Description
Problem and authority boundary
Wardnet has two distinct commercial authorities that must remain separate: the standing USD 20 billion product-quality ambition and tenant/customer contract metadata, including protected runtime TARGET_SALE_VALUE_KRW = 2_000_000_000. The USD 20B bar is not tenant pricing, ARR, accounting truth, or a reason to alter the 2B KRW readiness predicate.
Protected/default truth is now main@f8260f1e03836039ff9463dd99fa982e4e270c4b after protected #155. The protected runtime 2B KRW predicate remains unchanged.
Current owning candidate — 2026-09-11 KST
PR #162 remains the bounded authority/documentation candidate. Reverse-direction restack #315 ordinarily adopted current protected main without force or destructive rebase. Current exact #162 is 3e3a19a115448d5787ceaa34929018fb832fdd3d, based on current protected main@f8260f1e03836039ff9463dd99fa982e4e270c4b.
Its protected-main-relative delta remains exactly six paths: 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, and tests/commercial_authority_architecture.rs. Protected #155 authentication/security truth is inherited rather than copied. PR #130 remains sole writer for docs/product-technical-gap-baseline.md; #162 does not compete for that path.
Exact-current evidence
On unchanged exact 3e3a19a115448d5787ceaa34929018fb832fdd3d:
- CI
34577138782— SUCCESS - Security Scan
34577138789— SUCCESS - SAST Semgrep
34577138762— SUCCESS - required CodeQL PR
34577138720— FAILURE at the delegated current-head terminal-verdict settlement boundary
The source/authority separation is therefore causally GREEN in Wardnet-owned deterministic/security lanes but not merge-authorized. .github#1929 owns delegated CodeQL settlement, .github#772 solo-maintainer governance, and .github#712 runner/materialization. Wardnet does not duplicate those owner paths, manufacture source churn or promote predecessor evidence.
Completion gate
Keep #162 Draft and this issue open until #162 or a verified complete successor carrying every unique authority/document/test delta reaches protected main; protected runtime continues to preserve the accepted 2B KRW customer predicate unless independently changed by an accepted product contract; and one unchanged integration candidate has every then-live repository/security/coverage/package/SBOM/provenance/CodeQL/review/thread/governance gate terminal-valid with fresh protected-base compatibility.
No predecessor-evidence reuse, self/model approval, routine administrator bypass, force push, destructive rebase, gate weakening, mutable foreign dependency, source copy or cross-service SQL.
Activity
seonghobae commentedon Sep 3, 2026
Active bounded repair is Draft PR #162, exact head
3b5aa81664ed8f2fd8b29438418be920f43f93e0on protectedmain@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 historical20b-krwdocument path only as a compatibility shim while published evidence-manifest references still depend on it. RED6adb83af0be136ae96c95132fa625bf752f24642established 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 commentedon Sep 3, 2026
PR #162 continues to own the commercial-authority separation, but a fresh concurrent-lane inventory corrected one attempted extension. The initial RED/GREEN
05d5da8436047799d6b91054abece70775fc43c7→0c9ea796a0b450222e205df0f7e615d5211930e3was based on the protected-main absence ofdocs/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 repaire0ea22ed1fe278af331f0e47d11a291f18aaca85removes the duplicate fitness requirement and current headbd41d8430b269cbd9b440d225e1d53b28a4fe817removes 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.