Metadata-Version: 2.4
Name: vyuha
Version: 0.1.0
Summary: Git-native agentic delivery engine — queue, parallel agents, quality gates, staged deployment
Project-URL: Homepage, https://github.com/sudheerdvn/vyuha
Project-URL: Repository, https://github.com/sudheerdvn/vyuha
Project-URL: Bug Tracker, https://github.com/sudheerdvn/vyuha/issues
Author-email: Sudheer Donaboina <54123367+sudheerdvn@users.noreply.github.com>
License: 
                                         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 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
        
           APPENDIX: How to apply the Apache License to your work.
        
              To apply the Apache License to your work, attach the following
              boilerplate notice, with the fields enclosed by brackets "[]"
              replaced with your own identifying information. (Don't include
              the brackets!)  The text should be enclosed in the appropriate
              comment syntax for the file format. We also recommend that a
              file or class name and description of purpose be included on the
              same "printed page" as the copyright notice for easier
              identification within third-party archives.
        
           Copyright 2026 Sudheer Donaboina (github.com/sudheerdvn)
        
           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.
License-File: LICENSE
License-File: NOTICE
Keywords: agent,agentic,cli,devops,git,local-ai,mcp,ollama,orchestration,tickets,workflow
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
Classifier: Topic :: Utilities
Requires-Python: >=3.11
Requires-Dist: mcp>=1.0.0
Requires-Dist: portalocker>=2.0
Requires-Dist: pyyaml>=6.0
Requires-Dist: rich>=13.0
Provides-Extra: dev
Requires-Dist: pytest-mock>=3.12; extra == 'dev'
Requires-Dist: pytest>=8.0; extra == 'dev'
Provides-Extra: security
Requires-Dist: bandit; extra == 'security'
Requires-Dist: pip-audit; extra == 'security'
Requires-Dist: semgrep; extra == 'security'
Provides-Extra: treesitter
Requires-Dist: tree-sitter-c>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-cpp>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-go>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-java>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-javascript>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-python>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-ruby>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-rust>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter-typescript>=0.21; extra == 'treesitter'
Requires-Dist: tree-sitter>=0.21; extra == 'treesitter'
Description-Content-Type: text/markdown

# Vyuha

[![PyPI](https://img.shields.io/pypi/v/vyuha)](https://pypi.org/project/vyuha/)
[![CI](https://github.com/sudheerdvn/vyuha/actions/workflows/ci.yml/badge.svg)](https://github.com/sudheerdvn/vyuha/actions/workflows/ci.yml)
[![Python 3.11+](https://img.shields.io/badge/python-3.11+-blue.svg)](https://www.python.org/downloads/)
[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
[![Local Ollama](https://img.shields.io/badge/local-Ollama-4b5563)](https://ollama.com/)
[![MCP](https://img.shields.io/badge/MCP-ready-7c3aed)](https://modelcontextprotocol.io/)

Git-native workflow for coding agents: ticket queue, parallel worktrees, review gates, staged deployment.

Vyuha gives AI agents (Claude, Codex, Ollama, aider, etc.) a structured way to work on your codebase in parallel without stomping on each other. Tickets live as local Markdown files by default, agents claim them, worktrees keep them isolated, and a file-based lock prevents merge conflicts. No SaaS, no subscriptions, no external state — everything is in your repo.

> **Experimental preview.** Vyuha is a local workflow layer for coding agents, not a production orchestration platform. It is under active development. V1 provides git-level isolation and diff inspection; it does not sandbox agents at the OS level. See [Security Status](#security-status) and [Known Limitations](#known-limitations) before running it on repositories you care about.

---

## Demo

![Vyuha demo: create tickets, inspect the board, and run orchestrate](docs/assets/demo.gif)

---

## Why vyuha?

| | vyuha | GitHub Issues | Linear | Jira |
|---|---|---|---|---|
| State lives in repo-local files | ✅ | ❌ (GitHub's servers) | ❌ (cloud) | ❌ (cloud) |
| Coordinates parallel agent worktrees | ✅ | ❌ | ❌ | ❌ |
| Works fully offline with local executors | ✅ | ❌ | ❌ | ❌ |
| No account / no SaaS dependency | ✅ | ❌ | ❌ | ❌ |

Traditional trackers store the work. Vyuha also decides *which agent works on what*, keeps parallel work from colliding, and gates deploys — ticket files are how that state stays in your repo.

MCP is built in — run `vyuha mcp` to expose the full command set as native tools for any MCP-compatible agent (Claude, Cursor, etc.), no shell commands required.

---

## Concepts in 30 seconds

```
.vyuha/tickets/TICK-007.md   ← source of truth (YAML frontmatter)
        │
        ▼
vyuha next         ← agent asks: what should I work on?
vyuha start TICK-007  ← agent claims it; worktree + branch created
  ... agent works in .vyuha/worktrees/tick-007/ ...
vyuha complete TICK-007
vyuha review TICK-007
vyuha merge TICK-007   ← branch → main, worktree removed
vyuha promote production  ← staged deploy with guard/pre/post hooks
```

Three axes, never mixed:

| Axis | Commands |
|---|---|
| **Analysis** — turn intent into scoped tickets | `create`, `analyze` |
| **Execution** — who works on what without colliding | `board`, `next`, `start`, `complete`, `review`, `merge` |
| **Delivery** — how merged code reaches environments | `promote`, `pipeline-status`, `flag` |

---

## Security Status

Vyuha is an experimental local-first project manager for coding agents. Before running it autonomously on a repository, read this section.

**What Vyuha does to limit agent scope:**
- Runs each agent in a dedicated git worktree, one per ticket
- Enforces a `touches` list: files committed outside the declared scope route to `needs_review`
- Hard-blocks writes to CI/CD configs, credential files, and Vyuha's own source
- Scans ticket text for prompt injection signals before dispatch
- Optionally runs gitleaks, semgrep/bandit, pip-audit, and npm-audit on agent-produced diffs

**What Vyuha does NOT do:**
- MCP is not a sandbox. `vyuha mcp` exposes ticket lifecycle commands as native tools; an agent with access to those tools can claim tickets, create branches, and trigger merges. The MCP server authenticates nothing beyond what the MCP client config enforces.
- Host executors inherit host permissions. Agents (Claude Code, aider, Codex) run as the invoking OS user with full filesystem and network access. There is no bwrap, seccomp, or container wrapping.
- The file-based lock is single-machine, single-checkout. Two separate clones on two machines can both claim the same ticket.

**Recommendation:** use `--human-review final` when running `vyuha orchestrate` on any repository with production code. This stops after implementation and requires `vyuha merge <id>` to be run manually after you inspect the diff.

For the full threat model, executor permission matrix, and safe usage recommendations, see [SECURITY.md](SECURITY.md) and [docs/security-model.md](docs/security-model.md).

---

## Known Limitations

- **Lock scope is single-machine, single-checkout.** The file-based concurrency lock at `.vyuha/orchestrator.lock` prevents two `vyuha orchestrate` runs on the same checkout from racing, but does not coordinate across separate clones or machines.
- **No OS-level sandbox in V1.** Agents run as child processes with full user permissions. Vyuha inspects the git diff after the agent exits; it cannot observe what the agent read or sent over the network during execution.
- **Executor permissions come from the executor runtime, not from Vyuha.** When you configure `flags: ["--dangerously-skip-permissions"]` for Claude Code, that flag disables Claude Code's own per-action approval prompts so the agent can run headless. Vyuha passes the flag; the trade-off is intentional for unattended runs but means the agent acts without interactive confirmation.

---

## Platform support

| Platform | Status |
|---|---|
| Linux | Supported — primary development platform |
| macOS | Supported — CI-verified on every push |
| Windows | Core functionality works; projects using `.sh` executor scripts require WSL |

---

## Install

```bash
pip install vyuha
vyuha init    # scaffold .vyuha/ + .vyuha.yml in your repo
```

To run from source:

```bash
git clone https://github.com/sudheerdvn/vyuha
cd vyuha
pip install -e ".[dev]"
```

---

## Quick start

```bash
# 1. Create a ticket file
cat > .vyuha/tickets/TICK-001.md << 'EOF'
---
id: TICK-001
title: Add rate limiting to the upload endpoint
status: open
priority: 1
touches:
  - src/upload.py
  - src/middleware.py
parallel_safe: true
autonomy: supervised
close_criteria: POST /upload returns 429 after 100 requests/min per user
---

## Background
A single client can saturate the worker pool with rapid uploads.
EOF

# 2. See the board
vyuha board

# 3. Agent claims and works
vyuha start TICK-001
# ... implement in .vyuha/worktrees/tick-001/ ...
vyuha complete TICK-001
vyuha review TICK-001
vyuha merge TICK-001

# 4. Deploy
vyuha promote production
```

---

## Commands

### Board & planning

```bash
vyuha board                    # ticket board + pipeline snapshot
vyuha next                     # recommend next ticket(s) + safe parallel batch
vyuha pipeline-status          # commits pending at each environment stage

# Machine-readable output (any board/next/pipeline-status/flag list command):
vyuha --json board
vyuha --json next
vyuha --json pipeline-status
vyuha --json flag list
```

### Ticket lifecycle

```bash
# Draft → open
vyuha analyze TICK-007         # fill touches + close_criteria, then open the ticket
vyuha open TICK-007            # flip draft → open without re-running analysis (requires touches already set)

# Execution
vyuha start TICK-007           # claim; creates branch + worktree
vyuha complete TICK-007        # code done → code_complete
vyuha review TICK-007          # submit for review → in_review
vyuha merge TICK-007           # merge to main, delete worktree → merged
vyuha validate TICK-007        # optional post-merge validation → validated
vyuha done TICK-007            # close ticket → done
```

### Deployment

```bash
vyuha promote staging          # guard → pre-promote → sync → post-promote
vyuha promote production
vyuha pipeline-status          # see what's pending where
```

### Feature flags

```bash
vyuha flag list                        # show all flags (global)
vyuha flag list --env staging          # show flags for 'staging' environment
vyuha flag enable  new_checkout_flow --env staging
vyuha flag disable new_checkout_flow --env production
```

### MCP server

```bash
vyuha mcp    # start stdio MCP server; attach any MCP-compatible client
```

Exposed tools: `board`, `next_ticket`, `pipeline_status`, `flag_list`, `flag_set`,
`start`, `complete`, `review`, `merge`.

### Utilities

```bash
vyuha init             # scaffold .vyuha/ + .vyuha.yml
vyuha install-commands # copy Claude slash commands into .claude/commands/
vyuha gh-sync          # mirror tickets to GitHub Issues (manual visibility sync; read-only view, not bidirectional)
vyuha gh-sync --dry-run  # preview what would be created or updated
```

---

## Configuration

`.vyuha.yml` in your repo root (walk-up discovery — run from any subdirectory):

### Executors

vyuha dispatches tickets to whichever executor you configure. Each executor CLI has its own flag for non-interactive operation — pass those flags via `executors.<name>.flags` so the orchestrator can run without waiting for prompts:

```yaml
executor: claude   # default executor for orchestrate

executors:
  claude:
    flags: ["--dangerously-skip-permissions"]  # required for headless; disables Claude Code's per-action prompts — see Known Limitations
  aider:
    flags: ["--yes-always"]                    # auto-confirm all prompts; skip editor
  codex:
    flags: ["--approval-policy=never"]         # no per-action approval prompt
  ollama:
    models:
      implement: llama3.1
      review: qwen2.5-coder

```

Per-executor `bin` overrides the binary name for a supported executor; `flags` are prepended before the prompt.

For human review, set `reviewer: human`. `vyuha orchestrate` will stop after implementation is complete and wait for `vyuha review <ticket> --verdict approved` or a changes-requested verdict before merge.

For fully local/offline runs, set `executor: ollama` and choose local models:

```yaml
executor: ollama
models:
  analyze: llama3.1
  implement: qwen2.5-coder
  review: qwen2.5-coder
```

Vyuha will invoke `ollama run <model> <prompt>`; install and pull those models with Ollama first.

```yaml
ticket_prefix: TICK
tickets_dir: .vyuha/tickets
worktrees_dir: .vyuha/worktrees
executor: claude

core_files:
  - src/core/auth.py
core_patterns:
  - "src/db/**"

lock_statuses: [in_progress, code_complete, in_review]

flag_file: ~/.vyuha/feature_flags.json

environments:
  - name: staging
    branch: staging
    from: main
    trigger: auto        # driven by git post-commit hook; vyuha reports status
    flag_file: ~/.vyuha/staging.feature_flags.json

  - name: production
    branch: production
    from: main
    trigger: manual      # Vyuha promote production runs the full sequence
    guard_script: scripts/check-deploy-window.sh
    pre_promote:
      - scripts/run-integration-tests.sh
    post_promote:
      - scripts/restart-service.sh
    flag_file: ~/.vyuha/feature_flags.json
```

---

## Concurrency model

**Scope: single git checkout, single machine.**

The `touches` list in each ticket is the lock. vyuha holds the lock from
`in_progress` through `in_review` — releasing only at `merged`. This prevents
merge conflicts when multiple agents work in parallel.

```
Agent A: TICK-003  touches: [src/auth.py]    status: in_progress  → LOCKED
Agent B: TICK-007  touches: [src/billing.py] status: in_progress  → LOCKED
Agent C: TICK-009  touches: [src/auth.py]    status: open         → BLOCKED (overlaps A)
```

**What this does NOT prevent:** two separate git clones on two machines claiming the same ticket. `check_local_not_behind_remote` runs on every `start` to reduce this window, but it does not close it entirely — this is a V1 limitation covered in [Known Limitations](#known-limitations).

Five concurrency bugs fixed versus the original orchestrator:

| Bug | Fix |
|---|---|
| Lock released at `code_complete` | Lock held until `merged` |
| TOCTOU on `start` | Re-read ticket from disk immediately before write |
| Merge worktree leaked | Capture worktree path before nulling the field |
| Case mismatch on macOS | Worktree dirs always lowercased |
| Substring dedup in gh-sync | Exact `[TICK-N]` prefix match |

---

## Testing

```bash
venv/bin/pytest tests/ -q
```

880+ tests across 21 modules. All concurrency and security fixes have dedicated test coverage.

---

## MCP integration

Add to your MCP client config:

```json
{
  "mcpServers": {
    "vyuha": {
      "command": "vyuha",
      "args": ["mcp"]
    }
  }
}
```

The server starts on stdio. An AI agent can then call `board()`, `next_ticket()`,
`start("TICK-007")`, etc. as native tools — no shell commands required.

---

## Roadmap

Planned work:

- Per-task executor selection
- Stronger sandboxing for agent runs
- Executor conformance tests
- Distributed ticket coordination

See [ROADMAP.md](ROADMAP.md) for details.

---

## Docs

- `docs/demo-walkthrough.md` — end-to-end walkthrough: idea → analyze → parallel worktrees → review → merge, using a toy calculator project; includes a dry-run path for users without an executor configured
- `docs/troubleshooting.md` — FAQ and debug steps: executor hangs, stuck tickets, worktree cleanup, lock files, MCP setup, and more
- `SECURITY.md` — security policy, reporting vulnerabilities, and what Vyuha does and does not do
- `docs/security-model.md` — full threat model, trust boundaries, executor permission matrix, MCP trust model, V1 limitations, and safe usage recommendations
- `docs/ARCHITECTURE.md` — built architecture, module map, and design invariants
- `docs/config-reference.md` — supported `.vyuha.yml` keys and defaults
- `docs/executor-capabilities.md` — capability matrix comparing Claude, Codex, Aider, and Ollama across headless support, prompt transport, local model support, auto-commit behavior, and sandbox status
- `.vyuha.yml.example` — annotated example configuration
