This release introduces sharper feedback while you edit and publish arguments.

Clearer save-time feedback in normal mode. When you save an argument in normal mode, Proposit now catches and explains specific logic problems before they cause issues elsewhere — most notably, mixing axioms and citations as supporting evidence for the same claim. Previously a save like that would succeed and the problem only became visible later (or showed up as a generic engine error). Now the save is rejected with a clear list of issues to fix, attached to the specific claim or premise that has the problem. If you're an advanced-mode user, this gate is off and your save accepts the in-progress state as before — the same problems still surface as inline hints on the argument view.

Publish-time consistency check. The publish flow now runs the strictest validation pass before promoting your draft. If your argument has structural issues that would cause confusing display in the published view, publish returns a list of the specific violations rather than going through with a half-formed publication. (Most arguments edited in normal mode are already valid by the time you reach publish — this gate is the safety net.)

Vocabulary refresh, under the hood. The propositional-logic library was updated to a vocabulary that better matches the way Proposit talks about supporting evidence. Citation edges now use "claim" / "supporting claim" terminology in place of "citing claim" / "source claim" everywhere — same edges, same behavior. A new claim category, axiomatic, was reserved so that future support for self-evident propositions can ship without another schema migration round-trip; the category is not yet exposed in the UI.

Canonical citation shape on save. Citations attached to a claim now always end up in a clean, canonical shape on save — the parenthesization that previously surfaced inconsistently when you had two or more citations is now applied uniformly.

Inline violation banner. When the save-time grammar check rejects a change, Proposit now shows a clear inline banner on the argument view listing the specific issues that blocked the change (with each issue's code and explanation). Previously these rejections surfaced as a generic error and the user had no actionable detail.

Inference operators from scratch. Building an implies or iff no longer requires you to first lay down an AND and then cycle to it — there's a dedicated "→ Add inference" affordance now. On an empty premise it sits next to "+ Add first claim" and walks you through both the antecedent and consequent in one dialog (with an Implies / Iff toggle). On a premise that already has content, the same affordance lives in the premise gear menu: it wraps your existing claim into the consequent and asks for an antecedent. Both flows let you draft a new claim inline or pick an existing one.

Coming next. The advanced editing mode (a per-user setting that lets you build arguments more freely, with inline hints instead of save-time rejection) is wired into the back-end and waiting on the matching UI affordance.

Under the hood. The propositional-logic library was updated to the next patch (1.0.2). The headline change is invisible from the UI but load-bearing: every argument with one or more premises now always has exactly one designated as its conclusion. Previously the system would let an argument briefly drift into a "premises but no conclusion" state during editing, and downstream features (publish gate, repair flows, fork-aware diff) had to defensively handle that case. Now the engine itself prevents that state from arising through any user action — the first premise added to a new argument becomes the conclusion automatically, and deleting the current conclusion in a multi-premise argument re-designates one of the remaining premises rather than leaving the argument in a half-built state. If you ever see a "conclusion required" warning at publish time, it now means the argument was loaded from an older snapshot that predates this guarantee, not that you forgot to mark one.

Cleanup pass. Removed 4 abandoned, never-published drafts that were structurally incomplete and predated the grammar checks. Affected drafts were created Aug–Sep 2025 and never touched since. The cleanup runs automatically on deploy of this release — no action needed on your end.