docs(commercial): separate USD 20B quality from contract readiness - #162
Draft
seonghobae wants to merge 12 commits into
Draft
docs(commercial): separate USD 20B quality from contract readiness#162seonghobae wants to merge 12 commits into
seonghobae wants to merge 12 commits into
Conversation
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 3, 2026
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
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.
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.mdis the canonical customer-contract/readiness document and retains the existing2_000_000_000KRW predicate;docs/commercial/usd-20b-product-quality-bar.mddefines the USD 20 billion ambition as a buyer-visible product/security/operability/release/integration quality bar, never as tenant pricing, billing, ARR, accounting, orannual_contract_value_krw;20b-krwpath becomes a compatibility shim because protected-main evidence manifests currently publish that path; this avoids an unversioned API/document-manifest break;TARGET_SALE_VALUE_KRWto 20B KRW and keeps customer/readiness, product-quality, and compatibility authorities explicit.TDD / single-writer history
RED
6adb83af0be136ae96c95132fa625bf752f24642added the executable authority-boundary contract before the canonical documents existed. GREEN lineage007146411f4585ae8ee2410e4a54d44ff65e3cbd→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 remainsTARGET_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 integration — 2026-09-05 KST
Protected/default
mainis exact5829a0f08d78de464dd24393ce5d0f25fba9d126after merged #159. The prior candidatebd41d8430b269cbd9b440d225e1d53b28a4fe817was 11 protected commits behind. Fresh compare proved the intervening protected delta changed only.github/workflows/{ci,fuzz,scorecard-analysis}.yml,AGENTS.md, and the two workflow runner/queue contract tests; none overlaps this six-file commercial-authority slice.The branch was therefore repaired non-destructively with merge commit
c5ee24d5ddcf2031decb21869410aef51cdda6fa, preserving the full prior branch and exact protected main as parents. No force push or destructive rebase was used. Fresh compare against protected main reportsbehind_by=0; the effective delta is exactly:CLAUDE.mdREADME.mddocs/commercial/20b-krw-sale-readiness.mddocs/commercial/2b-krw-customer-contract-readiness.mddocs/commercial/usd-20b-product-quality-bar.mdtests/commercial_authority_architecture.rsAll predecessor workflow/review evidence is historical after this ancestry movement. Exact-head runs have materialized for
c5ee24d5...but are currently non-passing/queued: CI33907112694, Security Scan33907112695, SAST Semgrep33907112712, CodeQL PR33907112611. Queued state is not merge evidence and is covered by the central runner/control-plane owner path.Keep Draft until unchanged
c5ee24d5ddcf2031decb21869410aef51cdda6fahas terminal exact-head repository/security/coverage/central review/thread/governance evidence and the solo-maintainer rule is satisfiable without self/model approval. Do not use routine bypass, gate weakening, no-op dispatch commits, mutable foreign authority, or predecessor evidence reuse.