b3os-verification skillA
b3os-verification is agent-read markdown (skill) from b3rys/b3rys-team-os: b3rys method for proving that a change or a release is correct — and for making that proof hold and get stronger over time. Use when verifying a fix, a feature, or a release candidate; when deciding what to test headless vs in the running app; when a check fails and you must tell a wrong check from a real defect; or when setting up a one-command release check. Covers the 3 principles, the 5 ratchets, a layer + rubric table with numeric pass lines, a triage table for wrong checks, shared-resource.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# b3rys Verification — Prove It, and Keep It Proven Where this sits among the team skills: | Skill | Question it answers | |---|---| | `b3os-ai-code-safety` | How do we build it? (structure, refactoring) | | `b3os-project-mgmt` | How do we manage and report it? | | `b3os-harness-playbook` | How do we split it across parallel agents? | | **`b3os-verification`** | **How do we prove the result is right — now and on every later change?** | The core idea: a check you set up once must keep protecting you. A new feature or a bug fix ends with **one row in the feature table + a test + a deliberately broken version that the test catches**. The runner does the rest, every time. Passing the runner is evidence for review and approval (TEAM-OS §4), not a substitute for them. **Scope:** §1–5 apply to every change. §6–7 (one app window, the app runner) apply to products with a running app; for server or script work, skip them. --- ## 1. Three principles 1. **Run it; don't read it.** A diagnosis from reading source is a *candidate*. It is not a conclusion until a repro or a measurement confirms it. …
Read the whole file at its exact version.
How to install
mdr add b3rys/b3rys-team-os/b3os-verification@git:20260924.2302b08mdr add b3rys/b3rys-team-os/b3os-verification@sha256:279799f7fa301ae0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_5mze4u6tbtwu77yi)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.2302b08 latest | 2026-09-24 | 2302b08 | 11,570 B | A | view · diff |
| git:20260924.19836be | 2026-09-24 | 19836be | 12,511 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11570 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
b3rys/b3rys-team-os · 14 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5mze4u6tbtwu77yi GET https://markdownregistry.com/api/v1/resolve?ref=b3rys/b3rys-team-os/b3os-verification GET https://markdownregistry.com/api/v1/blob/279799f7fa301ae09b730922cdb98f9b66698397698233fea21fc6be20de7daf
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.