Vinyasar 0.1.0
Evidence-bound self-healing supervision for Yasarda.
Vinyasar is the optional automation layer formerly described as “Yasarda Steward.” It inspects a target, assigns stable issue codes, evaluates a pinned user policy, invokes only reviewed capability-scoped playbooks, performs a fresh verification, and writes an append-only canonical JSON run record plus optional Markdown.
The first release deliberately has one mutating capability:
yasarda.recover. It can restore an interrupted journaled Yasarda transaction
through Yasarda's public recovery API. It cannot run commands, author or execute
arbitrary code, install generated playbooks, overwrite divergent content, or
relax Yasarda's filesystem guards.
Trust model
AI reasoning belongs outside the mutation boundary. A model or agent may propose a diagnosis, profile revision, explanation, or future playbook. Vinyasar grants authority only when deterministic evidence, the exact pinned profile, a built-in reviewed playbook, a named target capability, attempt limits, cooldown, and fresh post-action verification all agree.
trigger -> inspect -> issue -> policy decision -> bounded playbook -> verify
|
v
canonical JSON + Markdown + CloudEvents
Authority is monotonic: adapters may remove authority but cannot add it. Unknown
issues use default_effect, which can only be observe or escalate.
Install
Install the supplied Yasarda 0.3.0 wheel first, then Vinyasar:
python -m pip install ./yasarda-0.3.0-py3-none-any.whl
python -m pip install ./vinyasar-0.1.0-py3-none-any.whl
JSON profiles require no dependency beyond the base install. YAML profiles are
optional and require vinyasar[yaml]; JSON remains the canonical portable form.
Generate and inspect a profile
Profile generation performs read-only setup inspection. It never overwrites its output file. On a supported POSIX local filesystem it pre-authorizes guarded recovery of interrupted operations. On iCloud Drive, other detected cloud storage, remote/FUSE storage, or non-POSIX hosts it generates an escalation-only rule instead. The target repository, Yasarda journal, and Vinyasar attempt ledger must all pass that check.
vinyasar init \
--repo /path/to/repository \
--out /path/to/vinyasar-profile.json \
--schedule "every 30 minutes"
vinyasar validate /path/to/vinyasar-profile.json
vinyasar inspect /path/to/vinyasar-profile.json --trigger manual
validate prints the exact authority represented by the profile. inspect runs
the full reconciliation path in dry-run mode and still emits configured reports.
Run
vinyasar run /path/to/vinyasar-profile.json \
--trigger on_startup \
--trigger-id launch-2026-09-09T18:00:00Z
Schedulers remain external. launchd, systemd, CI, or an agent invokes the
one-shot command and supplies a stable trigger ID. Reusing the same trigger ID
with the same profile and mode returns the existing append-only report and does
not repeat a repair.
An approval policy produces an exact approval_id in its decision. A later run
can supply it with --approve ID. Changing the issue evidence, playbook,
capability, or profile revision changes that ID.
For MCP clients, start a fixed-profile stdio server:
vinyasar-mcp --config /path/to/vinyasar-profile.json
The MCP tools can inspect, reconcile, and retrieve a report. They contain no
arguments for changing target paths, policy, playbooks, capabilities, or
approvals. If an approval rule is used, independently reviewed approval IDs
must be supplied as host startup arguments. The adapter is synchronous and does
not claim experimental MCP Tasks support.
Exit status is 0 for healthy, repaired, or dry_run; 3 for
approval_required; 2 for unresolved or failed runs; and 130 for interruption.
Profile policy
The packaged schemas are available through vinyasar schema profile and
vinyasar schema run. Unknown fields,
duplicate JSON keys, overlapping issue rules, write directories inside the target
repository, actionable rules without exact capabilities/playbooks, and authority
attached to observe/escalate rules are rejected.
The Yasarda state directory is mandatory and revision-pinned in every normalized profile. Profile generation resolves Yasarda's configured or default state path so a later environment-variable change cannot silently select different journals.
Built-in issue codes:
INTERRUPTED_OPERATION: a public Yasarda operation status requires recovery.DIRTY_WORKTREE: Git reports uncommitted changes; observed by default.UNSUPPORTED_STORAGE: Yasarda refuses mutation on the detected filesystem.INSPECTION_FAILED: status could not be established; always escalated by the generated profile.
The generated profile enables manual, startup, and failed-execution triggers. A recorded scheduled expression is metadata for the external scheduler; Vinyasar does not reinterpret or execute natural-language schedules.
Reports and events
Every completed run writes vinyasar-RUN_ID.json with mode 0600. Markdown is
derived from that JSON. Existing report paths are never overwritten. Each record
contains CloudEvents 1.0-compatible issue, policy-decision, action, and run
envelopes suitable for future MCP Task or A2A adapters.
No repository source contents are collected by Vinyasar. Yasarda receipts omit the source bytes retained privately in recovery journals. Report retention is recorded in configuration but deletion is not automated in this release.
Limits
- Vinyasar is a supervisor, not an OS sandbox or a semantic repair oracle.
- Only the built-in recovery playbook is executable in 0.1.0.
- Attempt reservations are persisted before mutation; crashes consume an attempt.
- Maximum attempts apply to unchanged evidence. Changed evidence produces a new issue identity and requires a fresh policy decision.
- MCP Tasks and A2A are adapter targets, not Vinyasar's source of truth.
- Cryptographic attestation, OPA/Wasm policy backends, SARIF, and OpenTelemetry exporters are intentionally outside this minimal trusted core.
Metadata
Release files for vinyasar 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vinyasar-0.4.0.tar.gz | 80.0 kB | Without provenance | Details for vinyasar-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vinyasar-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for vinyasar-0.4.0-py3-none-any.whl |
Total release size: 146.2 kB
Release files / vinyasar-0.4.0.tar.gz
| Download URL | vinyasar-0.4.0.tar.gz |
|---|---|
| Size | 80.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c084344cf3a0b56f914b1e5bfca9157dfa499733801191da383855a84fb52a0
|
|
BLAKE2b-256 checksum How to use checksums |
3ccae6f20a500ebf69ee4852f162737da04dbbe96d26218b0d4e0806fe92e995
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Release files / vinyasar-0.4.0-py3-none-any.whl
| Download URL | vinyasar-0.4.0-py3-none-any.whl |
|---|---|
| Size | 66.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a60732ca8a2eaba1c13e5b930c94cf9fe1a85bf72b379e90056be64850b0f1d
|
|
BLAKE2b-256 checksum How to use checksums |
3350a92279fd1b6f9462ba1b802744fa41edbb37a6940cd92c768b1efca375c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Security for vinyasar 0.4.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.