Zephr

32 MCP tools · 11 platform surfaces · shared registry

Engineering

Evidence, not marketing.

Every article on this page links to its source evidence — an ADR, a test run, or a design decision. No fabricated scores. No invented certifications. No AI slop.

evidence-backed·source-linked·no fabricated claims
What we write about

Three subjects, and a rule about all of them.

The rule is that a post has to be adapted from something already in the repository — an architecture decision record, a test run, a design document. That constraint is what keeps the writing narrow, and it is why there are five posts here rather than fifty. If a claim in one of them sounds surprising, the source link at the bottom of the post is the place to check it rather than take our word.

  • Engineering

    2 posts

    How the store is built: the bi-temporal model, and the test suite that gates it.

  • Trust

    2 posts

    What the system refuses to do — abstain rather than guess, and bind a scope it cannot later widen.

  • Continuity

    1 post

    Moving a session between tools without losing the record of how it got there.

Illustrative example — not live data

Articles

Writing about what we actually shipped.

Each post is adapted from a source document in the repo. If a claim sounds surprising, the source link at the bottom of the post is the place to check.

Read the security model.

git clone https://github.com/DigitalSoftDistribution/zephr.git

The documentation covers the architecture, tool contract, TrustBench methodology, and trust model in detail. Every claim links to its source.