kotobase
Menu

Kotobase engineering blog

Technical details, legal documents and some account steps still dey for English.

Technical decisions, experiments wey you fit repeat, guides to join systems, and release evidence—no be ordinary graph-database SEO.

Latest

Why an Obsidian graph no suppose own your Markdown

Local-first design wey safe for conflict two-way sync, queryable [[wikilinks]], and CID-reproducible AI context.

See how Obsidian workflow dey go · Read di implementation guide (e open for GitHub)

One graph for tenant, plenty query protocols

How Cypher, Gremlin, GraphQL, SPARQL, and Datomic queries dey share identity, capability discovery, and audit boundaries.

Read di protocol evidence (e open for GitHub)

Signed Worker only get value if you deploy those exact bytes

Clean rebuild dem, check say generated-source no change, SBOM/SLSA attestations, plus exact-artifact deployment.

Read di supply-chain guide (e open for GitHub)

Enterprise readiness wey no be just compliance waka

Living gap register wey separate implemented controls, contractual commitments, and work wey still need independent evidence.

Read di current register (e open for GitHub)

Editorial contract

Every post must link to runnable code, ADR, measured evidence, or clearly labeled proposal. Marketing claims no go turn to facts just because dem show here.