Short answers about the Verified Rehydration Agent pack, each quoting the pack's own documents or pointing to them.
No. In the words of its license: “This package is a normative specification. It is not software, SaaS, a managed service, consulting, support, managed operations, implementation delivery, or a validation service.” The specification defines how a conforming agent must behave; your engineering team builds the agent from it, in any language or paradigm. The only executables in the package are the reproducibility binaries of the NNT (Non-Normative Tests) companion — observational evidence, not normative, and not a reference build.
Because the specification is the product. A reference build in one language would become the thing to copy, and the specification would stop being execution-neutral. The license is explicit: the package “is not a reference implementation, and no reference build is shipped.” The five reconstructions in the NNT companion are study artifacts — evidence that the specification can be built from the pack alone — not implementations to follow. The pack asks you to read them only after your own implementation passes the Conformance Tests.
Python, Rust, Prolog, C and Bash are five different ways of building software: a high-level scripting language, a systems language, a logic language, an imperative language and a shell. Five paradigm-isolated reconstruction contexts built the agent from the pack alone, one in each, and ran its 29 conformance records against each reconstruction: all 29 converged across the five, with zero divergent records — 27 convergent PASS and 2 convergent SKIP. The five contexts were isolated from one another but shared their reconstruction model, prompt authorship and training data, as the companion discloses. This is observational evidence that the specification is derivable and self-sufficient — not a certification, and not a list of supported stacks. A separate supplement records five additional target paradigms: Common Lisp, Brainfuck, spreadsheet formulas, an Analytical Engine-style program and AWK.
Check it first against the pack's own instruments. The license describes the agent as semantically closed: “every term is resolved within the package's Semantic Index and Ambiguity Register” — 96 normative terms in the Semantic Index, 11 lexical-overload resolutions in the Ambiguity Register. The Conformance Tests carry 29 records anchored 1:1 to the specification, and the Verification Runbook in the package (verify.md) has you reproduce the pack's declared values on your own machine: a mismatch is a fact you report, not a judgment you make. If the error stands, write to contact@semantichor.com.
None are promised. The license states that “SEMANTICHOR is not obligated to provide support”, and that the package is provided “as is.” It covers one version — “the package version identified by the manifest_ref” shown on the Verified Rehydration Agent page — and “confers no right to updated, future, or other versions.” A revised specification is published under its own license.
Within its license, yes. The package is distributed free of charge, and the license grants, “Subject to the Restriction section”, among other rights, “the right to deploy and operate those implementations for any lawful purpose, including in the course of a commercial business”. It also reserves uses, in its Restriction section. Read both in full: the license is published on this site, and the Verified Rehydration Agent page sets out what it permits and what it reserves.
The pack. The author constructed the pack's seven canonical files, including the conformance tests, reviewed them manually, and designed and calibrated the NNT harness. Large language models were used openly, as tools to accelerate research and production, with manual review: they assisted the drafting of the pack's documents and, by design, built the five reconstruction baselines in the NNT companion, which are study artifacts, not reference implementations. No tool is an author; the author is accountable for the content. What matters is not which tools touched the documents but whether the pack can be verified: its integrity is anchored by the Manifest and its conformance suite is runnable.
The supplementary derivations. The author designed and calibrated the harnesses of the derivations in this supplement. Large language models were used openly, as tools to accelerate research and production, with manual review: they produced the renderings (Common Lisp, Brainfuck, spreadsheet formulas, an Analytical Engine-style program and AWK) and the comparators (the Rust rendering and the reference output spec_162.txt) in an AI-provider environment, as the study artifacts reported in Section 5 of the article; they are not reference implementations. No tool is an author; the author is accountable for the content. What matters is not which tools touched the files but whether they can be verified: the supplement has its own Manifest, which names the pack Manifest as its parent.