Selected Work
A technical SEO portfolio and AI systems portfolio with six public artifacts, explicit ownership, implementation details, constraints, and inspectable evidence.
Six Public Artifacts
Atlas SEO Audit Console
Problem: Technical audits lose credibility when recommendations cannot be traced back to URL-level evidence.
Role: Founder; product architecture, crawler behavior, evidence-state policy, review workflow, and interface design.
Built: Native crawl records, raw/render comparison, indexability and canonical checks, link graphs, SQLite-backed run persistence, issue review, and structured export paths.
Constraints: Provider gaps, failed fetches, challenge pages, and contaminated renders remain measurement gaps—not site-health findings.
Status: Core crawl and evidence workflow implemented; public proof covers bounded source capture and a render-review state. Provider mesh and scoring policy remain active development.
Not public: Private targets, client records, credentials, and unreviewed provider output.
Inspect the sanitized crawl run
Who Owns the Toll Roads in Texas?
Problem: “Who owns the road?” collapses public title, concession rights, creditors, operators, billing, and residual value into one misleading answer.
Role: Research design, source ledger, ownership model, calculations, writing, and visual explanation.
Built: An answer-first statewide ownership lookup, downloadable CSV, toll-dollar waterfall, project comparison, finite-life DCF screen, fact-gap ledger, and primary-source index.
Constraints: Public/private distinctions, dated cap tables, analyst estimates, and missing disclosures stay labeled throughout.
Status: Published July 11, 2026; ownership lookup and reader updated July 23, with the evidence cutoff preserved.
Not public: No private diligence, bids, carrying values, or current security recommendations.
ViralBench + Codex Improvement Harness
Problem: A leaderboard score does not explain why an agent succeeded, failed, regressed, or improved across controlled trials.
Role: Code-level audit, evaluation architecture, experiment design, and technical writing.
Built: A proposed trace schema, replay layer, controlled-trial loop, evidence boundary, and bounded Codex engineering workflow.
Constraints: The article separates implemented repository behavior from proposed harness work and unverified production coverage.
Status: Published engineering design; not represented as a deployed evaluation service.
Not public: Credentials, live campaign data, and any production experiments not evidenced in the public repository.
Read the architecture and limits
Austin Crawlability Pilot
Problem: Local-service SEO advice is often published without a bounded sample, inspectable rows, or a distinction between access gaps and negative findings.
Role: Study design, public collection, measurement-gap policy, analysis, and publication.
Built: A 12-site homepage/robots/sitemap pilot, aggregate summary, public CSV, methodology, and cutoff-aware reporting.
Constraints: The pilot is not representative and makes no ranking, traffic, conversion, revenue, citation, or site-health claim.
Status: Published pilot generated June 25, 2026.
Not public: No private analytics, Search Console data, client identity, or broader Austin-market inference.
Void Agency
Problem: Teams need a bounded route from crawl evidence to implementation work without a generic growth retainer or opaque audit deck.
Role: Founder and operator across scoping, audit systems, implementation, analytics, and client delivery.
Built: A technical SEO and web-systems practice with a four-stage method, explicit inputs and exclusions, Atlas-backed evidence paths, implementation handoffs, analytics review, and acceptance checks.
Constraints: Private client names and outcome data remain private; the public site shows method and artifacts instead.
Status: Operating; $50K+ collected revenue as of May 31, 2026. The figure is a first-party claim; the linked method does not verify revenue.
Not public: Client identities, credentials, unreleased deliverables, and unsupported outcome claims.
Sulayman Bowles Technical Ledger
Problem: Code, experiments, competition work, and technical notes become hard to inspect when scattered across repositories and old portfolio surfaces.
Role: Builder, editor, and maintainer of the public proof layer.
Built: A separate artifact domain for projects, source links, technical notes, and durable records that support—rather than duplicate—the identity site.
Constraints: The ledger stays artifact-first and routes canonical identity context back to this site.
Status: Live public proof layer; reviewed July 12, 2026.
Not public: Private repositories, abandoned experiments without learning value, and secrets or local machine state.
Supporting Links
See an Atlas sample crawl run
A sanitized crawl table showing URL status, indexability, links, canonicals, and issue notes.
Read the technical SEO audit method
The process page for crawl, diagnose, repair, and measure work.
View the GitHub repo for the audit CLI
Public scraper and audit-system code.
Request an audit
Audit intake for technical SEO, site systems, analytics, and markets research.
Read the markets research memo with assumptions
Educational research memo with an assumptions table and clear limits.
Evidence Before Intake
What standard will the work use?
The public method shows evidence capture, finding review, owners, acceptance checks, and reruns. It is process evidence—not a client-outcome case study.
Can I inspect the proof before sharing access?
The Atlas demonstration exposes a dated, sanitized source record and its limits. It does not establish rankings, traffic, revenue, or full production coverage.
What makes a useful first brief?
Bring a site or product surface, the suspected evidence gap, and the decision the work must support. Keep credentials and sensitive client data out of the form.
Public Routes
- Home - Portfolio homepage and selected work.
- Work - Six public records with ownership, system details, status, constraints, and supporting evidence.
- Atlas - An in-development crawl and evidence system with capability and public-proof status.
- Research - Search, technical SEO, product, data, markets, and infrastructure research.
- About - Technical practice, current work, experience, and operating principles.
- Resume - Recruiter-ready experience, education, skills, and PDF.
- Contact - Direct email and a short project brief.
- SEO Audit Method - Technical SEO audit services, process, deliverables, and rerun checks.
- Austin Technical SEO - Austin technical SEO consultant, crawlability pilot, and audit entry point.
- Void Agency - External site for the fixed-scope technical SEO practice.
- HTML Sitemap - Plain links to every public canonical route.
- Tech Ledger - Technical projects, experiments, and project ledger.