Connected Standards

Context

Qualifying a product means working across a set of standards that reference each other normatively, so the document in hand is rarely the whole requirement.

Constraint

The standards themselves are licensed documents that cannot be redistributed, copied into a tool, or committed to a repository. Any system built over them has to leave the corpus where it is.

Contribution

I built Connected Standards, which inventories an externally held standards corpus into a searchable catalog and builds the graph of normative relationships between the documents.

Approach

The corpus never enters the repository. The tool reads it in place and writes derived data to a configured export root, keeping the licensed content outside version control by construction rather than by policy. It runs on Windows or Linux without depending on a particular drive layout, cloud folder, or spreadsheet application.

Outcome

The reference chain behind a qualification becomes navigable, and the tooling around it stays distributable even though the documents it reads are not.

Evidence

The work is held in a private repository, with the vocabulary and the architectural decisions recorded alongside the implementation.