PILOT - CLOSED - INVITATION ONLYBobby Guru is operating as a limited closed pilot. Features, availability and commercial terms may change before general release.

$ governance --profile --protocol 1.0.0

Site governance

Bobby.guru is governed by the same network site-governance standard we apply to every site we operate, and that Bobby applies to yours. This page is the document of record for this site. Unknown is a valid, visible value - it produces a question, not a guess.

Site profile

fieldvaluesourcelast verifiedconfidence
operator legal entityunknownowner - none
registration detailsunknownowner - none
primary domainbobbyguru.comowner2026-08-22high
brandBobby.guru - late-night terminalbrand book2026-08-22high
business modelsubscription membership + Guru Creditsowner2026-08-22high
payment modelStripe, EUR, monthlyowner2026-08-22medium
marketplace roledirect service providerowner2026-08-22high
target marketsEU, UK, USowner2026-08-22medium
jurisdiction / governing lawNetherlands (proposed)owner - low
dispute routeunknowncounsel - none
data-protection rolecontroller for accounts, processor for submitted contextdraft - low
sub-processorsunknown - to be registered before productionowner - none
languagesensite2026-08-22high
timezoneEurope/Amsterdamowner2026-08-22high
analytics propertyunknownowner - none
search propertyunknownowner - none
age policy18+ commercial buyersowner2026-08-22medium
release policyno release without approved readiness reportstandard2026-08-22high

Environment & release blockers

This project is a sandbox: it changes daily, is not a released production system, and must stay noindex on any non-production domain. Git is not connected by deliberate owner decision. That does not block sandbox work; it is a critical blocker before the production remix, the production genesis and any real release.

environment                            = sandbox
git_connected                          = false
git_connection_status                  = deferred_by_owner
git_required_for_current_sandbox_work  = false
git_required_before_production_remix   = true
git_required_before_production_genesis = true
git_required_before_real_release       = true
release_blocker                        = critical
blocker_activation_stage               = production_remix_preparation
payments_enabled                       = false
public_registrations_enabled           = false
mcp_endpoint_live                      = false

Model of record

Two stages

Stage A, release readiness, is human-driven: discover capabilities, ask structured questions, raise findings, produce a signed readiness report. Stage B, nightly monitoring, is read-only drift and regression detection. Neither writes site state.

Protocol vs adapter

A reusable protocol layer holds types, capability negotiation, findings, proposals and evidence. Site-specific adapters implement them and must pass one shared contract test suite. No protocol file may import an adapter.

Least privilege

Governance tables live in a private schema the data API cannot reach, with forced row-level security and append-only evidence. Corrections are new rows referencing the superseded one - never updates, never deletes.

Separated identity

One permanent service-agent account per platform, created only by an owner-confirmed action. It never shares a human session and never uses a service-role key. A principal-kind mismatch is a hard rejection plus a security finding.

Roles are not permissions

Roles live in their own table behind a security-definer check. The developer role is operational, not a security boundary: every governance write additionally requires a specific permission, a typed proposal and an exact hash match.

Approval by a second human

Proposals are typed and domain-scoped. Approval requires the matching permission class and a different human. Anything touching published legal text also requires counsel evidence bound to the exact document hash.

Permission classes

governance.read · governance.questions · governance.propose · governance.approve · governance.execute · governance.legal · governance.privacy · governance.security · governance.finance · governance.analytics · governance.release · governance.agent_admin · governance.fixtures