Trust proof
A source is useful when it records channel, context, intent, source detail, owner, and next action.
Source attribution turns attention into accountable routing.
The source ledger shell prepares the path for tracking how people found BearSchiele, why they reached out, and where they should go next.
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
Referral source
Capture who or what created the opportunity and whether follow-up attribution is needed.
Content source
Track book, talk, video, post, podcast, or search source tied to the inquiry.
Handoff source
Record whether the opportunity should remain BearSchiele-led or route to a brand lane.
Receipt targets
- source captured
- attribution note
- route decision
- follow-up proof
Genesis AI rails
- Command Center source ledger
- AI Brain source summary
- Voice intake context
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.