Different confidence signal
Those tools end when the model
says it's done and the diff looks right to you. lex-code ends when lex check
@@ -142,6 +148,41 @@
Why lex-code
+ What's a typed issue?
+ Work as a declared, checkable contract instead of a paragraph of prose — an API shape and
+ the examples that prove it, the acceptance a run either closes against or doesn't. Real
+ output, the same issue used in "Try it" below:
+ $ lex issue show aea6613fc9e96953bb1c89fb3c45ac7200f62a379acdee2a47e29bab4c938ced
+{
+ "acceptance": {
+ "api": [
+ { "kind": "added", "name": "zip",
+ "signature": "(xs :: List[A], ys :: List[B]) -> List[(A, B)]" }
+ ],
+ "examples": [ "zip([1,2],[\"a\",\"b\"]) => [(1,\"a\"),(2,\"b\")]" ],
+ "shape": "typed_delta"
+ },
+ "created_at": 1790252464,
+ "issue_id": "aea6613fc9e96953bb1c89fb3c45ac7200f62a379acdee2a47e29bab4c938ced",
+ "title": "add zip"
+}
+ Issues live in Lex's own op-log VCS: every accepted change is a content-addressed,
+ hash-chained op, and lex issue verify checks the acceptance against HEAD, not a
+ cached memory of it — which is why the same verdict can flip if the code it once verified is
+ later removed. Honestly: there's no web UI for any of this yet, just the CLI. Real, truncated
+ output from this repo:
+ $ lex op log
+op_id: 188906eedb0952d086826165b6e49148485936d9deb9b1155f1e349f9cadc019
+kind: modify_body
+parent: 021e626a7699e6940565cd7e2aa8b4a53e137d220327b6ed1e9e3f129fdae57c
+
+op_id: 021e626a7699e6940565cd7e2aa8b4a53e137d220327b6ed1e9e3f129fdae57c
+kind: add_function
+parent: c32da6062f16626dc4d5e5e84783ca642d92f7cb8d0879a1dfd767614de760b0
+ ...
+