Skip to content
View zioladev's full-sized avatar

Block or report zioladev

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
.github/profile/README.md
Ziola

Independent software studio building working software for the agentic web.

ziola.dev  ·  hello@ziola.dev


What we build

Ziola builds for the agentic web — where models act through the tools a page exposes, not just the pixels it renders. Our work runs along three lines: conformance (holding a build to a standard, deterministically), capability discovery (finding, understanding, and running the tools a surface offers), and the infrastructure that makes agent actions inspectable, interoperable, and safe to execute.

Built, not pitched.


Open source

Open-source infrastructure for the WebMCP provider surface — define and validate structured browser tools, check any provider against the contract, then run and verify that independently built providers compose. Zero-dependency · TypeScript → ESM · Apache-2.0. Built from real multi-provider WebMCP journeys.


Status Qualification currently operates against Ziola's reference evidence format (provider-conformance-report/2). A generalizable ingestion layer - normalizing evidence from arbitrary WebMCP implementations - is in active development.


Early Releases Ziola packages are currently v0.1.0. Their contracts are implemented and tested, but intentionally open to revision as WebMCP evolves and real-world interoperability evidence accumulates.

Package Phase
@zioladev/provider-tools Provider Declaration · Phase 1 npm
@zioladev/provider-conformance Provider Conformance · Phase 2 npm
@zioladev/interop-runtime Interoperability Runtime · Phase 3 npm
@zioladev/interop-conformance Interoperability Qualification · Phase 4 npm
@zioladev/execution-control Execution Control · Phase 5 npm
@zioladev/cli CLI · Phase 6 npm

Roadmap

✓ Provider Tools  →  ✓ Provider Conformance  →  ✓ Multi-Provider Runtime  →  ✓ Interoperability Conformance  →  ✓ Execution Control  →  ✓ CLI  →  Generalizable Ingestion

Work

Project What it is Status
sirocco.gallery A design system that defends itself — a live WebMCP provider. Shipped · Origin Trial
swatchdog.dev The drift check for AI-built apps — design conformance over MCP. Shipped · Connector Directory
axiomdrift.ai Long-form human–LLM interaction, examined as structure. Research
refraktor.tech Discover, understand, and execute the tools a page exposes. Shipped · Chrome
treefrog.tech An interoperable WebMCP town — providers a consumer can chain. In build
selvage.dev The transaction boundary for agentic web actions. In build

Full case notes and live demos: ziola.dev/work


Research

Published under Axiom Drift, archived on Zenodo with DOIs.

  • Beyond Content — long-form interaction as measurable structure: Temporal Dynamics, Surface Matching, Two Archives.
  • Agentic Transaction AssuranceBefore the Provider Call: Enforcing Exact-Term Authorization for State-Changing Tool Actions — the research behind Selvage.

In the wild

  • Anthropic Connector Directory — swatchdog, listed
  • Chrome Web Store — Refraktor & Refraktor Pro
  • Chrome Origin Trial — sirocco.gallery & treefrog.tech, participants
  • Zenodo — peer-archivable research with DOIs
  • Vercel Community — swatchdog featured in the Weekly builders showcase

Writing

Field notes from the build — ziola.dev/notes:


ziola.dev  ·  hello@ziola.dev  ·  Ziola LLC · EST MMXXVI

Popular repositories Loading

  1. provider-tools provider-tools Public

    Define, validate, and register structured browser tools for the experimental WebMCP API

    TypeScript

  2. .github .github Public

  3. provider-conformance provider-conformance Public

    Measure WebMCP providers across models and runtimes. Attribute every failure to the layer that caused it. Keep the provider blameless when it's not at fault.

    TypeScript

  4. interop-runtime interop-runtime Public

    Model-agnostic runtime for executing stateful, multi-step trajectories across independent WebMCP providers.

    TypeScript

  5. interop-conformance interop-conformance Public

    Qualify WebMCP interoperability against frozen profiles: qualified / not_qualified / insufficient_evidence - no execution.

    TypeScript

  6. execution-control execution-control Public

    A neutral execution-control seam for agent tool calls: allow / block / indeterminate, only allow proceeds.

    TypeScript