Reference build
An inspectable system or repository that demonstrates an engineering pattern. It is not automatically a production deployment.
Toledo Technologies · evidence pressing 001
Proof, with the labels left on.
This ledger separates what was built, what was observed, and what is only a sample. No project count, deployment claim, or client story is implied by a repository existing.
Research note
A dated analysis of public evidence. It is not presented as a paid engagement, private audit, or client outcome.
Sample deliverable
A clearly labeled example of the artifact a discovery can produce. It contains no invented client provenance.
Side A · reference builds
Systems you can inspect
Capability references only. These codebases are not offered for sale or license.
- 01 TallySec A security-education reference that combines deterministic scoring, synthetic data, structured labs, assessments, and a FastAPI service.
- 02 ComplyCrawl A Python web-automation reference built around robots.txt checks, tamper-evident audit trails, and explicit crawl controls.
- 03 AegisTwin An engineering reference for event-driven agent architecture, policy gates, deterministic replay, and local memory graphs.
DELPHI / OUTPUT SPECIMEN 01
What paid discovery leaves behind
SAMPLE
NOT A CASE STUDY
NOT A CASE STUDY
- 01:12 Decision record
Business goal, constraints, assumptions, and rejected alternatives.
- 03:40 Risk map
Dependencies, failure modes, open questions, and a named mitigation owner.
- 07:05 Scope sheet
Included work, exclusions, acceptance criteria, and handoff boundary.
- 11:18 Quote basis
Milestones, calendar, payment structure, and the evidence behind the number.
Your system will have its own evidence
Need a custom build?
Start with the business problem and the operating constraints. A web application build begins at $15K; discovery is scoped separately when the unknowns need to be resolved first.
Describe the system