INDEPENDENT EXPERIMENTAL ENGINEERINGSYSTEMS / SOFTWARE / RESEARCH

PROJECT
TRINITYⅢ

A small systems laboratory.
Built from the inside out.

Software, reverse engineering, and the structures underneath. A growing body of work, research, and references by Jesus Chavez.

01 / Being built

Work index ↗

PRJ-001 / ACTIVE DEVELOPMENT

Loupe

Looking inside
Windows executables.

A Windows executable is a set of decisions written into bytes. Loupe is how I’m learning to read them.

Explore the project ↗Run Loupe
PRJ-001 / LOUPESTATIC CORE
01PE filebytes on disk
02inspect.ParseHeaders · addresses · sections
03 / NATIVELoupe CLIUnicorn harness
Experimental execution
03 / BROWSERTrinity LabGo → WebAssembly
Static inspection
One image model. Two interfaces.
Architecture of the shared inspection boundary.
PRJ-002NoxStateful detection / Go / MITRE ATT&CK

02 / Being studied

Research index ↗

Where does
this address live?

VA = base + RVA

File bytes and virtual memory have different coordinates. A small distinction that the loader has to get right.

Follow the address model ↗
REC-001

PE address spaces

File offsets, relative virtual addresses, and the boundary between inspection and loading.

active notes / R01

03 / PERMANENT REFERENCE SET

Canon

Not inspiration. More like obligations.
The standard I am trying to meet.

REF-C / 1984

We disdained all existing software
The Evolution of the Unix Time-sharing System

Project Trinity is the independent work of Jesus Chavez, a software engineer studying systems, reverse engineering, and security.

Previously: backend and distributed systems at John Deere Financial and Fubo Gaming.

GitHub ↗LinkedIn ↗Current notes ↗