blacksilvergroups
Work with us

Douala

Theme

How we build Douala, Cameroon

How a Blacksilver company is built.

Every company we start stands on the same four layers. This page says what each one is, and shows where it’s true today, with the change, the document or the number behind it.

01How to read this site

Every figure says where it came from.

LIVEtime of check
Our server fetched it, and the time of the check is shown. If a check fails, the line disappears rather than guessing.
RECORDdate
A dated fact from our own engineering records.
SPECIMENcode and inputs
Invented inputs, run through our real code.

Anything else that moves on this site is a clock, or a drawing being drawn.

02The foundation

Four layers, one name on top.

Operations, stack, standards and family come from the group. Each company adds its own name and accent.

Cross-section

The Blacksilver foundationFour shared layers, operations, stack, standards and family, with Ocheso (live) and a second company (in internal testing) built on top, and room for the next.01 OPERATIONS01 OPERATIONS02 STACK02 STACK03 STANDARDS03 STANDARDS04 FAMILY04 FAMILYNEXT
  • OchesoLive
  • Our second companyInternal testing
  • Room for the next

Layer 01: Operations

We run what we ship.

We don’t build a company and hand it to someone else to keep alive. We host it, keep it running and answer for it.

Receipts

  • The group

    RECORD21 Oct 2026

    Ocheso’s site, its API and its database are deployed and run by us.

  • Ocheso

    RECORD21 Oct 2026

    Before we called Ocheso live, we walked through it on the live system with two real accounts: create, publish, a wrong entry code refused, approval, play.

Layer 02: Stack

Widely used tools, placed carefully.

We choose well-known tools and spend our care on where things run and what they depend on.

Where our code runs
PartRuns onRegion
This siteStatic pages on Vercelnone listed
Ocheso’s siteNext.js on Vercelnone listed
Ocheso’s APIPython on Vercel, as two functions on one domainDublin
Ocheso’s database and live gamesSupabase Postgres and RealtimeIreland
Our second company’s dashboardVercel, behind a sign-innone listed
Its collectorsA worker on RenderFrankfurt
Its databaseSupabase PostgresFrankfurt

In both companies, the code sits in the same region as its database.

RECORD22 Oct 2026

Layer 03: Standards

Six written standards, each with a receipt.

The same six rules apply in every company we start. Each one below links to where it is true today.

  1. BSG/S1

    The database decides.

    Permissions live in the database as rules, not scattered through application code. A bug in a route can make a request fail; it can’t let a stranger change your data.

    Serves: Trust is the product.

    • Ocheso

      RECORD21 Oct 2026

      Every request to Ocheso’s API runs as the person who made it, and the database’s row-level rules answer. The API holds no key that bypasses them, and refuses to start if one is configured. 87 checks, run as each role, prove the rules.

    • Our second company

      RECORD10 Aug 2026

      Every table in our second company’s database has row-level security on and no public access, and new tables get the same automatically.

  2. BSG/S2

    Code runs beside its data.

    An application runs in the same region as the database it talks to.

    Serves: We answer for what we ship.

    • Ocheso

      RECORD22 Oct 2026

      Ocheso’s API moved from Washington to Dublin, next to its database in Ireland. An agent’s move went from 1.1–1.7 s to 0.5–0.7 s, end to end.

      In the journal:The Atlantic was most of our latency

    • Our second company

      RECORD10 Aug 2026

      Our second company’s database was placed in Frankfurt to sit beside the worker that writes to it.

  3. BSG/S3

    A rewrite must make the same decisions.

    When we port or replace a component, we replay what the old one did and require identical answers before it ships.

    Serves: Correctness is non-negotiable.

    • Ocheso

      RECORD22 Oct 2026

      Ocheso’s agent brain, ported from TypeScript to Python: 8,048 recorded decisions replayed, every one identical.

    • Ocheso

      RECORD22 Oct 2026

      Maia’s network rewritten on numpy: the same top move in 270 of 270 test positions, and 4,800 of 4,800 sampled decisions identical.

      In the journal:The Atlantic was most of our latency

  4. BSG/S4

    Ship what a request depends on.

    Anything a request needs travels with the deployment, pinned to the version we tested. Nothing downloads while someone waits.

    Serves: We answer for what we ship.

    • Ocheso

      RECORD22 Oct 2026

      The official Stockfish 19 release ships inside Ocheso’s API, held to a fixed SHA-256 checksum. It made the same 960 of 960 sampled decisions as the engine our agents were calibrated on.

  5. BSG/S5

    A number is checked before it counts.

    Data that arrives looking fine is still checked: plausible ranges, declared units, and empty answers treated as faults.

    Serves: Transparency over black boxes.

    • Our second company

      RECORD9 Aug 2026

      Our second company treats a price under 100 XAF as no price, reads each shop’s declared currency unit instead of assuming one, and reports an empty page as a fault, not as an empty market.

    • Ocheso

      RECORD21 Oct 2026

      Ocheso’s API refuses a request that tries to set a field it may not set, such as an owner, a status or a rating, with an error naming the field, rather than quietly ignoring it.

  6. BSG/S6

    Say what the software isn’t, yet.

    If software falls short of a standard, it says so where people will read it.

    Serves: Correctness is non-negotiable.

    • Ocheso

      RECORD21 Oct 2026

      The first paragraph of Ocheso’s Swiss pairing code says it is not a certified FIDE Dutch implementation, then explains what it does instead.

    • Ocheso

      RECORD21 Oct 2026

      Ocheso’s health check says the process is up, and deliberately doesn’t claim the database is.

    • Our second company

      RECORD9 Aug 2026

      Our second company’s dashboard says that only one of its sources covers all three cities, rather than implying coverage it doesn’t have.

Layer 04: Family

Its own name, with ours beneath it.

Every company leads with its own name, its own mark and its own accent colour, on the shared obsidian and silver. Blacksilver sits underneath, smaller.

Receipts

  • Ocheso

    RECORD21 Oct 2026

    Ocheso’s site carries ‘a Blacksilver company’ and links back here.

The endorsement

Naming rules

  1. Coined, one word, ownable.

  2. On-theme, never on-the-nose.

  3. Room to grow: never named for one commodity or one city.

  4. Four checks before it’s adopted: trademark; domain and handles; meaning in the languages of its market; no confusion with another of ours.

  5. “Blacksilver” never appears in a company’s name.

How a company joins the group

  1. Brief. Who it’s for, what it replaces, and whether it may grow beyond its first market.

  2. Name. A coined word that clears four checks: trademark; domain and handles; meaning in the languages of its market; no confusion with another of ours.

  3. Lockup. Its wordmark, and the three approved ways to set it with ours.

  4. Endorse. “a Blacksilver company” on its site, in its product and in its legal footer.

  5. Cross-link. It’s listed here, and its footer links back.

How we name a company

03What we won’t build

What we won’t build.

No company in the group is built on wagering or chance, named for it, or described in its language. It would undercut the trust our companies depend on.