Trust proof
A speaking opportunity is real when audience, topic, date, budget, source, fit, and next action are captured.
Speaking requests should become clear opportunities, not scattered messages.
The speaking route prepares event, keynote, workshop, panel, and leadership-room inquiries for governed qualification and follow-up.
WordPress role
Home, landing, trust, SEO, and public discovery-call entry remain on WordPress until an approved cutover.
GitHub app role
This app owns the body: speaking, media, source context, trust proof, handoff posture, and Command Center sync.
Founder trust body
What this surface now controls
Keynotes and leadership rooms
For events that need practical leadership, accountability, veteran-informed execution, and founder perspective.
Panels and interviews
For conversations around leadership, AI-enabled operations, Black founder trust, veteran leadership, and ecosystem building.
Follow-up proof
Every speaking inquiry should capture source, audience, topic, date, owner, and next step.
Receipt targets
- speaking inquiry
- event fit review
- topic alignment
- follow-up assignment
Genesis AI rails
- Voice speaking intake
- AI Brain opportunity summary
- Command Center event pipeline
Next build gate
Move from public founder-trust body to app-owned intake: validation, sanitized client response, server logs, receipt payload, and durable Command Center proof.