Fair-pricing commitment
Every tier is published in human-readable HTML at /smb/pricing/ and machine-readable JSON at /smb/pricing/rates.json. No hidden markup for any market. No customer-by-customer deal-desk negotiation for the productised floor and cohort tiers. Retainer tier allows scope customisation, but the base rate follows the same PPP x scale formula.
Enforcement: rates.json is the source of truth. Any locale page showing different prices is a bug and must be fixed within 48 hours.
Equity-tier access
A 40 percent discount stacks on any tier for eligible operators. Self-declaration on application, verified once by the hub lead, renewable every 12 months. Eligibility covers: underrepresented founders, women-first leadership teams, registered social enterprises or non-profits, student-led ventures under 24 months old, and operators in conflict-affected or post-conflict regions.
Minimum allocation: 25 percent of cohort slots per intake reserved for equity-tier applicants. If allocation is undersubscribed, unused slots roll to the next intake, they do not convert to standard-tier slots.
Data residency per market
SMB operational data sits in the region of the hub. EU customers: Frankfurt (Hetzner) or Copenhagen (Fly.io CPH) at customer choice. UK customers: London (Fly.io LHR). Morocco customers: Paris (Fly.io CDG, closest EU point; MA data sovereignty law not yet enforced in our stack, flagged for review). Ghana customers: Johannesburg (Fly.io JNB) or London (Fly.io LHR) at customer choice.
Reviewed against Morocco Law 09-08 and Ghana Data Protection Act 2012 quarterly. Customers can request a region swap; executed within 30 days.
Runtime audit trail
Every ElektraOS agent execution on behalf of an SMB is logged with: agent name, input hash, output hash, model, latency, timestamp. Customers can request a full audit export at any time, no cost, delivered within 72 hours. Logs retained for 24 months, then hashed and archived.
No agent-generated content is published on customer-owned channels without human approval for cohort and retainer tiers. Floor tier allows opt-in auto-publish for specific content types; off by default.
Cross-link consent (Loomgraph)
Membership in Loomgraph Society does not grant automatic cross-linking. Every cross-link proposal requires: a shared entity in the knowledge graph OR a 1-hop entity relation, AND explicit approval from the receiving site's operator. Rejected proposals remain rejected until the operator reverses the decision.
Enforcement: /api/approvals endpoint on loomgraph.fly.dev, publicly auditable.
Hub lead compact
Local hub leads keep 70 percent of gross local revenue. The remaining 30 percent funds the shared runtime, the equity pool (which subsidises the 40 percent equity discount), and compliance review. Hub leads are independent operators, not employees. They carry a 12-month minimum commitment and can exit on 90 days' notice.
Revenue split reviewed annually. Any change requires 6 months' notice to existing hub leads.
Exit and data portability
Any SMB can exit on 30 days' notice (floor, cohort) or 90 days' notice (retainer). On exit we deliver: full data export (S3 bucket or local download, customer choice), all agent configurations in portable JSON, all Loomgraph registry entries removed within 7 days. No lock-in on domains, content, or operational data.
Cohort tier exits before the 12-month term require a pro-rata buy-out of the remaining months; this is the only exit fee anywhere in the stack.
B Corp certification path
We have started certification prep under the 7th edition standards (published April 2026, 683 pages, first major overhaul since 2007). Target submission: Q2 2027. Certifying entity: a Netherlands stichting (foundation) as the global coordinator, with regional affiliates in UK, Denmark, Morocco, Ghana. Equity-pricing policy already aligns with B Lab's 40 percent equity-pricing mechanism.
Prep document maintained at /vault/governance/bcorp_prep.md (internal). Public progress log on /log/.
Amendment and transparency
This pact is versioned. v1 effective 2026-04-24. Changes are published with a visible diff, a "what changed" summary, and the date. Breaking changes (anything that reduces a customer's rights or increases their price by more than PPP-adjusted inflation) require 90 days' notice.
Full diff history at /smb/governance/history/ (to be published from v2 onward). Feedback: yossra.benzad@gmail.com.