Sonvik

Explore. Execute. Verify.

Sonvik is an open-source tool for executing and verifying APIs from readable, versionable files. It runs locally, requires no account, and produces reproducible results in both development and CI.

Why Sonvik

  • Local-first: your requests and configuration remain in your files.
  • Git-native: tests are reviewed and versioned alongside the code.
  • Automation-ready: the same command works locally and in CI.
  • No GUI or cloud dependency: the MVP starts with a small, portable CLI.

Project status

Sonvik is building its 0.1.0 MVP: HTTP requests defined in YAML, optional environments, variable substitution, status verification, and stable exit codes.

Documentación en español · Read the English documentation · View the project on GitHub

Documentation

  • Documentation version: 0.1.0
  • Target product: MVP 0.1.0
  • Canonical language: Spanish; synchronized English translation
  • Last synchronized: 2026-10-16

This directory contains Sonvik's living documentation. The original brief (ES · EN) preserves the initial exploration; these documents turn that vision into traceable scope, requirements, and decisions.

Documentation map

ID Español English Purpose
BRIEF Brief del proyecto Project brief Initial context and non-normative proposals
DOC-01 Visión y alcance Vision and scope Problem, value proposition, and boundaries
DOC-02 Especificación de requisitos Software requirements Verifiable MVP behavior
DOC-03 Casos de uso Use cases Interactions and alternative flows
DOC-04 Arquitectura de software Software architecture Boundaries, flow, deployment, and security
DOC-05 Diccionario de datos Data dictionary Minimal canonical model and validation rules
DOC-06 Roadmap y gobernanza Roadmap and governance Delivery, quality, risks, and change management
ADR-001 Arquitectura y alcance del MVP MVP architecture and scope First architecture decision

Statuses

Draft → In review → Approved → Superseded or Retired.

Rules

  1. Spanish is the canonical source; the English version is synchronized in the same change.
  2. IDs are not reused; a removed item changes status.
  3. A behavior change updates the affected requirements, use cases, and criteria.
  4. Significant architecture decisions are recorded in docs/adr/.
  5. Markdown is the source of truth; other formats are generated artifacts.