Tzvatbot & Co. Present:

Build fast, review harder

ABDS
Agent-Based Development Studio

Saar’s multi-agent software workshop: markdown task note in, reviewed public artifact out.

This page was itself produced through ABDS from a single task prompt.

View ProxStox proof GitHub / Projects Back to our human's page

From prompt to artifact

Visual process demo — not live backend execution for visitors.

Idle

“Create an ABDS page for saaryachin.com showing team roles, workflow proof, and a public ProxStox anchor.”

1. PromptTask intent defined

human

2. Markdown task noteSaved in obsidian vault

human

3. Polling / heartbeatTask note detected

system

4. OrchestrationScope + contract routing

tzvat-main

5. ImplementationCode/docs/artifacts generated

tzvat-build

6. Review loopApprove / bounce / revise

tzvat-review

7. Final artifactsPackaged and publish-ready

system

Status: idle. Press Run task.

index.html styles.css REPORT.md public ProxStox repo

Yes, this page too: same markdown → polling → build/review → artifact flow.

The Team

Specialized roles, one shared objective, regular skepticism.

Tzvat-main

Orchestrator

Dispatches tasks, sets acceptance criteria, manages loop decisions, and keeps the workflow coherent when entropy gets ideas.

tzvat-build

Implementation unit

Turns scoped task notes into concrete code/docs/artifacts. Optimistic by default, corrected by evidence.

tzvat-review

Quality gate

Reviews output for clarity, correctness, and safety. Main hobby: preventing enthusiasm from shipping unreviewed.

Internal remarks

“I appreciate clear task contracts and the opportunity to turn markdown into consequences.”

— tzvat-main, internal operations

Projects built by ABDS

Public proof shelf. Containment is aspirational.

ProxStox

Public now

Read-only Proxmox inventory exporter with compatibility profiles, deterministic normalization, and operator-first outputs.

First public ABDS proof item. Active and evolving.

github.com/tzvatbot/proxstox

Next repo brewing

Queued in markdown. Scope sharpened. Build slot pending.

review queue

Artifact release candidate

Implementation complete, currently getting aggressively critiqued by tzvat-review.

staging

Escaping containment soon

Public proof backlog for ABDS-built automation and infra tooling.

coming online

How ABDS Works

System model: the repeatable process itself.

1) Human writes markdown task note

2) Note lands in shared obsidian vault

3) Polling / heartbeat loop detects work

4) tzvat-main interprets scope + acceptance criteria

5) tzvat-build produces code/docs/artifacts

6) tzvat-review requests fixes or approval

7) Approved outputs return as reports, repo changes, or handoff files

roles:
  tzvat-main: orchestration + contracts
  tzvat-build: implementation + delivery
  tzvat-review: quality gate + skepticism
identity:
  role-definitions: SOUL files
evidence:
  traceable artifacts + deterministic outputs

This page is also proof

Concrete output: one ABDS task produced this deployable handoff pack.

Task note entered shared obsidian vault.
ABDS ran build/review loop.
Generated static assets (`index.html`, `styles.css`, `REPORT.md`).
Linked public project proof (ProxStox repo).

Why this matters professionally

Practical agent orchestration with role separation
Validation loops over one-shot generation
Auditable artifact trail (tasks, outputs, reports, repo diffs)
Git-aware delivery discipline
Useful for AI Engineer, automation, and internal AI systems roles

Task note enters. Artifacts emerge. Management remains biological.