$ governance --profile --protocol 1.0.0Site 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
| field | value | source | last verified | confidence |
|---|
| operator legal entity | unknown | owner | - | none |
| registration details | unknown | owner | - | none |
| primary domain | bobbyguru.com | owner | 2026-08-22 | high |
| brand | Bobby.guru - late-night terminal | brand book | 2026-08-22 | high |
| business model | subscription membership + Guru Credits | owner | 2026-08-22 | high |
| payment model | Stripe, EUR, monthly | owner | 2026-08-22 | medium |
| marketplace role | direct service provider | owner | 2026-08-22 | high |
| target markets | EU, UK, US | owner | 2026-08-22 | medium |
| jurisdiction / governing law | Netherlands (proposed) | owner | - | low |
| dispute route | unknown | counsel | - | none |
| data-protection role | controller for accounts, processor for submitted context | draft | - | low |
| sub-processors | unknown - to be registered before production | owner | - | none |
| languages | en | site | 2026-08-22 | high |
| timezone | Europe/Amsterdam | owner | 2026-08-22 | high |
| analytics property | unknown | owner | - | none |
| search property | unknown | owner | - | none |
| age policy | 18+ commercial buyers | owner | 2026-08-22 | medium |
| release policy | no release without approved readiness report | standard | 2026-08-22 | high |
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