drce-public-20260924.1Corpus method
How to read this evidence
Excerpts identify relevant resources. Assess accomplishments through complete documents, material evidence and qualifications; this selection does not support complete private-history assessment.
Representations
Markdown, structured records and PDFs express the same selected meaning. Cases and evidence companions have distinct reading jobs; alternate formats of either are not independent corroboration.
Evidence interpretation
Preserve attribution, dates, revisions, evidence classes, limits and availability. Distinguish implementation from execution, AI contribution from Justin's direction and judgment, and bounded results from broader scientific, clinical or commercial outcomes.
Search is routing
Ranking is retrieval relevance only. Enumerate the map independently; a missing hit does not establish absence from the release.
Citation
Cite exact release and stable resource identity, state complete or excerpted scope, and retain material limits with the proposition.
Career orientation and RH Mission
Understand the professional account and inspect its most distinctive integrated agent-system project.
Use other complete cases and companions for their project claims; the public selection is not the complete Development Record.
- Supports: Assessment of the selected career account and bounded RH engineering contribution
- Does not support: Whole-history assessment
- Does not support: A solved RH or proven sustained autonomous scientific capability
Read this guide and enumerate the complete map.
- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Read the full technical CV.
- Full technical CVPresent the complete accepted technical CV.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Recommended companions- Professional narrativePresent the accepted professional development narrative.
Read the RH case and evidence together, following the fixed public-source links to the four examples and live successor while retaining their qualification boundaries.
- RH Mission case studyExplain the selected engineering case in its complete accepted narrative.
- RH Mission evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Full technical CVPresent the complete accepted technical CV.
Required companions- RH Mission evidence companionPreserve the complete selected evidence meaning for this release.
Read the professional narrative for the broader story and human-AI attribution.
- Professional narrativePresent the accepted professional development narrative.
Prerequisites- Full technical CVPresent the complete accepted technical CV.
Recommended companions- CTX Engine case studyExplain the selected engineering case in its complete accepted narrative.
- Pre-Note Delta case studyExplain the selected engineering case in its complete accepted narrative.
Choose the role-appropriate resume; these are alternative emphases, not independent evidence or separate employers.
- Agent systems resumePresent the accepted role-focused resume wording.
- Research and evaluations resumePresent the accepted role-focused resume wording.
- Agent infrastructure resumePresent the accepted role-focused resume wording.
Prerequisites- Full technical CVPresent the complete accepted technical CV.
Recommended companions- RH Mission case studyExplain the selected engineering case in its complete accepted narrative.
Agent execution and recovery
Inspect persistent workflow execution and its workstation mechanisms.
Preserve source, authored-test, retained-execution and firsthand-usage distinctions; procedural completion does not decide substantive correctness.
- Supports: Assessment of selected Runner and Workstation Control mechanisms and results
- Does not support: Universal reliability across tasks, clients or workstation conditions
Read Runner's complete case and evidence, then follow its public-source links; keep simulated recovery separate from live completion and stop.
- Protocol Runner case studyExplain the selected engineering case in its complete accepted narrative.
- Protocol Runner evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- Protocol Runner evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- Full technical CVPresent the complete accepted technical CV.
Follow Workstation Control's configuration-delivery and browser-ownership examples through their actual outcome boundaries.
- Workstation Control evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- Workstation Control evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- Protocol Runner evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Evaluation quality and experimental judgment
Examine whether tests measured intended usefulness and how results changed engineering decisions.
Keep development, held-out and broader comparisons separate; later diagnosis does not retroactively change a completed verdict.
- Supports: Assessment of selected comparative-evaluation and source-use investigations
- Does not support: General model superiority
- Does not support: Established clinical effectiveness or customer adoption
Read CTX's case and evidence, including protected comparisons, non-adoption and measurement limits.
- CTX Engine case studyExplain the selected engineering case in its complete accepted narrative.
- CTX Engine evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- CTX Engine evidence companionPreserve the complete selected evidence meaning for this release.
Read Pre-Note Delta's product, agent tooling, source-use evaluation and bounded deployment account.
- Pre-Note Delta case studyExplain the selected engineering case in its complete accepted narrative.
- Pre-Note Delta evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- Pre-Note Delta evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- CTX Engine evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Shipped application with public source
Inspect Life Links through fixed public source and bounded observations.
Preserve source revision and measurement population; retained aggregates do not make missing original measurements available.
- Supports: Assessment of included implementation and retained observations
- Does not support: Universal performance gains
- Does not support: Unmeasured adoption or later public-source changes
Read the complete Life Links companion and its intentional fixed-revision public links.
- Life Links evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- Life Links evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- Full technical CVPresent the complete accepted technical CV.
Retrieval, authorization and provenance
Inspect grounded repository access and the path from a corrected account to a release.
Preserve mutable versus immutable identity and Runner's execution role versus DRCE's record/release ownership.
- Supports: Assessment of selected Repo Reader and DRCE mechanisms within their evidence boundaries
- Does not support: Access to unselected private sources
- Does not support: Historical truth established merely by compilation
Read Repo Reader's selected source and authorization evidence.
- Repo Reader MCP evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- Repo Reader MCP evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- Full technical CVPresent the complete accepted technical CV.
Follow DRCE's corrected claim through source, test oracle, repair and release representation.
- DRCE evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.
Prerequisites- Justin Sublette - engineering work and selected evidenceEvaluate the published career account through complete application documents, substantial cases and inspectable selected evidence.
- Development Record Resource MapEnumerate every selected semantic resource and emitted representation.
Required companions- DRCE evidence companionPreserve the complete selected evidence meaning for this release.
Recommended companions- Protocol Runner evidenceProvide the accepted curated implementation extracts and recorded observations for inspection.