Colophon
This site is an engineering project: turning a working archive into a public record that can be checked. I keep source material separate from the pages, review what the evidence supports, and use repeatable builds to publish it. This colophon explains the decisions behind that system, including what failed and what changed.
AI assists with retrieval, organization, proposed interpretations, and software construction. I am responsible for the accepted account, attribution, and decision to publish.
Notebooks, CAD, test reports, photographs, and program documents.
Select what the evidence supports; retain its limits and attribution.
Curate the accepted project account separately from the website.
Generate the site and check specified integrity and consistency rules.
Publish the reviewed record as static pages with links to permitted evidence.
A file hash establishes identity, not interpretation. A passing build checks specified rules; it does not establish historical truth or replace review of the evidence.
Software & construction
Source material stays separate from the authored record. Human review establishes the account; repeatable generation and checks carry it into the public site. EN-OS explains that boundary, the earlier publication failures, and their correction.
The portfolio remediation removed fabricated fallback content and added checks against regression. Unsupported details were omitted instead of replaced with plausible prose. The record became more credible by showing the limits of its evidence.
In a bounded Kandev Desktop v0.90.0 pilot, a real task resumed with its scope, worktree, and reviewed artifact intact, then the accepted work merged. Adoption remained conditional on a governed adapter and explicit human approval. Autonomous second-agent review was not demonstrated.
The engineering record
Selected engineering decisions, linked to the project records behind them. Revision counts, measurements, estimates, and outcomes retain their distinct meanings and qualifications. How I Work describes the wider practice.
c24
I controlled C|24 board interfaces through Data Control Drawings. The June register lists 19 distinct PCBA designs; the MicPre8 I/O drawing records 12 revisions.
Read the project account →avegant-glyph
I took responsibility for Glyph's full mechanical bill of materials through tooling validation and production ramp, working with Intretech and component suppliers. Chris Westra, Misha Young and I worked through part fit, tooling corrections, finish requirements and readiness for the next build.
Read the project account →sc48
Compared SC48 4U configurations with three 80 mm fans at 8.5 V and 12 V: left R69 rise differed by 9.9°C and absolute temperature by 11.6°C, with differing ambient conditions.
Read the project account →c24
I designed the field-replaceable C|24 headphone-jack unit that shipped, with Arndt Hufenbach and Manufacturing pressing for service access. The earlier recessed mock-up had been rejected.
Read the project account →avegant-glyph
I proposed, tested and brought Glyph's optional headstrap into production, with Radius developing concepts and mockups. It shifted most of the load from the nosepiece to the top of the head. The earcups still had to grip firmly enough for use without the strap, so ear pressure remained.
Read the project account →c24
One C|24 side-cap sample lost 1.04 mm in length through painting and ended 2.27 mm below its lower drawing limit. Flatness was measured separately; the cure-support comparison addressed deformation.
Read the project account →c24
C|24's requirements called for an external power supply and prohibited a fan at the listening position. Moving power conversion outside the console helped make the lower-profile enclosure possible.
Read the project account →c24
C|24's July financial plan estimated 51.8% gross margin at an $8995 suggested retail price.
Read the project account →An automated curation system can reduce a pile without pretending to make the editorial judgment. On August 12, 2026, it moved 1,820 records into a traceable archive, drafted nine merges, and reduced the queue from 1,885 to 65. The remaining act was human: decide which evidence deserved a public story.
Accepted mutable work must be reachable from origin/main; read-only work needs no commit ceremony. Advisory lane warnings, isolated worktrees, and reachability and push-parity checks each cover a different failure mode, making completion observable.
Explore the Design system and Technical documentation.