@josfox/jos 4.1.0 → 5.0.0

package/LICENSE

@@ -1,21 +1,208 @@
-MIT License
-
-Copyright (c) 2024 JOS Open Standards Foundation
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+---
+
+Copyright 2026 JOSFOX LLC
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use the files of this repository that are not the specification text (the JSON Schema, the test vectors, the examples, the tools) except in compliance with the License. The specification text (SPEC-2.0.md, PROMISES.md and the documents of the registration package) is licensed under CC BY 4.0: see LICENSE-SPEC.md.

package/PROMISES.md

@@ -0,0 +1,52 @@
+# Promises of @josfox/jos
+
+Every promise of `jos`: what it is for, what 4.1.0 did, what 5.0.0 does with jos-core 2.0.0, what is planned, and the gate that proves today's behaviour. Generated from `promises.json` by `npm run promises:md`; do not edit by hand (`npm test` fails when this file is stale).
+
+Run the gate: `node --test test/promises.test.js` (also part of `npm test`). Each gate runs in a new temporary folder with a copy of `examples/` and the documents of `docs` in `promises.json` (`minimal-13.jos` is the 13-key Minimal Valid Artifact of the 4.1.0 page, unchanged), an empty temporary HOME, no provider key and a fake `curl` and `ollama` first on PATH: nothing reaches the network or your `~/.jos`. A gate checks the exit code shown and the text it expects in the output (see `promises.json`).
+
+Planned: `5.0.0` the final release of this host, `rc.9` the next release candidate of the specification and jos-core, `2.1` the next minor version of the format and kernel, `F3` a later phase.
+
+Status: delivered 12 · delivered differently 18 · planned 6 · dropped 2 (38 promises).
+
+| Feature | Intent | 4.1.0 | 5.0 | Planned | Gate |
+|---|---|---|---|---|---|
+| jos alone: discovery | Typing jos says what it does and which documents are here, without running or writing anything. | `jos` alone printed the help. | **delivered differently.** The essence in six lines, then the .jos documents of this folder and one down, each with its validate and run command. | — | `jos` → 0 |
+| jos start | Four working examples that need no key and no network, in one command, never overwriting anything. | Quick start cloned an external starter repository (jos-repo-starter, no longer maintained) and ran `jos llm` with Ollama. | **delivered differently.** `jos start [dir]` writes hello, flow, sealed and limits with a README; refuses (1) if any exists. | — | `jos start` → 0<br>`jos run jos-start/hello.jos` → 0<br>`jos run jos-start/sealed` → 0<br>`jos start` → 1 |
+| Self-check and version | One command says the installation works and which host and kernel it uses. | `jos verify` ran verification.jos; `jos --version` printed 4.1.0. | **delivered differently.** `jos verify` runs examples/hello.jos in a temporary folder; `--version` names the host and the jos-core it found. | — | `jos verify` → 0<br>`jos --version` → 0 |
+| Declare an intention | A .jos says what to do, when it is done and what to avoid, and jos shows it before it runs. | 0.0.7 intention, success_criteria and guardrails; `jos init` wrote a 0.0.7 file and a .sig.json sidecar. | **delivered differently.** `jos init` writes a 2.0 atom validated by jos-core; `run` and `validate` print Intention, Done when, Avoid, Limit; `validate` also prints what jos-core infers and flags what is not declared, and `--strict` refuses (2) a document that does not write its objective, criteria and guardrails. | — | `jos init demo` → 0<br>`jos run demo.jos` → 0<br>`jos run examples/01-hello.jos` → 0<br>`jos validate examples/01-hello.jos --strict` → 0<br>`jos validate fail-criterion.jos --strict` → 2 |
+| Validate without running | Checking a document never executes it; a document is one strict UTF-8 JSON object, read by content, not by file name. | `jos validate` checked 13 keys and ran nothing; JSON.parse let the last duplicate key win. | **delivered differently.** `validate` and `run --dry-run` start no step; any file name is read by content; duplicate keys, a BOM and (since jos-core 2.0.0-rc.8) an integer outside ±2^53 are invalid (2). | — | `jos validate noexec.jos` → 0<br>`jos validate noexec.txt` → 0<br>`jos run noexec.jos --dry-run` → 0<br>`jos validate dup-keys.jos` → 2<br>`jos validate bom.jos` → 2<br>`jos validate big-integer.jos` → 2<br>`jos examples/01-hello.jos` → 1 |
+| Every criterion evaluated | Done means every success criterion was checked, and the verdict of each one is shown. | success_criteria was text; nothing evaluated it. | **delivered differently.** Structured criteria are evaluated, each with a verdict line; a failed one is code 1; text criteria are recorded as descriptive. | — | `jos run examples/02-criteria.jos` → 0<br>`jos run fail-criterion.jos` → 1 |
+| Guardrails enforced | Guardrails are enforced, not suggested: a forbidden command never starts and a limit stops the process. | guardrails.avoid was not enforced; x_run_params.timeout only bounded execSync. | **delivered differently.** avoid blocks before launch (3); limit.seconds kills the process group (124); limit.output_bytes kills it (137); a non-positive limit is 4. | — | `jos run avoid-substring.jos` → 3<br>`jos run time-limit.jos` → 124<br>`jos run output-limit.jos` → 137<br>`jos run budget-zero.jos` → 4 |
+| Flows and gates | Steps run in sequence or as a DAG; a human gate stops the flow until a person approves it. | 0.0.7 orchestration flows run with execSync, one after another; no gates; `--flow` picked a flow. | **delivered differently.** jos-core flows with needs, gates and data between steps; `--approve <step>`, `--flow <name>`, `--input <json>`. | — | `jos run examples/03-flow-gate.jos` → 1<br>`jos run examples/03-flow-gate.jos --approve build` → 0<br>`jos run examples/03-flow-gate.jos --flow build-only` → 0 |
+| Reuse: use, templates, digests | A document reuses another by id, instantiates templates with slots, and pins what it depends on by digest. | None: `jos get` downloaded files without verifying them. | **delivered differently.** `use` by id and range, templates with typed slots, digest pins; `--library <dir>`, `--with <json>`. | — | `jos run examples/04-use-template/use.jos --library examples/04-use-template/lib` → 0<br>`jos run examples/04-use-template/lib/greeting.jos --with '{"name":"Ana"}'` → 0 |
+| Fractal: a folder is a document | An atom, a flow and a folder with .jos/ have the same shape; a sealed folder runs only while its hash matches. | One file per artifact; no folder documents. | **delivered.** `jos run <folder>` runs its .jos/manifest.jos; a sealed folder is verified by its directory hash first (3 on change). | — | `jos run examples/05-sealed` → 0<br>`node -e "require('fs').writeFileSync('examples/05-sealed/.jos/added.txt', 'x')"` → 0<br>`jos run examples/05-sealed` → 3 |
+| Refuse what it cannot honor | A document that needs something this runtime lacks is refused before anything starts, never half-run. | 0.0.7 had no requires[] and no security.tier: nothing was refused before running. | **delivered.** Unmet requires[] and security.tier sandbox exit 5 before the first step; receipts say isolation none. | — | `jos run examples/06-requires.jos` → 5<br>`jos run examples/07-sandbox.jos` → 5<br>`jos run requires-1.0.0.jos` → 5 |
+| Content identity | Every document has an id computed from its content; jos shows what jos-core decided, the same id on every machine. | A sha256 of the file bytes in a .sig.json sidecar. | **delivered differently.** `jos ids`: art_ (SHA-256 of the RFC 8785 canonical JSON), ent_ of the name, a folder's directory hash; jos and jos-core agree. | — | `jos-core validate examples/01-hello.jos` → 0<br>`jos ids examples/01-hello.jos` → 0<br>`jos ids examples/01-hello.jos examples/05-sealed` → 0<br>`jos ids dup-keys.jos` → 2 |
+| Integrity hash | A sealed document runs only while its content matches its hash. | A sha256 of the file bytes in a sidecar, checked by `run`. | **delivered differently.** integrity.hash (SHA-256 over RFC 8785 canonical JSON) is recomputed before anything starts; a mismatch is 3. | — | `jos run sealed.jos` → 0<br>`jos run integrity-mismatch.jos` → 3 |
+| Receipts, ledger and meter | Every run leaves a hash-chained ledger that can be listed, verified and metered. | ~/.jos/runs/*/events.jsonl: a witness log without hashes. | **delivered differently.** A ledger per run; `jos runs`, `jos ledger verify` (0 or 1), `jos meter` (unreported meters say not reported, never 0). | — | `jos run examples/01-hello.jos` → 0<br>`jos runs` → 0<br>`jos ledger verify {last_run}` → 0<br>`jos meter {last_run}` → 0<br>`jos ledger verify run_00000000000000000000000000` → 2 |
+| Credentials without exposure | A step gets a credential without it being in the document, on a command line or in any output. | `jos secrets set NAME VALUE` (value on the command line), `get` printed it; AES-256-CBC. | **delivered differently.** `set --stdin`, `get` shows a keyed fingerprint, `exec --only NAME --` gives it to one child; AES-256-GCM per entry. | — | `jos secrets set DEMO_KEY VALUE` → 64<br>`jos secrets set DEMO_KEY --stdin` → 0 (with stdin)<br>`jos secrets get DEMO_KEY` → 0<br>`jos secrets exec --only DEMO_KEY -- node -e "process.stdout.write(process.env.DEMO_KEY === 's3cr3t-promise-value' ? 'key-present' : 'key-missing')"` → 0<br>`jos run examples/11-openai.jos` → 1 |
+| A local model as a step | Use a local model (Ollama) from a document, offline. | `jos llm --adapter ollama` sent the artifact to Ollama and overwrote the .jos with the answer. | **delivered differently.** A shell step: 10-ollama.jos checks localhost:11434 and calls `ollama run`; without Ollama it sends nothing (1). | — | `jos run examples/10-ollama.jos` → 1 |
+| A read-only page of runs | See past runs in a browser without exposing files or secrets. | `jos serve` was an HTTP file explorer on every interface; it served ~/.jos/secrets/.master. | **delivered differently.** 14-serve.jos writes an HTML index of ~/.jos/runs to a temporary folder and serves only it on 127.0.0.1. | — | `jos run examples/14-serve.jos --dry-run` → 0 |
+| MCP, read-only | An MCP client can read a project folder and nothing else: no secrets, no writes, no programs unless allowed. | No MCP server. | **delivered.** `jos serve --mcp` over stdio, read-only by default; ~/.jos/secrets denied; --allow-write and --allow-shell are opt-ins. | — | `jos serve --mcp --root {work}` → 0 (with stdin) |
+| Exit codes | A script can tell done, not done, invalid, blocked, over budget, unexecutable and usage errors apart. | 0 and 1 only; --insecure and --verbose existed. | **delivered differently.** 0 done, 1 not done, 2 invalid, 3 blocked, 4 budget, 5 unexecutable, 124 time, 137 output, 64 usage, 70 host error; --insecure and --verbose are 64. | — | `jos run` → 64<br>`jos run minimal-13.jos --insecure` → 64<br>`jos run minimal-13.jos --verbose` → 64<br>`jos run object-step.jos` → 2<br>`jos run examples/01-hello.jos --input '{not json'` → 64 |
+| 4.1.0 Minimal Valid Artifact | The 13-key Minimal Valid Artifact of the 4.1.0 page, copied unchanged, validates and runs. | validate checked the 13 keys; run printed Hello!. | **delivered.** Read as 0.0.7 and normalized in memory to a 2.0 flow: validate 0, run prints Hello! (0). | — | `jos validate minimal-13.jos` → 0<br>`jos run minimal-13.jos` → 0 |
+| Read 0.0.7 | Documents written for 4.1.0 keep working, and validation checks the format, not a fixed list of keys. | 0.0.7 was the only format; validate required 13 keys (a document with 7 of them failed, exit 1). | **delivered differently.** Only jos and meta are required; 0.0.7 with text steps is normalized to a 2.0 flow and runs; object steps and, since jos-core 2.0.0-rc.8, type: prompt steps are invalid (2). | — | `jos validate only-7-keys.jos` → 0<br>`jos run only-7-keys.jos` → 0<br>`jos validate object-step.jos` → 2<br>`jos validate prompt-step-0.0.7.jos` → 2 |
+| 0.0.7 integrity_ref | A 0.0.7 document sealed by a separate manifest (security.integrity_ref) is refused when the manifest does not match. | Checked the file's sha256 against the manifest: Hash mismatch, exit 1. | **delivered.** Verified again by jos-core 2.0.0-rc.8 before anything starts, --dry-run too (jos run hands it the octets it read): a match runs (0), a changed document is blocked (3, integrity_ref: ...); stricter on paths than 4.1.0 (relative, inside the document's folder, no links); jos migrate reseals it as integrity.hash. | — | `jos run sealed-0.0.7/ref.jos` → 0<br>`jos run tampered-0.0.7/ref.jos` → 3<br>`jos run tampered-0.0.7/ref.jos --dry-run` → 3<br>`jos validate sealed-0.0.7/ref.jos` → 0<br>`jos migrate sealed-0.0.7/ref.jos` → 0<br>`jos run sealed-0.0.7/ref.v2.jos` → 0 |
+| jos migrate | A document sealed for 4.1.0 can move to the 2.0 seal without a window where it is unprotected, and a changed one cannot be laundered. | Not applicable (0.0.7 was the only format). | **delivered.** jos migrate verifies the manifest as run does; a mismatch is 3 and nothing is written; otherwise it writes <name>.v2.jos: the 2.0 normalization, integrity_ref removed, security.permissions moved to x-legacy-permissions, integrity.hash of the result; the result validates, runs, and a second migrate says already 2.0. 1.x documents: 64. | — | `jos migrate tampered-0.0.7/ref.jos` → 3<br>`jos migrate sealed-0.0.7/ref.jos` → 0<br>`jos validate sealed-0.0.7/ref.v2.jos` → 0<br>`jos run sealed-0.0.7/ref.v2.jos` → 0<br>`jos migrate sealed-0.0.7/ref.v2.jos` → 0<br>`jos migrate examples/01-hello.jos` → 0<br>`jos migrate shell-1.0.0.jos` → 64 |
+| 0.0.7 written by jos init of 4.1.0 | The document jos init of 4.1.0 wrote (with orchestration.state and its .sig.json) validates and runs. | jos init wrote it with orchestration.state { current_status: idle }; run verified the manifest and printed Hello from <name>. | **delivered.** Valid and runs under jos-core 2.0.0-rc.8: orchestration.state is kept as orchestration.x-legacy-state (never dropped), the manifest named by security.integrity_ref is verified before any step, and jos migrate writes the 2.0 document with integrity.hash. | — | `jos validate init-4.1.0/ref.jos` → 0<br>`jos run init-4.1.0/ref.jos` → 0<br>`jos migrate init-4.1.0/ref.jos` → 0 |
+| Read 1.0.0 and 1.1.0 | Every valid 1.0.0 document and the 1.1.0 short form are read unchanged. | 4.1.0 read 0.0.7 only. | **delivered.** Normalized in memory to 2.0 (the file is not rewritten) and run by jos-core; four 1.0.0 holes below. | — | `jos run shell-1.0.0.jos` → 0<br>`jos run short-1.1.0.jos` → 0 |
+| 1.0.0 execution.flow | A 1.0.0 flow written as execution.flow: [{invoke}] (SPEC §6.8 alias of orchestration.flows.main) runs. | Not applicable (0.0.7 only). | **delivered.** Runs since jos-core 2.0.0-rc.8: each invoke is a definition of the document or a use reference (here resolved from --library); rc.7 refused it (2). | — | `jos validate invoke-1.0.0.jos` → 0<br>`jos run invoke-1.0.0.jos --library lib-1.0.0` → 0 |
+| 1.0.0 execution.budget in a flow | execution.budget (alias of guardrails.limit) stops a flow past max_duration. | Not applicable (0.0.7 only). | **delivered.** Applied in flows too since jos-core 2.0.0-rc.8 (the minimum with guardrails.limit): a 1 s budget stops a 2 s step (124); rc.7 let it finish (0). | — | `jos run budget-1.0.0.jos` → 124 |
+| 1.0.0 gates keyed after-<step> | A gate keyed after-<step>, the form of the 1.0.0 text, is evaluated after that step. | Not applicable (0.0.7 only). | **delivered.** Since jos-core 2.0.0-rc.8 after-<step> is the gate of <step> when no step has that name: a gate after-a that fails stops the flow after a (1); rc.7 refused the run (2). | — | `jos validate gate3-1.0.0.jos` → 0<br>`jos run gate3-1.0.0.jos` → 1 |
+| 1.0.0 seal computed with the hash field empty | A 1.0.0 seal computed as its text says (hash field empty) verifies. | Not applicable (0.0.7 only). | **delivered.** Since jos-core 2.0.0-rc.8 a 1.0.x document without integrity.signature may carry the 1.0.0 seal (only hash empty) or the 2.0 one; it runs (0) and a changed document is still blocked (3). rc.7 blocked the 1.0.0 seal (3). | — | `jos run sealed-ok-1.0.0.jos` → 0<br>`jos run sealed-tampered-1.0.0.jos` → 3 |
+| BCP 47 language tags | Language tags are BCP 47 with a hyphen (en-US, not en_US), as the IANA text says. | Not checked (the 1.0.0 schema even shows en_US). | **delivered differently.** Not enforced by design (decision 2026-10-21): IANA.md says language tags SHOULD be BCP 47 tags with a hyphen; en_US validates. | — | `jos validate lang-underscore.jos` → 0 |
+| LLM engine and judged criteria | A step or a criterion answered by a model, declared in the document. | `jos llm` with the native (josfox.cloud) and ollama adapters; no Gemini, OpenAI or Anthropic code. | **planned.** Valid documents, refused at run with code 5, never faked; providers today only as shell steps (10–13). | 2.1 | `jos validate engine-llm.jos` → 0<br>`jos run engine-llm.jos` → 5<br>`jos run judge.jos` → 5 |
+| Signatures | A document is signed and the signature is verified before it runs. | No signatures; "cryptographically verifiable" meant a sha256 sidecar. | **planned.** Not verified yet: security.tier privileged is refused (5). | 2.1 | `jos run tier-privileged-unsigned.jos` → 5 |
+| Cache, crystals, store | Serve a sealed record of a past run instead of running again, and share pieces through a store. | None. | **planned.** A crystal validates; running one is code 5; no cache and no store. | 2.1 | `jos validate crystal.jos` → 0<br>`jos run crystal.jos` → 5 |
+| jos get | Fetch a document from a registry, verified before it is written. | `jos get` wrote to a path built from meta.name (path traversal) and did not verify the download. | **planned.** Frozen: exit 1 with the reason; nothing is downloaded. | 2.1 | `jos get foo` → 1 |
+| Learning | Adapt from feedback ("adaptive", the orchestrator). | Promised on the page; there was no learning code. | **planned.** None: 0.0.7 adaptive_ai is kept as x-legacy-adaptive_ai and not read. | 2.1 | `jos validate minimal-13.jos --json` → 0 |
+| jos serve as an HTTP explorer | A local dashboard of documents and runs. | `jos serve` explored files on every interface and exposed ~/.jos/secrets from the home folder. | **planned.** Off: exit 2; `jos serve --mcp` works; a runs page is 14-serve.jos. | F3 | `jos serve` → 2 |
+| jos llm, prompts, repo, add | Turn intentions into prompts, improve prompts, manage repositories, edit flows from the command line. | llm and prompts overwrote the .jos with unvalidated model output; repo served get; add edited 0.0.7 flows. | **dropped.** Frozen: each exits 1 and names its README; flows are written in the document. | — | `jos llm hello.jos` → 1<br>`jos prompts` → 1<br>`jos repo` → 1<br>`jos add` → 1 |
+| josctl and @josfox/jos-cli | Companion command lines installed next to jos. | The page told users to install josctl and @josfox/jos-cli. | **dropped.** Separate older packages, not part of 5.0 and not tested here; `jos run --flow <name>`, which josctl always passes, is accepted again. | — | `jos run minimal-13.jos --flow main` → 0 |
+
+Sources: README.md (What it can do, Not yet) and the audit of 2026-10-20 (T1: the 4.1.0 npm page, T3: what 1.0.0 defines, T4: what was told to IANA); each entry of `promises.json` names its row in `source`.