MNSTRY.ai · Documentation · Research and writing
MNSTRY builds consent-native technology for practitioner-led transformation. Sessions, programs, spaces, and companions carry the work between moments of human contact while keeping privacy, consent, and exit inside the design.
The public work begins one layer lower. We open the local tools, contracts, and verification that keep important bodies of work readable, portable, and under their stewards' control.
Not everything MNSTRY builds is open source. Everything listed below is.
Local governance toolkit for file-based bodies of work. Front-matter ontology, deterministic knowledge graph, fail-closed boundaries, offline conformance.
JavaScript · Apache-2.0 · v0.2.0-alpha.6 · Updated 6 Nov 2026
Repository · Documentation · Issues
local-first knowledge-graph governance ontology authoring validation
npm install --save-dev @mnstry/atelier@0.2.0-alpha.6Your files stay yours. Source remains readable in ordinary files and versioned in Git.
Rules can refuse. A boundary is only meaningful when invalid or over-broad states fail instead of passing quietly.
Exit is part of the product. Public contracts, offline checks, and a permissive license keep continuation possible without a MNSTRY account or service.
Each repository states its own contribution, disclosure, and security posture. Read those boundaries before opening a pull request. Issues and careful questions are always a good place to begin.
You can leave. That's why you can stay.
The repository catalogue is rebuilt daily from the public GitHub API. New public MNSTRY repositories appear automatically. Private repositories are never queried or named.