cratis-chronicle-multi-tenancy SKILL.md skillA
cratis-chronicle-multi-tenancy from cratis/ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cratis/ai/cratis-chronicle-multi-tenancy@git:20261014.91916f1Pins git:20261014.91916f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cratis/ai
- Path
.cratis/ai/skills/cratis-chronicle-multi-tenancy/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.91916f1, committed Oct 14, 2026
- First version recorded
- Oct 12, 2026
- Size
- 10,061 bytes
- Repository stars
- 4
- License
- MIT
Isolate tenants in Chronicle with namespaces - what a namespace actually isolates, how a namespace is selected and resolved through IEventStoreNamespaceResolver, how namespaces come into existence, and the code rules that let a single-tenant deployment grow a second tenant. Use when setting up tenancy, when writing code that touches events or data on behalf of a tenant, or when adding a second tenant. Do not use for authentication, authorization, or identity-provider setup.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Multi-tenancy with Chronicle namespaces Chronicle implements multi-tenancy through **namespaces**. A namespace is a logically separate store: its events, observers, and read models run independently, and there is no cross-namespace leakage. **Assume every application is multi-tenant.** A deployment serving one organization today is a multi-tenant application with one tenant in it. The second tenant arrives later, and code written as if there would only ever be one is discovered from the far side of a data migration. Whether a deployment *configures* tenant resolution is an operational choice; whether the code survives a second tenant is not. ## Verified product sources Sources: | Package | Purpose | | --- | --- | | `Cratis.Chronicle` | `EventStoreNamespaceName`, `IEventStoreNamespaceResolver`, `IChronicleClient.GetEventStore` | | `Cratis.Chronicle.AspNetCore` | the header and subdomain namespace resolvers | Reverify product sources before claiming support for another version. ## The concept | Term | Meaning | | --- | --- | | Namespace | a named isolation boundary within an event store | …
Read the whole file at its exact version.
How to install
mdr add cratis/ai/cratis-chronicle-multi-tenancy@sha256:ffa0d4b288a88f72The line at the top of this page pins the label git:20261014.91916f1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7cvvx6qky7a5anrr)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 12, 2026 and Oct 14, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.91916f1 latest | 2026-10-14 | 91916f1 | 10,061 B | A | view · diff |
| git:20261013.bfe50df | 2026-10-13 | bfe50df | 9,808 B | A | view · diff |
| git:20261013.9c1bacb | 2026-10-13 | 9c1bacb | 9,812 B | A | view · diff |
| git:20261012.9e91c1e | 2026-10-12 | 9e91c1e | 9,930 B | A | view · diff |
| git:20261012.4f7115e | 2026-10-12 | 4f7115e | 9,615 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 (10061 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
cratis/ai · 4 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7cvvx6qky7a5anrr GET https://markdownregistry.com/api/v1/resolve?ref=cratis/ai/cratis-chronicle-multi-tenancy GET https://markdownregistry.com/api/v1/blob/ffa0d4b288a88f7220104dd610c92f384667e7125cf846ae78cf9884778b8267
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.