{
  "id": "technical-ledger-index",
  "title": "Technical Ledger Public Index Dataset",
  "description": "A structured public index of the ledger records represented on sulayman-bowles.tech, intended for crawlability, source-graph inspection, and artifact-page validation.",
  "generatedFrom": "src/content/technicalLedger.ts",
  "generatedAt": "2026-06-26",
  "rows": [
    {
      "id": "atlas-engine",
      "title": "Atlas / Atlas Engine",
      "category": "major-system",
      "status": "active build",
      "visibility": "mixed public/private",
      "period": "2025-present",
      "route": "/atlas",
      "canonicalUrl": "https://sulayman-bowles.tech/atlas",
      "tags": [
        "Python",
        "SQLite",
        "crawl evidence",
        "technical SEO",
        "artifact exports",
        "review gates"
      ],
      "summary": "Python and SQLite audit console for crawl evidence, technical SEO diagnostics, search visibility testing, issue scoring, artifact exports, and operator/client review workflows.",
      "problem": "Technical SEO and AI-search audits can overstate findings when crawl state, render state, provider failures, or challenge pages are not separated from site-health evidence.",
      "approach": "Store URL-level crawl records, distinguish raw and rendered evidence, classify access states, score issues conservatively, and gate exports through operator review before client handoff.",
      "evidenceState": "Public summary and sample-oriented descriptions are available. Some implementation details, client-specific evidence, and operator artifacts remain private or operator-only.",
      "boundary": "Atlas should be described as an active technical system, not as a fully finished commercial platform or a guarantee of ranking outcomes.",
      "related": [
        "crawler-provider-research",
        "rank-correlation",
        "schema-evidence-packaging",
        "atlas-dashboard"
      ]
    },
    {
      "id": "ai-search-entity-ownership",
      "title": "AI Search Visibility / Entity Ownership",
      "category": "research-thread",
      "status": "active research",
      "visibility": "public summary",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "entity SEO",
        "structured data",
        "canonical pages",
        "LLM search",
        "source graph"
      ],
      "summary": "Research into how owned domains, structured data, answerable pages, canonical links, and proof surfaces make technical work easier to retrieve and cite accurately.",
      "problem": "Search engines and LLM search systems can blend stale snippets, partial profiles, and weak source pages when a person or project lacks clear owned public references.",
      "approach": "Separate the canonical identity hub, technical ledger, and commercial property; write crawlable first paragraphs; expose sameAs links; and publish source-like pages with conservative schema.",
      "evidenceState": "Public pages can show the domain architecture and source graph. Provider-specific discovery remains a research and monitoring problem.",
      "boundary": "This is retrieval clarity and source hygiene, not prompt injection, manipulation, or unsupported claims about model behavior.",
      "related": [
        "personal-site-entity-system",
        "void-commercial-layer",
        "schema-evidence-packaging"
      ]
    },
    {
      "id": "crawler-provider-research",
      "title": "Crawler / Provider Comparison Research",
      "category": "research-thread",
      "status": "active research",
      "visibility": "mixed public/private",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "Firecrawl",
        "Exa",
        "Apify",
        "rendering",
        "robots",
        "WAF",
        "measurement state"
      ],
      "summary": "Research into the reliability limits of internal crawlers and external providers across robots handling, sitemap recovery, rendering, WAF/challenge pages, and coverage gaps.",
      "problem": "Incomplete crawls, blocked fetches, challenge pages, and provider caps can look like site problems if measurement state is not modeled explicitly.",
      "approach": "Compare raw fetches, rendered content, sitemap sources, external provider returns, and failure states before converting observations into audit findings.",
      "evidenceState": "Public summaries describe the measurement boundary. Provider logs, private sites, and failed-run details may remain private.",
      "boundary": "Provider gaps are measurement gaps. They are not automatically client-visible SEO issues.",
      "related": [
        "atlas-engine",
        "challenge-render-contamination",
        "schema-evidence-packaging"
      ]
    },
    {
      "id": "rank-correlation",
      "title": "Search Rank Correlation Experiments",
      "category": "research-thread",
      "status": "active research",
      "visibility": "private evidence",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "ranking",
        "local search",
        "B2B queries",
        "confounders",
        "measurement design"
      ],
      "summary": "Measurement-design experiments testing whether Atlas-style technical scores correlate with local and B2B service-query ranking behavior.",
      "problem": "Ranking behavior is confounded by backlinks, domain authority, proximity, reviews, SERP features, brand demand, landing-page fit, freshness, and crawl/provider failures.",
      "approach": "Treat ranking correlation as an experimental design problem with explicit confounders, query classes, and evidence limits.",
      "evidenceState": "The current public state is research framing. No conclusive ranking-causality claim is made here.",
      "boundary": "Do not describe this work as proven ranking performance or guaranteed SEO lift.",
      "related": [
        "atlas-engine",
        "gbp-local-search",
        "backlink-authority-measurement"
      ]
    },
    {
      "id": "personal-site-entity-system",
      "title": "Personal Site Entity System",
      "category": "owned-property",
      "status": "maintained",
      "visibility": "public artifacts",
      "period": "2025-present",
      "route": "/systems",
      "canonicalUrl": "https://sulayman-bowles.tech/systems",
      "tags": [
        "canonical identity",
        "sameAs",
        "sitemap",
        "robots.txt",
        "llms.txt",
        "owned domains"
      ],
      "summary": "The owned web-footprint system behind Sulayman Bowles public identity, with the personal site as canonical hub and specialized properties for technical and commercial context.",
      "problem": "A personal site, agency site, technical project pages, public profiles, and research artifacts need distinct roles so search systems do not collapse them into one vague profile.",
      "approach": "Keep sulayman-bowles.dev as the identity source, sulayman-bowles.tech as the technical ledger, Void as the commercial layer, and public profiles as corroborating proof surfaces.",
      "evidenceState": "The domain roles, sitemap coverage, robots guidance, llms.txt files, and canonical links are public.",
      "boundary": "The technical ledger supports the identity hub. It does not replace the personal site.",
      "related": [
        "ai-search-entity-ownership",
        "void-commercial-layer",
        "schema-evidence-packaging"
      ]
    },
    {
      "id": "finance-research-archive",
      "title": "Finance Research Archive",
      "category": "research-thread",
      "status": "maintained",
      "visibility": "public summary",
      "period": "2024-present",
      "route": "/ledger",
      "canonicalUrl": "https://sulayman-bowles.tech/ledger",
      "tags": [
        "valuation",
        "market structure",
        "AI infrastructure",
        "fintech",
        "crypto",
        "semiconductors"
      ],
      "summary": "Structured archive for finance, valuation, market-structure, public-equity, AI infrastructure, fintech, crypto, semiconductor, and venture-style research.",
      "problem": "Analytical finance work can become misleading if it reads like advice, performance marketing, or undisclosed trading results.",
      "approach": "Frame finance material as research, valuation thinking, market structure notes, and evidence-backed analysis without performance claims.",
      "evidenceState": "Public summaries and research-page references exist. Sensitive trading details and private analysis are not disclosed.",
      "boundary": "This is not investment advice and does not claim returns or trading performance.",
      "related": [
        "personal-site-entity-system"
      ]
    },
    {
      "id": "living-codebase-atlas",
      "title": "Living Codebase Atlas",
      "category": "prototype",
      "status": "prototype",
      "visibility": "private evidence",
      "period": "2025-present",
      "route": "/ledger",
      "canonicalUrl": "https://sulayman-bowles.tech/ledger",
      "tags": [
        "agent workflows",
        "architecture maps",
        "regression matrix",
        "context bundles"
      ],
      "summary": "Agent-workflow system for turning a codebase into an architecture map, context bundle, regression matrix, issue triage record, and reviewable prompt packet.",
      "problem": "Long-running engineering work loses context when architecture, test expectations, decisions, and file-linked evidence are spread across chat history and local notes.",
      "approach": "Generate module maps, review packets, regression checklists, and file-linked context that agents and humans can use before changing code.",
      "evidenceState": "The public state is a summary. Working materials may be private, repo-specific, or operator-only.",
      "boundary": "Treat as a prototype workflow, not a packaged developer platform.",
      "related": [
        "atlas-engine",
        "agent-harness"
      ]
    },
    {
      "id": "void-commercial-layer",
      "title": "Void Agency as Commercial Application Layer",
      "category": "commercial-layer",
      "status": "maintained",
      "visibility": "public summary",
      "period": "2025-present",
      "route": "/systems",
      "canonicalUrl": "https://sulayman-bowles.tech/systems",
      "tags": [
        "technical SEO",
        "AI-search visibility",
        "commercial layer",
        "service context"
      ],
      "summary": "Commercial property where technical SEO and AI-search visibility work can be applied as services without making the technical ledger a sales page.",
      "problem": "Technical research, identity proof, and commercial service pages need separate functions to avoid confusing project evidence with marketing language.",
      "approach": "Keep Void focused on business/service context while the `.tech` property records the underlying systems, research threads, and evidence boundaries.",
      "evidenceState": "The commercial site is public. Private client details, private revenue, and unsupported client outcomes are not represented here.",
      "boundary": "Void is relevant context, not the center of sulayman-bowles.tech.",
      "related": [
        "ai-search-entity-ownership",
        "personal-site-entity-system",
        "atlas-engine"
      ]
    },
    {
      "id": "distributor-intake-copilot",
      "title": "Distributor Intake Copilot",
      "category": "prototype",
      "status": "partial",
      "visibility": "private evidence",
      "period": "2025",
      "route": "/ledger",
      "canonicalUrl": "https://sulayman-bowles.tech/ledger",
      "tags": [
        "offline prototype",
        "classification",
        "review states",
        "exports"
      ],
      "summary": "Offline prototype for classification, matching, policy handling, correction capture, review states, and exportable operating records.",
      "problem": "Operational intake flows need repeatable classification and review records without overstating automation or bypassing human review.",
      "approach": "Prototype offline snapshot/replay, correction capture, policy labels, and exportable records around reviewable decisions.",
      "evidenceState": "Partial local prototype context exists. Public proof is limited to a conservative summary.",
      "boundary": "Do not frame this as a live production system unless public evidence changes.",
      "related": [
        "living-codebase-atlas",
        "agent-harness"
      ]
    },
    {
      "id": "project-janus",
      "title": "Project Janus",
      "category": "archive",
      "status": "archived",
      "visibility": "private evidence",
      "period": "2024-2025",
      "route": "/ledger",
      "canonicalUrl": "https://sulayman-bowles.tech/ledger",
      "tags": [
        "market structure",
        "exchange data",
        "order books",
        "options overlays"
      ],
      "summary": "Archived finance and market-structure experimentation around exchange data, order-book structure, and options overlay research.",
      "problem": "Market-structure experiments are easy to misread as trading advice or performance records when the actual value is in research design.",
      "approach": "Preserve the project as archived experimentation and avoid publishing trading-performance claims.",
      "evidenceState": "Private or archived materials may exist. Public representation is intentionally narrow.",
      "boundary": "No investment advice, trading result, or performance claim is made.",
      "related": [
        "finance-research-archive"
      ]
    },
    {
      "id": "atlas-dashboard",
      "title": "Atlas Dashboard / Operator Console",
      "category": "major-system",
      "status": "active build",
      "visibility": "operator-only",
      "period": "2025-present",
      "route": "/atlas",
      "canonicalUrl": "https://sulayman-bowles.tech/atlas",
      "tags": [
        "operator console",
        "review states",
        "artifact integrity",
        "publish gates"
      ],
      "summary": "Operator-facing console concepts and review surfaces for triaging crawl records, issue states, artifact integrity, and publish readiness.",
      "problem": "Audit systems need internal review space where unsafe, partial, or failed evidence can be handled before any client-visible output exists.",
      "approach": "Separate operator-only states from publishable summaries and make review gates explicit.",
      "evidenceState": "Public descriptions are safe summaries. Detailed console workflows and client-specific records remain private or operator-only.",
      "boundary": "Operator-only findings should not be promoted as public claims.",
      "related": [
        "atlas-engine",
        "schema-evidence-packaging"
      ]
    },
    {
      "id": "agent-harness",
      "title": "Agent Harness / Scraper Abstraction",
      "category": "prototype",
      "status": "prototype",
      "visibility": "private evidence",
      "period": "2025-present",
      "route": "/ledger",
      "canonicalUrl": "https://sulayman-bowles.tech/ledger",
      "tags": [
        "agents",
        "scrapers",
        "queues",
        "provider boundaries",
        "auditability"
      ],
      "summary": "Experimental harness work around crawler/scraper abstractions, provider boundaries, queue operations, and reviewable agent outputs.",
      "problem": "Automated scraping and agent workflows need explicit provider boundaries, reproducible inputs, and auditable outputs.",
      "approach": "Keep provider behavior, failed states, generated artifacts, and review evidence separated in the workflow.",
      "evidenceState": "Current public evidence is summary-level only.",
      "boundary": "Treat as experimental infrastructure, not a universal autonomous browsing product.",
      "related": [
        "crawler-provider-research",
        "living-codebase-atlas",
        "challenge-render-contamination"
      ]
    },
    {
      "id": "gbp-local-search",
      "title": "GBP / Local Search Measurement Research",
      "category": "research-thread",
      "status": "active research",
      "visibility": "private evidence",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "Google Business Profile",
        "local search",
        "reviews",
        "proximity",
        "SERP features"
      ],
      "summary": "Research framing for measuring Google Business Profile strength, proximity, reviews, local packs, and local-service landing page fit.",
      "problem": "Local rankings blend site quality with geography, review strength, category fit, and SERP features.",
      "approach": "Keep local-search variables separate from crawl and technical SEO measurements.",
      "evidenceState": "Public summary only. No client-specific local ranking evidence is disclosed.",
      "boundary": "Do not infer client rankings or local-pack performance from this research page.",
      "related": [
        "rank-correlation",
        "backlink-authority-measurement"
      ]
    },
    {
      "id": "backlink-authority-measurement",
      "title": "Backlink / Directory / Brand Authority Measurement",
      "category": "research-thread",
      "status": "active research",
      "visibility": "public summary",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "backlinks",
        "directories",
        "brand authority",
        "confounders"
      ],
      "summary": "Research into how backlinks, directories, brand mentions, and authority surfaces confound technical-score interpretation.",
      "problem": "A technically weaker site can outrank a stronger one when authority, brand, or directory signals dominate the query class.",
      "approach": "Track authority variables as confounders instead of folding them into crawl-health evidence.",
      "evidenceState": "Public summary and method framing only.",
      "boundary": "Do not present authority research as a link-building guarantee.",
      "related": [
        "rank-correlation",
        "ai-search-entity-ownership"
      ]
    },
    {
      "id": "schema-evidence-packaging",
      "title": "Schema Validation and Evidence Packaging Research",
      "category": "research-thread",
      "status": "active research",
      "visibility": "mixed public/private",
      "period": "2025-present",
      "route": "/systems",
      "canonicalUrl": "https://sulayman-bowles.tech/systems",
      "tags": [
        "JSON-LD",
        "static HTML",
        "sitemap",
        "artifact integrity",
        "claim boundaries"
      ],
      "summary": "Research into JSON-LD, static fallback text, artifact manifests, route metadata, and client-safe evidence packaging.",
      "problem": "Structured data and generated artifacts can become misleading if they encode unsupported claims or stale run outputs.",
      "approach": "Use conservative JSON-LD, route-specific static content, manifest/run binding, and explicit claim boundaries.",
      "evidenceState": "The public site demonstrates route metadata, JSON-LD, sitemap, robots, llms.txt, and crawlable summaries.",
      "boundary": "Schema should describe public facts, not private proof or speculative claims.",
      "related": [
        "atlas-engine",
        "personal-site-entity-system",
        "crawler-provider-research"
      ]
    },
    {
      "id": "challenge-render-contamination",
      "title": "Challenge-Page / WAF / Render Contamination Research",
      "category": "research-thread",
      "status": "active research",
      "visibility": "mixed public/private",
      "period": "2025-present",
      "route": "/research",
      "canonicalUrl": "https://sulayman-bowles.tech/research",
      "tags": [
        "WAF",
        "challenge pages",
        "rendering",
        "false positives",
        "crawl safety"
      ],
      "summary": "Research into detecting when bot challenges, WAF interstitials, failed renders, or utility URLs contaminate crawl evidence.",
      "problem": "Rendered pages can be polluted by challenge pages or failed browser states, causing false findings and unsafe recommendations.",
      "approach": "Classify challenge, utility, failed-fetch, and render-contaminated states before issue scoring or client-facing actions.",
      "evidenceState": "The public state is a summary of the safety boundary.",
      "boundary": "Challenge pages and failed renders should not become normal recommendations.",
      "related": [
        "crawler-provider-research",
        "atlas-engine",
        "agent-harness"
      ]
    }
  ]
}