Verification index

Every claim here, and the artefact that supports it.

This page exists to make verification trivial. Each claim below links to the primary artefact behind it, so a reader can confirm the work without asking for anything. Material that is not public is listed as available on request, with its status stated plainly.

What this record covers

Where the evidence sits

The four areas this work is assessed on, and the artefacts that back each one.

Original published work

Three open-source tools under permissive licences: a local CI gate, a dependency-free mock engine for third-party APIs, and an air-gapped automation platform. The first two ship with the harness that produced their measurements, so the performance claims can be independently reproduced.

Evidence of professional and technical competence

A published evidence document that shows how each number was taken, discloses the measurement that was discarded, and has a dedicated section listing the claims that are not made. A platform whose architecture is checkable by reading its layout rather than by trusting a benchmark.

Recognition beyond a single employer

A dated body of published writing spanning 2013 to 2026, addressed to working engineers rather than to an employer, plus live documentation sites and public repositories for each project.

Ongoing public activity

A continuous record of shipping and publishing, evidenced by the activity log and the commit history of each repository.

Provenance

The commits and builds behind the claims

Every claim on this site resolves to a specific commit and, where the claim is a measurement, to a specific green build of that commit. The hashes below are the ones the site was built from.

RepositoryCommitBuildMeasured
ci-kit c761ca34a10a success 2026-10-21
api-mock-services 1454a6163339 success 2026-10-21
omeiza-workspace.github.io 7480f0b6c1e success 2026-10-21

Frictionless verification

How to check each claim

Every claim on this site is checkable against a public artefact. Here is the index.

The body of published writing is dated and public

Thirty articles between 2013 and 2026, with their original dates and source markdown.

/archive/

Recent technical writing exists and is cross-posted

Long-form essays published here, on Substack and on Dev.to, with RSS.

/blog/

The document pack

What is public, and what is on request

The full pack is supplied directly to the endorsing body. This table states what exists, so nothing has to be requested blind.

ItemStatusAvailability
Published repositories and their commit history Public https://github.com/omeiza-workspace
Evidence document with the measurements Public ci-kit/docs/EVIDENCE.md
Published writing, 2013–2026 Public /archive/ and /blog/
Project documentation sites Public github.io pages for each project
CV and employment history Held Available on request

Current state

Where the work stands

The projects, the releases and the published measurement behind them.

Published and live

  • CI Kit — v0.2.0 released, with its evidence document and a live documentation site.
  • api-mock-services — v1.0.0 released, eighteen providers, footprint enforced as a build gate.
  • Two documentation sites, published from the repositories on every push.
  • A measurement record that states how each number was taken, and what is not claimed.
  • 29 dated articles spanning 2013–2025, and four written for a specialist audience in 2026.

Work in progress

  • The Automation Gateway — an air-gapped Windows Service that runs enterprise workflows from JSON blueprints. In development; the architecture is written up, and the repository is on its way.
  • The npm package is being published under the @bytesickle scope, alongside the repositories under omeiza-workspace.
  • Adopters, mentions and contributed mocks are all accepted by pull request. The mechanism is published, the contribution guide is in each repository, and the review is fast.

Open to platform engineering and developer infrastructure work

Available for contract, fractional and permanent roles in platform engineering, developer experience and infrastructure tooling. Also available to speak and to review infrastructure work. For anything not on this page, email is the fastest route — I respond to technical and collaboration enquiries within two working days.