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]"

Note on Package Overlap: vinyasar 0.4.2 embeds a bundled yasarda namespace reporting version 0.4.0. Users do not need to install both packages.

Public Feature Coverage

Vinyasar provides four primary console scripts:

  • vinyasar: The primary self-healing controller CLI.
  • vinyasar-mcp: The MCP server for Vinyasar.
  • yasarda: The embedded Yasarda engine CLI for low-level structural mutation.
  • yasarda-mcp: 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

# Validate your profile against the schema
vinyasar schema > profile.schema.json

# Check environment constraints
vinyasar doctor

# Run self-healing supervision in a target repository
vinyasar run /path/to/repo --profile vinyasar.json

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.4.2

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.4.2
File Size Uploaded Provenance Actions
vinyasar-0.4.2.tar.gz 109.2 kB Without provenance Details for vinyasar-0.4.2.tar.gz

Built distribution (wheel)

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

Total release size: 198.0 kB

Release files / vinyasar-0.4.2.tar.gz

Download URL vinyasar-0.4.2.tar.gz
Size 109.2 kB
Tags Source
SHA-256 checksum
How to use checksums
87f1ceb465de483fa0b06722ce0e7e7febdb3eb2a065fa72fda0b467922208c9
BLAKE2b-256 checksum
How to use checksums
148c2e2adb201cb4ebd44896fa190aadeb82585e1aabf0a44227cf6a065e39f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

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

Download URL vinyasar-0.4.2-py3-none-any.whl
Size 88.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
94fcb08c6f8dd6f361a7ae986dc633bbb2d7210094a618ea47215ccf82a4cbc8
BLAKE2b-256 checksum
How to use checksums
5554d6d3bdb8ee5c513e7d6a11769c0b8f59a21b4406110c71aed5b7f72ef515
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Security for vinyasar 0.4.2

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