TAUSIK experimental

Core approach

Runs over an existing agent through MCP tools, skills, and host-dependent hooks. QG-0 requires a goal and acceptance criteria before task start; QG-2 checks verification evidence before task completion. Scoped verification runs can issue ed25519-signed receipts recording the checked code state, while a local database preserves decisions and dead ends across sessions.

Workflow

1. Install as a git submodule and run the Python bootstrap for the chosen host
2. /start — open a session and load project state and knowledge
3. /plan — capture requirements and create tasks with goals and acceptance criteria
4. /task <slug> — pass QG-0 and implement within the task scope
5. tausik verify --task <slug> — run scoped checks and issue a receipt when signing is configured
6. /ship — review, test, verify acceptance criteria, pass QG-2, and commit
7. /end — capture knowledge and prepare the session handoff

Supported tools

• Claude Code
• Codex
• Qwen Code
• Cursor
• Kilo
• OpenCode

Notes

TAUSIK (Task Agent Unified Supervision, Inspection & Knowledge) implements a task-specification and verification workflow over existing coding agents. It declares conformance to SENAR Core. The reviewed repository documents bootstrap installation, host integrations, task gates, receipts, and self-use in TAUSIK’s own development.

The submission’s claim that every task needs a passing, signed receipt is broader than the documented behavior. The receipt guide retains a fresh-run completion path without an explicit signed handle, and the task reference documents a recorded acknowledgment when no test gate applies. Receipt scope divergence is recorded and does not always block completion. These distinctions matter when interpreting a green result.

The experimental rating reflects limited independently verifiable adoption and the evolving verification contract. This review checked public documentation and the verify-first gate source; it did not run the software or independently validate the project’s self-reported effectiveness.

Sources

• README: installation, host matrix, self-use, and reported token comparison
• Task lifecycle and verification exceptions
• Signed receipts, scope, compatibility, and trust model
• Verify-first gate implementation
• Planning skill
• Ship skill

Added Sep 30, 2026 · Assessment last reviewed Sep 30, 2026 · How we track