The hub gathers how secrets, identity, and compliance are handled. The spine is credential hygiene: the [target credential-vault design] (Narrative_CredentialVault) removes rewrite.clj injection so [credentials never ride the MCP body] (Claim_CredentialsNeverInMCPBody) and are fetched from an internal-only Datomic-backed API, with the [internal endpoint reachable only on the Docker network] (Obs_InternalCredentialEndpoint), not exposed through Caddy. Operationally this was exercised by the [stale-credential cleanup in dev n8n] (Claim_CredentialCleanup) on 26 Mar. Compliance is the commercial frame: [GDPR/sovereignty/ISO act as adoption gates] (Narrative_EnterpriseComplianceGate), [local non-internet AI satisfies HIPAA and VIP privacy] (Narrative_LocalAI), and [client data-ownership] (Narrative_DataOwnership) (licensed base ontology, work-for-hire deliverables, repo under client org) removes lock-in. Two strands remain unsettled: the [BYOK OpenRouter-only limit] (Narrative_BYOKOpenRouterLimit) (Mar 17) and the [Vouch.io agent-identity bet] (Narrative_VouchIdentityForAgents).
Witness phrases
verbatim Credentials must never travel through the MCP message body; they are fetched by n8n from an internal-only Datomic-backed API.
verbatim Internal credential endpoint only reachable on Docker network, not exposed through Caddy — key security boundary.
verbatim Target design removes rewrite.clj credential injection; n8n calls back to an internal-only endpoint for secrets, enabling instant rotation and true multi-tenancy.
verbatim Current BYOK (bring your own key) only accepts OpenRouter API keys.
verbatim Local, non-internet-connected AI infrastructure is required for HIPAA compliance and VIP client privacy
verbatim Base ontology framework is licensed, not sold.
verbatim BYOK accepts only OpenRouter keys; Azure/Copilot enterprise customers can't plug in, routing compliance buyers to on-prem/Professional rather than BYOK — a known unresolved gap.
verbatim Vouch.io agent-identity infrastructure is validated tech but strategically undecided: open-source it as a standard, or sell as an enterprise product.
verbatim Ownership is split, not clean: deliverables and custom ontology are client-owned work-for-hire, but the base ontology framework is licensed (not sold) — a retained-vendor-IP boundary inside a no-lock-in pitch.
verbatim Credential security is partly aspirational vs shipped: the vault design (remove rewrite.clj injection, instant rotation, true multi-tenancy) is a target, while the dev cleanup is the realized state.
In this area
NarrativeNarrative_BYOKOpenRouterLimit BYOK Limitation: OpenRouter Only, Azure/Copilot Gap
NarrativeNarrative_DataOwnership Client owns memories, transactions, custom ontology extensions; base ontology licensed; repo under client org from day one
NarrativeNarrative_EnterpriseComplianceGate Enterprise compliance as adoption gate
NarrativeNarrative_VouchIdentityForAgents Vouch.io Identity Infrastructure for Agent Security
5 further nodes are not published in the public projection. Each node links from the entity index.