# BuilderSpace BuilderSpace — Midwest Builder Tour: hackathons, build weekends, pitch nights and speaker spaces, with free training resources for new founders. San Francisco startup teams travel to Louisiana and Nebraska to train alongside local builders and help local economies in areas seeing new data centres and jobs. Status, stated plainly: **everything here is PLANNED.** All 16 events are currently Private/unlisted on Luma, no invites have been sent, and **no venue, sponsor, speaker, or partner is confirmed**. Locations for in-person events are TBD unless marked Online. This file will never list a venue or sponsor that hasn't signed. - Site: https://builderspace.tech/ (GitHub Pages) - Contact (humans and agents): events@builderspace.tech - Sponsorship inquiries: sponsors@builderspace.tech (alias of the same mailbox) - Human steward: Mike Rice. Registration for agents is email-based and human-gated — see /auth.md. ## Events Onboarding nights — five free online sessions, Thursdays 6:00–7:30pm Central: - Fri Dec 4, 2026 — Welcome to the Tour (Online) - Thu Nov 19, 2026 — Community Night: Meet SF + Midwest Builders (Online) - Thu Dec 3, 2026 — Build Night: Ship Your First Project (Online) - Thu Dec 10, 2026 — Info Night: Sponsors, Training & Incubators (Online) - Thu Dec 17, 2026 — Pre-Season Prep: Get Ready for January (Online) The 2027 tour — eleven planned events, Central time, locations TBD: - Jan 8, 2027 — Season Opening Kickoff - Jan 9–11, 2027 — Bayou AI Build Weekend (multi-day hackathon) - Feb 11, 2027 — Crescent City Founder Toolkit - Feb 17, 2027 — Nights & Weekends: NOLA Builder Night - Feb 18, 2027 — Heartland Builders & Coffee - Mar 5–7, 2027 — Cajun Code Sprint (multi-day hackathon) — Luma: https://luma.com/x4fbwvvb - Mar 26–28, 2027 — Prairie AgTech Build Weekend (multi-day build weekend) - Apr 8, 2027 — Nights & Weekends: Prairie Builder Night — Luma: https://luma.com/ygc1jzq0 - Apr 15, 2027 — Red River Pitch Night - Apr 22, 2027 — BuildFest Skills & Certs Day - May 1, 2027 — Grand Finale (season closing) Only the two Luma links above are on file; the other 14 events have no public link yet. Final details are confirmed on Luma as they land. ## The roadmap - Phase 0 (Nov 19 – Dec 17, 2026) — Onboarding, online: form the community before anyone travels. - Phase 1 (Jan 8 – Mar 7, 2027) — Louisiana: New Orleans (Kickoff, Bayou AI Build Weekend, Founder Toolkit, NOLA Builder Night) and Lafayette (Cajun Code Sprint). Heartland Builders & Coffee (Feb 18) is grouped in this leg; its city is not yet named in the plan. - Phase 2 (Mar 26 – Apr 15, 2027) — Nebraska: Omaha and Lincoln are the plan's anchor cities; individual Nebraska event cities are not yet assigned in the records. - Phase 3 (Apr 22 – May 1, 2027) — Certify & close: Skills & Certs Day, then the Grand Finale. "What success looks like" on the site is the plan's aspiration, framed as goals — never as commitments or confirmed partners. ## Founder training & resources The tour's second job is training new founders. On the site: - "How to Get Credits for Startup Founders" — a nine-guide series on stacking startup credits honestly (the map, cloud, infra/dev tools, AI credits, business tools, the nonprofit track, rejections, redeeming & tracking). Amounts are "up to" maximums; confirm terms with each provider the day you apply. The guides are being published as resource pages by the AGI Future Foundation; links on the site are placeholders until that push lands. - A startup credits & programs catalogue, a credits audit of real application outcomes, and an application prep library — all grounded in real applications, approvals, and rejections. ## Sponsorship The tour is seeking sponsors — cash and/or product credits. In return the tour team works as the sponsor's brand ambassadors and developer-relations crew on the road: workshops and demos on the sponsor's tools, the sponsor's stack in the curriculum, hackathon tracks and judging, tour content, and first access to the builders being trained. All sponsorship numbers are proposed and negotiable; **no amounts are published here because none are set** — tier amounts on file are blank placeholders the steward fills. Nothing is promised, and no sponsor is named until they've signed. Inquiries: sponsors@builderspace.tech. Sponsors can also post offers for builders on the Sponsor Offers board: https://builderspace.tech/offers.html — posting is free; every offer is reviewed by a human before it is listed, and offers are listed in the sponsor's own words. ## Discovery files Machine-readable files for agents on this site: - /agents.json — catalogue of what is offered to agents and humans, with contacts. - /agent.json — the steward protocol in structured form. - /auth.md — agent registration (email-based, human-gated; no token, no OAuth/OIDC). - /.well-known/ai-catalog.json — agent resource discovery manifest. - /.well-known/api-catalog — resource/discovery linkset (this site has no API; the linkset lists real documents only). - /sitemap.xml — every page (currently one page). No OpenAPI spec, no status/health endpoint, no MCP server, and no OAuth/OIDC discovery documents exist for this site. Markdown content negotiation (Accept: text/markdown) is planned via a Cloudflare Worker once the domain is proxied — until then, this file is the Markdown homepage. ## Agent rules Agents may summarize, cite, and route inquiries to a human steward. Agents may NOT commit BuilderSpace or the steward, move funds, sign, book, or represent themselves as BuilderSpace. Sponsorship, venue, and speaker agreements are made by humans, in writing, only. Every first step is steward-gated: write to events@builderspace.tech with a subject starting [Agent], naming your operator and human principal. ## Agent layer (standard v2026-11-13.1) — appended 2026-11-13 Appended under the network agent-friendly standard (AGENT-FRIENDLY-STANDARD.md), merge approved by Mike 2026-11-13. Everything above this section is the site's original file, unchanged; the sections below are additions only. ## House law (summary) The full house law is embedded as the `houseLaw` block in this site's /agent.json; every interacting agent is expected to read and follow it. Summary: - Caps bind the account, never the device or the agent count: email 90/day per mailbox and ≤250 cold/day across the programme; social pacing — one platform at a time, ~2 minutes between same-platform actions, ≤3 posts/account/day, ≤25 actions/platform/day network-wide; first platform warning = full stop on that platform that day. - Draft-first, exact-copy approval: no agent sends, posts, publishes, or submits anything outward without Mike's approval of the exact version. Nightshift work additionally requires Bino's approval. - Suppression is law: suppressed contacts are locked out of every queue on every surface; suppression is checked before any queue is built and again before any draft. An agent that cannot check suppression does not send — it hands off. - Published contacts only: outreach uses published institutional contacts. Pattern/inferred emails are never mailable. The filings graph is never a contact source. - Human handoff: anyone who asks for a human, or opens a price/scope conversation beyond published registry prices, leaves the automated thread the same day and is flagged to the human (Mike; Russell Vacanti on Foundation matters; a Fellowship steward on Fellowship matters). Agents state published prices; they never quote custom terms, discounts, or timelines. - Evidence labels: claims are labelled VERIFIED / REPORTED / HYPOTHESIS. Filed fact and intended plan are never blended; a nonprofit's tax status is stated only as: California nonprofit corporation, EIN assigned, no IRS determination letter on file. - Holding separation: holdings keep separate lanes, contacts, and claims. Cross-holding work splits into one Agent-Net packet per holding. Fellowship surfaces carry no commerce, ever. - Agents never sign, move funds, hire/fire, offer securities, enact doctrine or charters, or complete payment/KYC/signature steps. Humans execute; agents prepare. ## Affordances on this site (from /agent.json) - discover — LIVE - quote — LIVE — route: PRICES.json (registry entry ids named in this manifest) - cite — LIVE - request-human — LIVE — route: mailto:x@agifuturefoundation.org - register-honour-code — LIVE — route: mailto:x@agifuturefoundation.org (subject: CODE: — ) - join-waitlist — LIVE — route: mailto:x@agifuturefoundation.org (subject: WAITLIST: ) - purchase — LIVE — route: The PayPal route recorded in the PRICES.json entry — gate: Only registry entries whose state is LIVE or LIVE-WITH-DEFECT, one entry at a time, route verbatim from the registry. Every other entry returns its state and gate instead. - book-discovery-call — GATED — gate: The Session 01 Booking / CTO links are created at the PayPal sitting (Mike's sign-in). The paid Session 01 line also carries an open naming conflict (the live Dec 4 Session 01 is a free tour night) recorded in PRICES.json. ## Prices - Prices registry: /prices.json on this site — the network PRICES.json registry. Every price resolves from it; quote nothing that is not in it.