Tenex source archive
Capture date: 2026-10-09. The archive contains 34 public sources. Original response files remain separate from this report. HTML captures exclude external scripts, images, fonts, and embedded media. A response hash confirms archive integrity. It does not confirm the source claim.
The manifest records URLs, redirects, authors, dates, access status, review scope, and file hashes. The search log records discovery paths and unresolved gaps. The report explains the system and assesses the evidence.
Review limits
We reviewed the main written articles that support the report. We reviewed selected sections of S13–S18 for methods and attribution. Their embedded episodes remain unreviewed. S21 contains a publisher account under a Transcript label. We did not review the complete audio or video. S23 and S24 contain application shells, not job descriptions. Their HTTP 200 status does not establish complete capture. S30 redirects to a current Claude webinar page. Its captured text does not name Tenex. S31–S33 provide public skill evidence. We did not install or execute the skill. The main branch URLs can change. The saved files and hashes preserve the inspected versions.
Source index
Article titles below preserve the original source text. A dash in the date column means that we did not establish a publication date.
Attribution and claim checks
S16 describes a Gauntlet AI method. S17 describes Vercel results. S18 describes a Bolt method. Those pages do not establish Tenex customer returns. S13 describes JJ Englert’s context method. It does not establish the exact MetaHarness architecture. S28 is a founder partnership announcement. We did not find a separate Vercel confirmation in this search. S29 lists tools across the founder’s businesses. It is not a current Tenex architecture specification.
Reuse and capture files
The catalogs preserve the selected URLs. The capture helper saves public responses and hashes. To repeat a capture, use a new folder and preserve the prior manifest. The current manifest includes researcher annotations after the initial capture. Original response bodies and headers retain their recorded hashes.