tvl-spec 1.4.0__tar.gz

tvl_spec-1.4.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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 the 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
+
+   Copyright 2026 Traigent
+
+   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.

tvl_spec-1.4.0/LICENSE-content

@@ -0,0 +1,25 @@
+Creative Commons Attribution 4.0 International
+
+The authored content listed below is licensed under the Creative Commons
+Attribution 4.0 International License (CC-BY-4.0).
+
+Covered paths in this repository:
+
+- `docs/`
+- `formalization/`
+- `tvl_book/website_content/`
+- `website/client/public/docs/`
+- `website/client/src/book/**/*.mdx` (book prose)
+- `website/client/public/book/media/**` (book figures and rendered animations)
+- `website/dist/public/book/tvl-book.pdf` (the built book PDF; not tracked, listed so the licence travels with the file)
+
+You are free to share and adapt this material for any purpose, including
+commercial use, provided that you give appropriate credit, provide a link to
+the license, and indicate whether changes were made.
+
+License URL:
+
+- https://creativecommons.org/licenses/by/4.0/
+
+Unless a file or subdirectory states otherwise, materials outside the covered
+paths above follow the repository's default Apache-2.0 license in `LICENSE`.

tvl_spec-1.4.0/MANIFEST.in

@@ -0,0 +1,5 @@
+include tests/data/domain_encode_before.py.txt
+include tests/data/structural_tokenizer_subclass_before.json
+
+recursive-include spec/grammar *.json *.ebnf
+recursive-include conformance/cases/runtime *.yml

tvl_spec-1.4.0/NOTICE

@@ -0,0 +1,9 @@
+TVL (Tuned Variables Language)
+Copyright 2024-2026 Traigent Ltd.
+
+This product includes software developed at Traigent Ltd.
+(https://www.traigent.ai/).
+
+Licensed under the Apache License, Version 2.0. See LICENSE.
+Authored documentation, formalization notes, and learning content are
+licensed under CC-BY-4.0. See LICENSE-content.

tvl_spec-1.4.0/PKG-INFO

@@ -0,0 +1,207 @@
+Metadata-Version: 2.4
+Name: tvl-spec
+Version: 1.4.0
+Summary: TVL: a typed AI agent requirements and verification specification language
+Author-email: Traigent Team <open-source@traigent.com>
+License: Apache-2.0
+Project-URL: Homepage, https://tvl-lang.org
+Project-URL: Repository, https://github.com/Traigent/tvl
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: LICENSE-content
+License-File: NOTICE
+Requires-Dist: PyYAML>=6.0
+Requires-Dist: jsonschema>=4.19
+Requires-Dist: ortools>=9.8
+Requires-Dist: scipy>=1.11
+Provides-Extra: dev
+Requires-Dist: z3-solver>=4.12; platform_system != "Windows" and extra == "dev"
+Requires-Dist: mkdocs-material[imaging]>=9.2; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: datasets>=3; extra == "dev"
+Requires-Dist: huggingface_hub>=0.31; extra == "dev"
+Dynamic: license-file
+
+# TVL — an AI agent requirements specification language
+
+[![CI](https://github.com/Traigent/tvl/actions/workflows/ci.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/ci.yml)
+[![CodeQL](https://github.com/Traigent/tvl/actions/workflows/codeql.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/codeql.yml)
+[![Lean proofs](https://github.com/Traigent/tvl/actions/workflows/lean-proofs.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/lean-proofs.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Spec: 1.4](https://img.shields.io/badge/spec-1.4-informational.svg)](CHANGELOG.md)
+
+**Tuned Variables Language (TVL)** is a typed, machine-checkable language for specifying what an AI agent must achieve, what parts of its design may vary, and what evidence is required before a candidate may be accepted.
+
+AI agent requirements are often scattered across prompts, configuration files, evaluation scripts, dashboards, and release checklists. That makes it hard to answer basic questions: Which agent designs are allowed? Which properties are required? Which evaluation set and metrics define success? What evidence supports a release or certification claim?
+
+TVL puts those requirements in one reviewable specification. It describes an **agent design space**, rather than prescribing the code or optimization algorithm used to build one agent.
+
+## A 30-second example
+
+Save this as `support-bot.tvl.yml`. It declares two allowed agent choices, one rule relating them, one objective, and the promotion policy:
+
+```yaml
+tvl:
+  module: example.support_bot
+tvl_version: "1.2"
+
+environment:
+  snapshot_id: "2026-01-01T00:00:00Z"
+
+evaluation_set:
+  dataset: "test://support-bot"
+
+tvars:
+  - name: model
+    type: enum[str]
+    domain: ["small", "large"]
+  - name: max_tool_calls
+    type: int
+    domain:
+      range: [0, 5]
+
+constraints:
+  structural:
+    - when: model = 'small'
+      then: max_tool_calls <= 3
+
+objectives:
+  - name: resolution_rate
+    metric_ref: metrics.resolution_rate.v1
+    direction: maximize
+
+promotion_policy:
+  dominance: epsilon_pareto
+  alpha: 0.05
+  min_effect:
+    resolution_rate: 0.01
+```
+
+From a clone of this repository (see [Quick start](#quick-start) to install), check it:
+
+```bash
+tvl-validate support-bot.tvl.yml   # prints: Schema + lint checks passed.
+tvl-lint support-bot.tvl.yml       # prints: Lint checks passed.
+```
+
+## The problem TVL solves
+
+A TVL module connects four things that otherwise drift apart:
+
+1. **Agent design space** — typed variables for allowed models, prompts, tools, retrieval, routing, memory, orchestration, and other agent choices.
+2. **Required properties** — structural rules, operating assumptions, objectives, acceptable ranges, and behavioral constraints.
+3. **Evaluation contract** — the evaluation set and metric identifiers used to produce comparable evidence.
+4. **Acceptance policy** — the evidence and statistical conditions required to accept or promote a candidate.
+
+This gives developers, evaluators, CI systems, and certification workflows a shared contract for AI agent verification.
+
+## What makes TVL different
+
+TVL specifies the set of acceptable agents. It does not specify the construction procedure for a particular agent.
+
+```text
+TVL module
+  ├── allowed agent choices
+  ├── relationships between those choices
+  ├── required measured properties
+  ├── pinned evaluation context
+  └── acceptance and promotion criteria
+          ↓
+    validators, optimizers, evaluators, CI gates, or certifiers
+```
+
+Any compatible tool may search the declared space. The TVL contract stays stable when the optimizer, model provider, agent framework, or implementation changes.
+
+## Verification and certification scope
+
+TVL can be the specification layer for a verifiable certificate. A defensible claim is scoped to:
+
+- a versioned TVL module;
+- a candidate configuration or implementation binding;
+- a pinned evaluation set and environment context;
+- named evaluator and metric definitions;
+- evidence produced by a governed process; and
+- the acceptance checks that actually ran.
+
+Passing a TVL gate means that the candidate met the declared requirements under that pinned contract and evidence. It does not by itself prove universal safety, correctness, or performance outside that scope. See [AI Agent Requirements and Certification](docs/agent-requirements.md).
+
+## TVL 1.3: requirements in production
+
+TVL 1.3 (accepted 2026-10-21) is a conservative extension of TVL 1.2: a module without the new blocks means exactly what it meant before. It adds three optional blocks: `requirements` (what must keep holding once the agent runs, such as "at most 5% of traces take longer than 2 s" or "the agent never calls a forbidden tool"), `monitors` (which evidence checks a requirement, before release or in production, and with what statistics) and `responses` (what should happen when a monitor reports a breach, from a notification to a human-approved suspend). A separate `tvl_pack` document carries organisation floors that modules can only tighten.
+
+TVL states what these declarations mean and what each verdict promises; its tools validate, compose and compile them, and `tvl-ci-gate` decides promotion monitors from fully resolved evaluation-set counts. Evaluating runtime evidence and carrying out responses is outside the language ([RFC 0003 §3.5](formalization/rfc-0003-runtime-requirements-monitors-responses.md)).
+
+- Guide: [Requirements, Monitors and Responses](docs/guides/requirements-monitors-responses.md)
+- Book: [Chapter 6 · Requirements in Production](tvl_book/website_content/book/chapter-06-requirements-in-production.md)
+- Specification: [RFC 0003](formalization/rfc-0003-runtime-requirements-monitors-responses.md) (Accepted) and [formal semantics §12](formalization/tvl-formal-semantics.md)
+- Examples: [`spec/examples/runtime-1.3/`](spec/examples/runtime-1.3/)
+
+## Quick start
+
+Install the Python package and CLI tools from the repository root:
+
+```bash
+git clone https://github.com/Traigent/tvl.git
+cd tvl
+python -m pip install -e ".[dev]"
+```
+
+Validate a shipped AI agent specification:
+
+```bash
+tvl-validate spec/examples/rag-support-bot.tvl.yml
+tvl-check-structural spec/examples/rag-support-bot.tvl.yml
+tvl-check-operational spec/examples/rag-support-bot.tvl.yml
+```
+
+## Language version
+
+The current language version is **TVL 1.4**. TVL 1.1 added calibrated variables (`cvars`), operational `policies`, and the strict `promotion_policy.require_calibration` mode ([RFC 0001](formalization/rfc-0001-knob-bindings-cvars-policies.md)); TVL 1.2 added `composites` ([RFC 0002](formalization/rfc-0002-composite-knobs.md)); TVL 1.3 added runtime requirements, monitors and responses ([RFC 0003](formalization/rfc-0003-runtime-requirements-monitors-responses.md), above); TVL 1.4 added reactive outcome notifications, undecided-run notifications and notification guards ([RFC 0004](formalization/rfc-0004-reactive-outcomes-and-guards.md), accepted 2026-10-21, and [formal semantics §13](formalization/tvl-formal-semantics.md#13-reactive-outcomes-and-notification-guards-tvl-14)). All are conservative extensions: a module that uses none of these constructs (nor TVAR ownership `scope`, also added in 1.1) is also a valid 1.0 module. The user guides focus on the core constructs; every diagnostic the validators emit, including those for the 1.1 and 1.2 constructs, is listed in the [error code catalog](docs/reference/error-codes.md). See the [changelog](CHANGELOG.md) for details.
+
+## Repository map
+
+- `spec/` — normative grammar, schemas, examples, and promotion contracts
+- `docs/` — problem statement, language reference, verification model, and guides
+- `formalization/` — formal semantics, with normative and informative sections identified
+- `python/` and `tvl_tools/` — reference validators, SDK, and CLI tools
+- `tests/` and `conformance/` — executable validation and compatibility cases
+- `vscode-tvl/` and `editor_shared/` — editor support
+- `website/` — source for [tvl-lang.org](https://tvl-lang.org)
+- `proofs/` — Lean mechanization for selected results (pre-RFC-0001/0002 core subset; `cvars`/`policies`/`composites` are not yet formalized, see `proofs/PROOF_SUMMARY.md`'s coverage note; the TVL 1.3 language results and TVL 1.4 guard results are listed in its *Runtime (TVL 1.3)* and *RFC 0004* sections)
+
+## Start here
+
+1. [AI Agent Requirements and Certification](docs/agent-requirements.md)
+2. [Getting Started](docs/getting-started.md)
+3. [Language Reference](docs/reference/language.md)
+4. [Semantics and Verification Reference](docs/reference/verification.md)
+5. [Agent Evaluation and Promotion Evidence](docs/guides/statistical-validation-guide.md)
+6. [Requirements, Monitors and Responses (TVL 1.3)](docs/guides/requirements-monitors-responses.md)
+7. [Complete examples](spec/examples/)
+
+## Specification boundary
+
+TVL standardizes what a conforming module means and what a verifier must check. It does not standardize search algorithms, optimizer architecture, scheduling, sample allocation, or internal solver representation. Those mechanisms may be documented by individual implementations without becoming part of the language contract. Likewise, for TVL 1.3 the language defines what a runtime requirement means and what each verdict promises; how an evaluator decides from runtime evidence and how a platform executes responses are not part of the language contract.
+
+## License
+
+- Code, schemas, validators, CLI tools, editor support, tests, executable examples, and the website application are licensed under Apache-2.0 in [LICENSE](LICENSE), unless a subdirectory provides its own license file.
+- Authored documentation, formalization notes, and learning content are licensed under CC-BY-4.0 as described in [LICENSE-content](LICENSE-content).
+
+## Community
+
+- [Contributing](CONTRIBUTING.md) · [RFC process](formalization/README.md) · [Governance](GOVERNANCE.md) · [Maintainers](MAINTAINERS.md)
+- [Code of Conduct](CODE_OF_CONDUCT.md) · [Security policy](SECURITY.md) · [Support](SUPPORT.md)
+
+## Links
+
+- Website: <https://tvl-lang.org>
+- Documentation: <https://tvl-lang.org/specification>
+- Discussions: <https://github.com/Traigent/tvl/discussions>
+- Issues: <https://github.com/Traigent/tvl/issues>

tvl_spec-1.4.0/README.md

@@ -0,0 +1,177 @@
+# TVL — an AI agent requirements specification language
+
+[![CI](https://github.com/Traigent/tvl/actions/workflows/ci.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/ci.yml)
+[![CodeQL](https://github.com/Traigent/tvl/actions/workflows/codeql.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/codeql.yml)
+[![Lean proofs](https://github.com/Traigent/tvl/actions/workflows/lean-proofs.yml/badge.svg)](https://github.com/Traigent/tvl/actions/workflows/lean-proofs.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+[![Spec: 1.4](https://img.shields.io/badge/spec-1.4-informational.svg)](CHANGELOG.md)
+
+**Tuned Variables Language (TVL)** is a typed, machine-checkable language for specifying what an AI agent must achieve, what parts of its design may vary, and what evidence is required before a candidate may be accepted.
+
+AI agent requirements are often scattered across prompts, configuration files, evaluation scripts, dashboards, and release checklists. That makes it hard to answer basic questions: Which agent designs are allowed? Which properties are required? Which evaluation set and metrics define success? What evidence supports a release or certification claim?
+
+TVL puts those requirements in one reviewable specification. It describes an **agent design space**, rather than prescribing the code or optimization algorithm used to build one agent.
+
+## A 30-second example
+
+Save this as `support-bot.tvl.yml`. It declares two allowed agent choices, one rule relating them, one objective, and the promotion policy:
+
+```yaml
+tvl:
+  module: example.support_bot
+tvl_version: "1.2"
+
+environment:
+  snapshot_id: "2026-01-01T00:00:00Z"
+
+evaluation_set:
+  dataset: "test://support-bot"
+
+tvars:
+  - name: model
+    type: enum[str]
+    domain: ["small", "large"]
+  - name: max_tool_calls
+    type: int
+    domain:
+      range: [0, 5]
+
+constraints:
+  structural:
+    - when: model = 'small'
+      then: max_tool_calls <= 3
+
+objectives:
+  - name: resolution_rate
+    metric_ref: metrics.resolution_rate.v1
+    direction: maximize
+
+promotion_policy:
+  dominance: epsilon_pareto
+  alpha: 0.05
+  min_effect:
+    resolution_rate: 0.01
+```
+
+From a clone of this repository (see [Quick start](#quick-start) to install), check it:
+
+```bash
+tvl-validate support-bot.tvl.yml   # prints: Schema + lint checks passed.
+tvl-lint support-bot.tvl.yml       # prints: Lint checks passed.
+```
+
+## The problem TVL solves
+
+A TVL module connects four things that otherwise drift apart:
+
+1. **Agent design space** — typed variables for allowed models, prompts, tools, retrieval, routing, memory, orchestration, and other agent choices.
+2. **Required properties** — structural rules, operating assumptions, objectives, acceptable ranges, and behavioral constraints.
+3. **Evaluation contract** — the evaluation set and metric identifiers used to produce comparable evidence.
+4. **Acceptance policy** — the evidence and statistical conditions required to accept or promote a candidate.
+
+This gives developers, evaluators, CI systems, and certification workflows a shared contract for AI agent verification.
+
+## What makes TVL different
+
+TVL specifies the set of acceptable agents. It does not specify the construction procedure for a particular agent.
+
+```text
+TVL module
+  ├── allowed agent choices
+  ├── relationships between those choices
+  ├── required measured properties
+  ├── pinned evaluation context
+  └── acceptance and promotion criteria
+          ↓
+    validators, optimizers, evaluators, CI gates, or certifiers
+```
+
+Any compatible tool may search the declared space. The TVL contract stays stable when the optimizer, model provider, agent framework, or implementation changes.
+
+## Verification and certification scope
+
+TVL can be the specification layer for a verifiable certificate. A defensible claim is scoped to:
+
+- a versioned TVL module;
+- a candidate configuration or implementation binding;
+- a pinned evaluation set and environment context;
+- named evaluator and metric definitions;
+- evidence produced by a governed process; and
+- the acceptance checks that actually ran.
+
+Passing a TVL gate means that the candidate met the declared requirements under that pinned contract and evidence. It does not by itself prove universal safety, correctness, or performance outside that scope. See [AI Agent Requirements and Certification](docs/agent-requirements.md).
+
+## TVL 1.3: requirements in production
+
+TVL 1.3 (accepted 2026-10-21) is a conservative extension of TVL 1.2: a module without the new blocks means exactly what it meant before. It adds three optional blocks: `requirements` (what must keep holding once the agent runs, such as "at most 5% of traces take longer than 2 s" or "the agent never calls a forbidden tool"), `monitors` (which evidence checks a requirement, before release or in production, and with what statistics) and `responses` (what should happen when a monitor reports a breach, from a notification to a human-approved suspend). A separate `tvl_pack` document carries organisation floors that modules can only tighten.
+
+TVL states what these declarations mean and what each verdict promises; its tools validate, compose and compile them, and `tvl-ci-gate` decides promotion monitors from fully resolved evaluation-set counts. Evaluating runtime evidence and carrying out responses is outside the language ([RFC 0003 §3.5](formalization/rfc-0003-runtime-requirements-monitors-responses.md)).
+
+- Guide: [Requirements, Monitors and Responses](docs/guides/requirements-monitors-responses.md)
+- Book: [Chapter 6 · Requirements in Production](tvl_book/website_content/book/chapter-06-requirements-in-production.md)
+- Specification: [RFC 0003](formalization/rfc-0003-runtime-requirements-monitors-responses.md) (Accepted) and [formal semantics §12](formalization/tvl-formal-semantics.md)
+- Examples: [`spec/examples/runtime-1.3/`](spec/examples/runtime-1.3/)
+
+## Quick start
+
+Install the Python package and CLI tools from the repository root:
+
+```bash
+git clone https://github.com/Traigent/tvl.git
+cd tvl
+python -m pip install -e ".[dev]"
+```
+
+Validate a shipped AI agent specification:
+
+```bash
+tvl-validate spec/examples/rag-support-bot.tvl.yml
+tvl-check-structural spec/examples/rag-support-bot.tvl.yml
+tvl-check-operational spec/examples/rag-support-bot.tvl.yml
+```
+
+## Language version
+
+The current language version is **TVL 1.4**. TVL 1.1 added calibrated variables (`cvars`), operational `policies`, and the strict `promotion_policy.require_calibration` mode ([RFC 0001](formalization/rfc-0001-knob-bindings-cvars-policies.md)); TVL 1.2 added `composites` ([RFC 0002](formalization/rfc-0002-composite-knobs.md)); TVL 1.3 added runtime requirements, monitors and responses ([RFC 0003](formalization/rfc-0003-runtime-requirements-monitors-responses.md), above); TVL 1.4 added reactive outcome notifications, undecided-run notifications and notification guards ([RFC 0004](formalization/rfc-0004-reactive-outcomes-and-guards.md), accepted 2026-10-21, and [formal semantics §13](formalization/tvl-formal-semantics.md#13-reactive-outcomes-and-notification-guards-tvl-14)). All are conservative extensions: a module that uses none of these constructs (nor TVAR ownership `scope`, also added in 1.1) is also a valid 1.0 module. The user guides focus on the core constructs; every diagnostic the validators emit, including those for the 1.1 and 1.2 constructs, is listed in the [error code catalog](docs/reference/error-codes.md). See the [changelog](CHANGELOG.md) for details.
+
+## Repository map
+
+- `spec/` — normative grammar, schemas, examples, and promotion contracts
+- `docs/` — problem statement, language reference, verification model, and guides
+- `formalization/` — formal semantics, with normative and informative sections identified
+- `python/` and `tvl_tools/` — reference validators, SDK, and CLI tools
+- `tests/` and `conformance/` — executable validation and compatibility cases
+- `vscode-tvl/` and `editor_shared/` — editor support
+- `website/` — source for [tvl-lang.org](https://tvl-lang.org)
+- `proofs/` — Lean mechanization for selected results (pre-RFC-0001/0002 core subset; `cvars`/`policies`/`composites` are not yet formalized, see `proofs/PROOF_SUMMARY.md`'s coverage note; the TVL 1.3 language results and TVL 1.4 guard results are listed in its *Runtime (TVL 1.3)* and *RFC 0004* sections)
+
+## Start here
+
+1. [AI Agent Requirements and Certification](docs/agent-requirements.md)
+2. [Getting Started](docs/getting-started.md)
+3. [Language Reference](docs/reference/language.md)
+4. [Semantics and Verification Reference](docs/reference/verification.md)
+5. [Agent Evaluation and Promotion Evidence](docs/guides/statistical-validation-guide.md)
+6. [Requirements, Monitors and Responses (TVL 1.3)](docs/guides/requirements-monitors-responses.md)
+7. [Complete examples](spec/examples/)
+
+## Specification boundary
+
+TVL standardizes what a conforming module means and what a verifier must check. It does not standardize search algorithms, optimizer architecture, scheduling, sample allocation, or internal solver representation. Those mechanisms may be documented by individual implementations without becoming part of the language contract. Likewise, for TVL 1.3 the language defines what a runtime requirement means and what each verdict promises; how an evaluator decides from runtime evidence and how a platform executes responses are not part of the language contract.
+
+## License
+
+- Code, schemas, validators, CLI tools, editor support, tests, executable examples, and the website application are licensed under Apache-2.0 in [LICENSE](LICENSE), unless a subdirectory provides its own license file.
+- Authored documentation, formalization notes, and learning content are licensed under CC-BY-4.0 as described in [LICENSE-content](LICENSE-content).
+
+## Community
+
+- [Contributing](CONTRIBUTING.md) · [RFC process](formalization/README.md) · [Governance](GOVERNANCE.md) · [Maintainers](MAINTAINERS.md)
+- [Code of Conduct](CODE_OF_CONDUCT.md) · [Security policy](SECURITY.md) · [Support](SUPPORT.md)
+
+## Links
+
+- Website: <https://tvl-lang.org>
+- Documentation: <https://tvl-lang.org/specification>
+- Discussions: <https://github.com/Traigent/tvl/discussions>
+- Issues: <https://github.com/Traigent/tvl/issues>

tvl_spec-1.4.0/conformance/cases/runtime/compatibility/check-operational-refuses-pack.yml

@@ -0,0 +1,20 @@
+case_format: tvl-runtime-case/1
+family: compatibility
+description: check operational refuses pack
+spec_refs:
+- formalization/rfc-0003-runtime-requirements-monitors-responses.md#5.1
+- formalization/rfc-0003-runtime-requirements-monitors-responses.md#11.2
+input:
+  kind: toolchain
+  entrypoint: tvl-check-operational
+  reader: v1_3
+expected:
+  error: unsupported_construct
+  construct: tvl_pack
+  exit_code: 2
+pack:
+  tvl_version: '1.3'
+  pack:
+    module: test_pack
+  requirements: []
+  monitors: []

tvl_spec-1.4.0/conformance/cases/runtime/compatibility/check-structural-refuses-pack.yml

@@ -0,0 +1,20 @@
+case_format: tvl-runtime-case/1
+family: compatibility
+description: check structural refuses pack
+spec_refs:
+- formalization/rfc-0003-runtime-requirements-monitors-responses.md#5.1
+- formalization/rfc-0003-runtime-requirements-monitors-responses.md#11.2
+input:
+  kind: toolchain
+  entrypoint: tvl-check-structural
+  reader: v1_3
+expected:
+  error: unsupported_construct
+  construct: tvl_pack
+  exit_code: 2
+pack:
+  tvl_version: '1.3'
+  pack:
+    module: test_pack
+  requirements: []
+  monitors: []