Skip to main content

Vinyasar: Policy-Driven Self-Healing Supervision for Yasarda

Experimental package. Policy-driven, evidence-bound self-healing supervision and mutation engine.

Installation

pip install vinyasar
# with optional YAML profile support:
pip install "vinyasar[yaml]"

Yasarda is a dependency: vinyasar depends on the yasarda package (yasarda>=0.5,<0.6) and no longer embeds a copy. Installing vinyasar installs yasarda, which provides the yasarda and yasarda-mcp commands. There is one engine at one version.

Public Feature Coverage

Vinyasar provides two console scripts, and its yasarda dependency provides two more:

  • vinyasar: The primary self-healing controller CLI.
  • vinyasar-mcp: The MCP server for Vinyasar. --config P serves one pinned profile; --profiles-dir DIR serves every profile file in a host-owned directory from one host, where tools take a profile name chosen from the host-fixed set (list_profiles names them), and approvals stay with the host (--approve).
  • yasarda (from the yasarda package): The Yasarda engine CLI for low-level structural mutation.
  • yasarda-mcp (from the yasarda package): The MCP server for Yasarda.

It also provides two subcommands under vinyasar for configuration hygiene and host verification:

  • vinyasar schema: Outputs the JSON schema for validation of vinyasar.json/vinyasar.yaml profiles.
  • vinyasar doctor: Verifies the health and presence of the required environment and evaluator constraints.

Basic Example

# Generate a profile for an app repository: its test suites become test_run
# checks (each program granted by name), failing checks route to reviewed
# Yasarda remediations by approval only, and no evaluator is configured.
vinyasar init --kind app-repo --repo ~/work/my-app --out ~/profiles/my-app.json \
  --catalog ~/profiles/my-app-remediations --test-command "cargo test --offline"

# Check the profile (and that every named remediation exists in the catalog)
vinyasar doctor ~/profiles/my-app.json

# Run once; exit 3 means approval is required, and the run record names the
# exact plan and its approval ID
vinyasar run --trigger manual --trigger-id round-1 ~/profiles/my-app.json

# Run again with the approval for that one plan
vinyasar run --trigger manual --trigger-id round-1-approved --approve APPROVAL_ID ~/profiles/my-app.json

# The profile and run-record schemas
vinyasar schema profile
vinyasar schema run

Plain vinyasar init (kind repo) generates the conservative operational profile: recovery of interrupted Yasarda operations, nothing else.

vinyasar conformance run checks this installation against the packaged conformance set, byte for byte; src/vinyasar/conformance_set/README.md is the protocol a second implementation follows to be held to the same outputs.

Architecture

Vinyasar acts as an externally scheduled, trigger-driven reconciler. Schedule expressions (such as crons) are owned by external schedulers (e.g., launchd, systemd, or CI pipelines). When invoked, Vinyasar operates as a bounded one-shot process to inspect the target repository, consult the Yasarda engine, execute allowed playbooks, and exit, leaving behind a cryptographic-like ledger of actions taken.

Evaluator Prerequisite

For optional policy braking and advisory evaluations during operation, Vinyasar delegates to the jev evaluator. If these features are utilized, it requires jev >=0.6.2,<0.7.0 to be available on the host PATH.

The jev state ceiling is a word, not a free byte count. Each word is one payload:

  • standard — 64 KiB of issue metadata. This is the default when the word is omitted, and the only payload vinyasar inspect and vinyasar run send. --state-cap on those commands must be standard or omitted, and a profile word other than standard is rejected before a run starts. Passing --state-cap still requires spec.evaluator.
  • inventory — 1 MiB. A path census: relative paths and decimal sizes, not file bodies. vinyasar inventory --repo PATH builds it in process and does not call jev.
  • windows — 4 MiB. One verified UTF-8 slice per path. vinyasar windows --repo PATH --spans FILE checks each span against the file's own bytes. It is not a whole file, and the file read limit stays 8 MiB. It does not call jev.

vinyasar judge inventory and vinyasar judge windows are the only commands that send those payloads to jev. They take the same builder flags, a required --question, and at least one --option KEY=DESCRIPTION. They do not run a playbook and they do not restore a journal. vinyasar doctor prints the profile word and does not accept --state-cap. There is no exponent and no unlimited word.

Metadata

Release files for vinyasar 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vinyasar 0.5.0
File Size Uploaded Provenance Actions
vinyasar-0.5.0.tar.gz 134.0 kB Without provenance Details for vinyasar-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for vinyasar 0.5.0
File Interpreter ABI Platform Actions
vinyasar-0.5.0-py3-none-any.whl Python 3 none any Details for vinyasar-0.5.0-py3-none-any.whl

Total release size: 245.6 kB

Release files / vinyasar-0.5.0.tar.gz

Download URL vinyasar-0.5.0.tar.gz
Size 134.0 kB
Tags Source
SHA-256 checksum
How to use checksums
65bc44334fce647c28bb97243aed4bec5a6997567e85818249182f548771debb
BLAKE2b-256 checksum
How to use checksums
b6c9c7fc8d670d7b3f086ee23ece1d966438aadfbce8c94b77af2ad7d56ab9e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / vinyasar-0.5.0-py3-none-any.whl

Download URL vinyasar-0.5.0-py3-none-any.whl
Size 111.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
19c6cce886480f90759636eef7e8471e7c908597b3aafcd33e0a4fc23ed6b08a
BLAKE2b-256 checksum
How to use checksums
0a1de76b9e67b10ef21c07ecaac1ee05f0c30af7cf914aea050d04645d75bdd9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for vinyasar 0.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page