← Back to the dossier

THE SOURCE INDEX / EVIDENCE & SCOPE

Evidence has a boundary.

A repository, a first-hand account, and a simulation support different kinds of claims. This site keeps those distinctions visible.

CASE 01

Dynamo Air

Read the case →
Source inspection

Source-controlled engineering documentation

Local repository and authored commit history support participation in Git-based technical documentation. The supplied account and prior portfolio review describe AI assistance and engineering review.

What this does not establish

Company documents remain private. Repository participation does not establish design authority, certification responsibility, exact employment dates, or measured outcomes.

CASE 02

Conduit

Read the case →
First-hand account

Industrial field work and customer context

Fitz’s account, recorded in the November 2026 portfolio review, describes factory visits, customer knowledge bases, presentation tools, and work as a field-deployed engineering intern.

What this does not establish

Customer conversations and artifacts are not public. The workflow is author-reported, not independently verified by a public artifact; no quantified business outcome is claimed.

CASE 03

Avorth

Read the case →
Source inspection

Read-only adapters and coverage state

Inspected accounting and field-service adapters reject accounting writes and expose whether paginated reads reached the end.

What this does not establish

Private code and account records are withheld. Code inspection does not establish production adoption, complete coverage of every API, or a fresh test run.

Source inspection

Approval, delivery, and acknowledgement

Engine code and test assertions were inspected for exact-payload approval, stale or corrupted hashes, and acknowledgement versus exhausted escalation.

What this does not establish

Paging is simulated. Assertions were read, not rerun for this site. This is a prototype account, not an independent security audit or proof of live dispatch.

CASE 04

VALUN

Read the case →
Documentation review

Work states and signed checker receipts

Current private repository documentation describes a work lifecycle, delivery-bound checker receipts, configured trust roots, and a hash-chained event log.

What this does not establish

The implementation and sandbox were not independently audited. Identity-to-address mapping is operator-asserted; mock settlement proves no real payment. Private source is not linked.

CASE 05

Compute & energy

Read the case →
Saved simulation

Projection-error results

A sanitized excerpt of the saved numerical results supplies the projection-error values shown in the notebook. Published values were compared with the original CSV.

What this does not establish

A narrow model slice, not end-to-end model quality or physical hardware. The original experiment was not rerun for this site.

Download projection data · CSV
Analytical note

Sampling-node and schedule arithmetic

Explicit units and assumptions reproduce the sampling-node charge/reset bound and compare rounded active-tile subtotals at the same ideal readout time.

What this does not establish

These are analytical bounds and reported estimates. Omitted drive, routing, idle, wake-up and reduction costs prevent a system-level savings claim. No hardware measurement is implied.

Download calculation note · TXT

What the status labels mean

USED
Used in a real workflow, with the source of that account identified. It does not imply a measured outcome.
BUILT
Implemented software was inspected. This does not imply deployment, adoption, or a new independent test run.
PROTOTYPE
A limited implementation or documented prototype. Production behavior is not implied.
EXPERIMENT
A numerical or technical experiment with a stated scope. Simulation is distinct from hardware measurement.

Evidence available here

What remains private

Company engineering documents, customer conversations, account records, and private repositories are not reproduced or linked. The Dynamo and Avorth pages describe abstracted workflows. Conduit’s account is explicitly first-hand; its customer artifacts are not public.

VALUN’s page describes the current private repository documentation. It does not substitute for an implementation audit or establish that sandboxing, identity, or settlement boundaries hold against an adversary.

What is deliberately not claimed

No invented adoption metrics, time savings, production reliability, engineering authority, hardware efficiency gains, or model-quality improvements. The compute notebook does not equate projection error with end-to-end language-model quality.

Open questions describe current interests. They are not professional titles or claims of power-engineering, HPC, or ML-research expertise.

Résumé and contact

The résumé download is withheld while an older PDF and unresolved source claims are reconciled. Request a current résumé by email. A LinkedIn link will be added when the correct profile URL is confirmed.