avesus.github.io

<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
    <title>Contact Brian Greenforest | Greenforest I/O</title>
    <meta name="description" content="Contact Brian Greenforest about funded R&D, FPGA systems, radio RTL, raw WebGL and GLSL computing, Cartilage, product architecture, fabrication, and technical leadership.">
    <meta name="robots" content="index, follow, max-snippet:-1, max-image-preview:large">
    <link rel="canonical" href="https://greenforest.io/contact.html">
    <meta property="og:title" content="Contact Greenforest I/O">
    <meta property="og:description" content="Bring the system and the boundary that blocks it across FPGA, radio, WebGL and GLSL, Cartilage, software architecture, semiconductor R&D, or product engineering.">
    <meta property="og:type" content="article">
    <meta property="og:url" content="https://greenforest.io/contact.html">
        <link rel="icon" href="/favicon.ico">
    <!-- greenforest:share-metadata:start -->
    <!-- greenforest:preview-source:none -->
    <meta property="og:site_name" content="Greenforest I/O">
    <meta property="og:image" content="https://greenforest.io/social-previews/contact.png">
    <meta property="og:image:secure_url" content="https://greenforest.io/social-previews/contact.png">
    <meta property="og:image:type" content="image/png">
    <meta property="og:image:width" content="1200">
    <meta property="og:image:height" content="630">
    <meta property="og:image:alt" content="Contact Greenforest I/O - Greenforest I/O share preview">
    <meta name="twitter:card" content="summary_large_image">
    <meta name="twitter:image" content="https://greenforest.io/social-previews/contact.png">
    <meta name="twitter:image:alt" content="Contact Greenforest I/O - Greenforest I/O share preview">
    <script src="/site-analytics.js" defer></script>
    <!-- greenforest:share-metadata:end -->
    <script type="application/ld+json">
        {
            "@context": "https://schema.org",
            "@type": "ContactPage",
            "@id": "https://greenforest.io/contact.html#webpage",
            "url": "https://greenforest.io/contact.html",
            "name": "Contact Greenforest I/O",
            "about": {
                "@type": "Organization",
                "@id": "https://greenforest.io/#organization",
                "name": "Greenforest I/O",
                "legalName": "Solid State Pros LLC",
                "url": "https://greenforest.io/",
                "sameAs": "https://www.solidstatepros.com/",
                "email": "brian@solidstatepros.com",
                "contactPoint": {
                    "@type": "ContactPoint",
                    "email": "brian@solidstatepros.com",
                    "contactType": "technical and business inquiries",
                    "areaServed": "US",
                    "availableLanguage": "English"
                }
            }
        }
    </script>
    <script src="/common-script.js" type="text/javascript"></script>
</head>

<body class="article-structured">
    <header><h1 class="page-title">Contact Brian Greenforest</h1></header>

    <section class="abstract">
        <p class="lead">Bring the system, the boundary that blocks it, and the opportunity to turn it into something valuable.</p>
        <p>Start a conversation about funded R&amp;D, product architecture, implementation, streaming FPGA arithmetic, raw WebGL and GLSL systems, Cartilage, radio, semiconductor development, fabrication access, collaboration, a principal engineering role, or technical due diligence.</p>
        <p><a href="https://www.solidstatepros.com/" target="_blank" rel="noopener">Solid State Pros LLC</a> carries Greenforest I/O engagements from the first technical exchange into professional work.</p>
    </section>

    <main>
        <section>
            <h2>Send The Real Object First</h2>
            <p>A short first message can establish everything important: name the system, the blocked outcome, and the opportunity.</p>
            <p>Attach or link the repository, circuit, shader, diagram, paper, trace, capture, measurement, board, process description, or product architecture. Name the decisive factor—timing, state, routing, physical feasibility, fabrication, cost, reliability, performance, or explanation.</p>
            <p><a class="cta-link" href="mailto:brian@solidstatepros.com?subject=Technical%20work%20inquiry%20for%20Greenforest%20I%2FO">Email a technical work inquiry</a></p>
        </section>

        <section>
            <h2>Problems That Match The Practice</h2>
            <p><strong>Streaming arithmetic:</strong> a dataflow needs a narrow, regular FPGA schedule, or the <a href="serial_multiplier/">bubbles-free serial multiplier</a> can unlock a larger architecture.</p>
            <p><strong>Browser GPU computation:</strong> a product needs direct WebGL or GLSL control over texture-backed state, framebuffer passes, readback, or a spatial computing model. <a href="webgl-glsl-computing.html">Run the browser-GPU machinery</a>.</p>
            <p><strong>Reconfigurable systems:</strong> an organization wants to develop, teach, fund, license, or house <a href="cartilage-reconfigurable-computing-roadmap.html#support">Cartilage</a> from its browser editor and simulator through RTL, physical design, and fabrication. The <a href="cartilage/">learning path</a> builds the architecture from one multiplexer upward.</p>
            <p><strong>Any hidden layer:</strong> a product, signal path, model, or process has reached the point where the abstraction underneath it now controls the engineering outcome.</p>
        </section>

        <section>
            <h2>Name The Opportunity</h2>
            <p>For business, partnership, funding, institutional, or product inquiries, include the organization, timeline, available resources, and technical territory: FPGA, semiconductor R&amp;D, AI systems, programmable matter, radio, software architecture, or another emerging technology.</p>
            <p>Name the desired outcome: an architecture, implementation, product, review, principal role, laboratory access, funding, collaboration, fabrication path, license, or introduction. Specificity turns the first exchange into useful work.</p>
        </section>

        <section>
            <h2>Contact Details</h2>
            <p><strong>Email:</strong> <a href="mailto:brian@solidstatepros.com">brian@solidstatepros.com</a></p>
            <p><strong>Legal entity:</strong> <a href="https://www.solidstatepros.com/" target="_blank" rel="noopener">Solid State Pros LLC</a></p>
        </section>
    </main>

    <nav class="article-links">
        <p>Choose a concrete starting point:</p>
        <a href="proof-and-artifacts.html">Working Systems And Source</a>
        <p>Enter through circuits, browser machines, physical radio, source, and reconfigurable architecture.</p>
        <p>Develop the largest program:</p>
        <a href="cartilage/">The Complete Cartilage Learning Path</a>
        <p>Follow the largest research program from visible logic to runtime spatial reconfiguration.</p>
        <a href="/">Explore Greenforest I/O</a>
    </nav>
</body>

</html>