ck-conjoinlisted

# C→K — conjunction The terminating operator. A concept becomes a proposition with definite status, and the design of that branch is complete. Read `${CLAUDE_PLUGIN_ROOT}/references/GRAMMAR.md` first. ## The test Take the leaf's proposition and ask K, as it now stands, whether it holds. - **K says yes, with evidence** → conjunction. The concept is now knowledge. - **K says no, with evidence** → refutation. Also a real result: the space shrank and you know why. - **K still can't say** → nothing happened. Leave it `open`. This is the normal outcome and you should expect it most of the time. ## The trap Conjunction is *not*: - "this seems buildable" - "we've decided to do this one" - "this resembles a product that exists" Those are enthusiasm, prioritisation, and pattern-matching. The requirement is narrow: **something must now be known that was not known before.** If you cannot write that sentence as a K entry, the conjunction has not happened, and `ck` will refuse the status change — by design. Watch for the commonest cause of a false conjunction: a restrictive partition that was mislabelled expansive. If the branch closed suspiciously easily, re-read its `breaks` line and ask whether it really violated anything. ## Doing it Conjunction is two commands, in this order. The K entry comes first because it *is* the conjunction; the status change is bookkeeping. ```bash ck add-k <session> \ --text "What is now known." \ --status true \ --source "<the evidence