OpenSpec ships its verification command off by default

OpenSpec's front page presents the /opsx loop with a verify stage among its commands. The project's own documentation adds a qualification the front page does not: "By default, OpenSpec uses the core workflow profile (propose, explore, apply, update, sync, archive). If you want the expanded workflow commands (new, continue, ff, verify, bulk-archive, onboard), configure them with openspec config profile and apply with openspec update." The command table lists /opsx:verify as "Validate implementation against artifacts (expanded workflow)". The same document describes apparatus the front page leaves out: artifacts form a directed acyclic graph, state is read from whether a file exists on the filesystem rather than held in a phase variable, and the stated principle is "Dependencies are enablers, not gates".

Why it matters: A verification stage you have to opt into is a different adoption story from one every installation gets. If you were counting OpenSpec as evidence that spec-conformance checking is spreading as a default convention, the count is smaller than the front page suggests. The part that does ship by default, a dependency graph that reports readiness from the filesystem instead of from a declared phase, is the more useful piece of harness design in the documentation.