@mnstry/atelier 0.2.0-alpha.1

package/README.md

@@ -0,0 +1,262 @@
+# MNSTRY Atelier
+
+A methodology that creates real transformation cannot scale through static
+content, generic AI, or manual labor. The Atelier is a local-first toolkit for
+authoring that body of work as structured documents machines can validate —
+in plain files, on your machine, under your control.
+
+It is built for methodology holders and the studios that serve them: you
+author primitives, sources, and offers in your own repositories; the Atelier
+builds a knowledge graph over them, projects a local review surface, checks
+readiness against published protocols, and validates exports against public
+contracts. The MNSTRY runtime remains the authority for identity, consent,
+visibility, provisioning, bookings, commerce, sessions, audit, and
+client-grade sharing — using it is optional, and everything here works
+without it.
+
+## Status
+
+- Version: `0.2.0-alpha.1`
+- Stability: alpha — contracts are under a compatibility gate from the
+  `v0.2.0-alpha.0` epoch tag onward; everything else may still move
+- Runtime: Node.js `>=22.18.0 <23`
+- Dependencies: ajv, ajv-formats (JSON Schema validation); nothing else at
+  runtime
+- Distribution: `@mnstry/atelier@0.2.0-alpha.1` on npm, published from the
+  `v0.2.0-alpha.1` tag. The older `v0.2.0-alpha.0` tag is the contract
+  epoch marker, not an install target — it predates the current tree.
+- Telemetry: none. Network egress: none, with one documented exception —
+  see "Nothing leaves your machine" below.
+
+## Claims you can check
+
+This package makes three promises. None of them asks for your trust — each
+one names the command that proves it.
+
+**Nothing leaves your machine, with one exception you can see.** There is no
+telemetry, no update check, no crash reporting, and no send path anywhere in
+the package. The exception: when no actor is configured, `boundary check` and
+`doctor` fall back to the `gh` CLI to resolve your GitHub login, which is an
+authenticated request to GitHub made with your own credentials. Set
+`MNSTRY_ATELIER_ACTOR` and that path is never taken. The only network client
+refuses non-loopback URLs, the served pages carry a policy that authorizes no
+external origin, and a fail-closed gate scans the executable and markup files
+under `src/`, `bin/`, `scripts/`, and `examples/` for egress primitives. Two
+limits worth stating plainly: the gate does not read the `.json` and `.md`
+files under `templates/` and `skills/`, and it does not model
+`child_process`, which is why the `gh` fallback above does not trip it:
+
+```bash
+npm run egress:check
+```
+
+**Compatibility is checked by machinery, not memory.** Documents valid
+against the `v0.2.0-alpha.0` contracts stay valid: every change is checked
+against the baseline tag's validators, and schema widening outside `ext`
+containers is refused by a schema-vs-schema differ. Breaking changes require
+a new contract version and a recorded migration. Known limit: the differ
+compares schemas structurally and does not resolve `$ref` pointers, so a
+`$ref` retargeted at a looser definition is not caught by this gate — the
+fixture tests catch that for contracts with negative fixtures, and closing
+the gap in the differ is tracked work:
+
+```bash
+npm run contract:compat
+```
+
+**Conformance works offline, forever.** Validating a document against the
+published contracts needs this package and nothing else — no account, no
+service, no network:
+
+```bash
+atelier dry-run ./atelier-export.json
+```
+
+`docs/continuity.md` records the distribution commitments behind these
+claims, including the perpetual Apache-2.0 grant on every tagged release you
+receive.
+
+## Quickstart
+
+```bash
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.1
+
+npx atelier init --fixture=sample-workspace --target ./sample
+npx atelier graph --project ./sample/atelier.project.json
+npx atelier project --project ./sample/atelier.project.json
+npx atelier readiness --project ./sample/atelier.project.json
+MNSTRY_ATELIER_ACTOR=owner npx atelier boundary check --project ./sample/atelier.project.json
+npx atelier dev --project ./sample/atelier.project.json
+```
+
+`npx` here runs the binary already installed in `./node_modules/.bin`. Always
+install first, and keep the `@mnstry/` scope — the unscoped name `atelier`
+belongs to an unrelated third-party package.
+
+`init` scaffolds a fictional sample workspace, `graph` builds the knowledge
+graph from front matter and sidecars, `project` generates the local review
+surface, `dev` serves it on loopback only. From there:
+
+```js
+import { validateAtelierExportDryRun } from '@mnstry/atelier'
+
+const report = validateAtelierExportDryRun(exportDocument)
+console.log(report.accepted, report.importable, report.errors)
+```
+
+Real projects start from the `private-domain`, `shared-project`, or
+`distribution` templates instead of the sample fixture.
+
+## What this package does
+
+- Initializes neutral local Atelier projects.
+- Builds a front-matter and sidecar-led knowledge graph; a `.kg.json` sidecar
+  enrolls any file — Markdown, JSON, YAML, CSV, media — without the kit ever
+  parsing the foreign format.
+- Generates and serves a local GUI projection over a loopback-only sidecar.
+- Produces agent-harness context and capability envelopes, and ships neutral
+  Codex and Claude skill wrappers for readiness review work.
+- Records proposal metadata without browser apply/write endpoints.
+- Enforces the local source `audience` and runtime `visibility` boundary, and
+  rejects unresolved, disguised, or non-public-projectable source references.
+- Enforces Repo Boundary Guard V1 for private domain and shared project
+  repos: strict policies fail closed when private or sensitive source is
+  placed in a shared repo, when protected local files are staged, or when
+  private-domain material appears in shared work without a `git.promote`
+  disclosure record.
+- Validates `atelier-export@v1` JSON against the published schema and
+  produces deterministic dry-run reports with `accepted`, `importable`, and
+  `worstOperationStatus`.
+- Ships the bundled `mnstry-readiness-pack@v1` with twelve claim-first
+  readiness protocols, extensible through validated extension packs.
+- Writes and checks `atelier.lock.json`, and applies branch-based,
+  review-first upgrades that refuse dirty repos and never silently overwrite
+  authored content.
+- Checks first-party source, templates, and examples for forbidden
+  non-localhost egress — a fail-closed discipline gate over this repo's own
+  code, not a runtime sandbox.
+
+## What this package does not do
+
+- It does not write to a MNSTRY runtime database.
+- It does not import, provision, publish, or send anything.
+- It does not contact external services.
+- It does not execute model-assisted analysis or any model provider.
+- It does not include client project content.
+
+These limits are the design. An authoring tool for private material earns
+trust by what it refuses to be able to do.
+
+## Your documents and the boundary
+
+What you author is yours. Documents live in your repositories, in formats you
+chose, readable without this tool. The one vocabulary the contracts enforce:
+`audience` describes local source readership (`public`, `team`, `operator`,
+`staff`, `private`, `sensitive`); runtime/export `visibility` describes
+runtime exposure and accepts only `private`, `shared`, `platform`, or
+`public`. A public export referencing a source whose audience is not public
+is refused — that check is fixture-pinned and mutation-tested.
+
+## Build a branded distribution
+
+The Atelier is designed to be white-labeled. A distribution wraps the CLI
+under its own name, contributes a validated extension pack (branded
+protocols, terms, templates), and themes the projection — while the root
+contracts, guards, and conformance stay canonical underneath. Start by
+copying the worked example:
+
+- `examples/loomworks-studio` — a complete fictional distribution: branded
+  bin, extension pack, themed workspace template.
+- `docs/distributions.md` — the contract a distribution must honor.
+- `TRADEMARKS.md` — naming rules; Apache-2.0 grants code rights, not brand
+  rights. Every distribution carries "powered by MNSTRY Atelier" attribution,
+  checked by `atelier distribution check`.
+
+## The MNSTRY relationship
+
+The Atelier is the front porch, not the house. Conformance — is this document
+valid against the published contracts? — is public, offline, and free,
+forever. Admission — will MNSTRY's governed runtime accept it for delivery to
+clients? — is a separate, opt-in step: a signed attestation issued by MNSTRY
+against criteria this package publishes (`docs/attestation.md`). You can
+build on the Atelier without ever talking to MNSTRY. If you want your work to
+run on MNSTRY runtimes, the path is admission, and the rejection message is
+part of the contract.
+
+## Feedback and announcements
+
+Both channels respect consent by construction. `atelier feedback` writes a
+scanned, redaction-checked report to a local file — there is no send path;
+you choose whether and where to share it. `announcements list` verifies
+project-shipped announcements against a committed public key — pull-only,
+nothing phones home to ask.
+
+## Running the test suite from a fresh clone
+
+`npm test` includes one fail-closed check that expects a private denylist
+file (`release-denylist.local.json`, gitignored) used by MNSTRY's release
+lane. On a fresh clone that file is absent, so the check **fails** — it never
+passes silently on missing protection. Expect this, after `npm install`:
+
+```bash
+npm install
+npm test     # 509 tests: 508 pass, 1 fail — the denylist check, by design
+```
+
+To acknowledge the missing file and run the rest, which turns that failure
+into a recorded skip:
+
+```bash
+ATELIER_ALLOW_MISSING_DENYLIST=1 npm test     # 508 pass, 0 fail, 1 skipped
+```
+
+## Command reference
+
+```bash
+atelier dry-run ./atelier-export.json
+atelier contract check
+atelier graph --project ./atelier.project.json
+atelier project --project ./atelier.project.json
+atelier readiness --project ./atelier.project.json
+atelier readiness protocols
+atelier readiness journey --project ./atelier.project.json
+atelier readiness run mnstry.readiness:identity-map --project ./atelier.project.json
+atelier readiness packet --project ./atelier.project.json
+atelier readiness export --dry-run --project ./atelier.project.json
+atelier boundary check --project ./atelier.project.json
+atelier boundary check --staged --project ./atelier.project.json
+atelier boundary install-hooks --project ./atelier.project.json
+atelier promote --source-repo tenant-private-domain --target-repo project-alpha --kg-id tenant-private-domain:seed
+atelier lock write --project ./atelier.project.json
+atelier lock check --project ./atelier.project.json
+atelier upgrade --dry-run --project ./atelier.project.json
+atelier upgrade --apply --project ./atelier.project.json --branch codex/atelier-upgrade-YYYYMMDD
+atelier extension-pack validate --project ./atelier.project.json
+atelier attestation verify ./attestation.json
+atelier feedback create --message "what happened"
+atelier announcements list
+atelier distribution check --target ./my-distribution
+atelier dev --project ./atelier.project.json
+```
+
+`upgrade --apply` creates or switches to the requested branch, refuses dirty
+authored repos, preserves unrelated user hooks through composed hook files,
+runs only registered migrations, refreshes generated projections, and leaves
+a Git commit for review. It will not weaken boundary policy, introduce
+telemetry, enable non-localhost egress, run model-assisted analysis, or write/import/apply
+runtime state.
+
+## Sample fixtures
+
+Fixtures in this package are fictional and generic. Project-specific adapter
+fixtures belong in their project repositories, not in the published Atelier
+package.
+
+## License and contributing
+
+Apache-2.0. See `LICENSE`, `NOTICE` (attribution obligations that survive
+forks), `TRADEMARKS.md` (naming), and `docs/continuity.md` (distribution
+continuity commitments). Contributions are accepted under inbound-equals-
+outbound Apache-2.0 with a DCO sign-off — `CONTRIBUTING.md` is the working
+agreement, including how to contribute without exposing client material or
+your own private methodology.

package/SECURITY.md

@@ -0,0 +1,93 @@
+# Security policy
+
+The Atelier is an authoring tool for private material. Its guarantees are
+enforcement claims, not aspirations — so a way around a guarantee is a
+vulnerability here even when nothing crashes and no data is lost.
+
+## Reporting a vulnerability
+
+**Use GitHub private vulnerability reporting**:
+<https://github.com/MNSTRY/atelier/security/advisories/new>. That channel is
+private, gives you a tracked advisory, and lets a fix and a disclosure be
+prepared together.
+
+If that is unavailable to you, email **erik@mnstry.ai** with `atelier security`
+in the subject line.
+
+Do not open a public issue for a vulnerability, and do not include client
+material, private methodology, or key material in a report. A report needs the
+mechanism, not your real data — if you cannot demonstrate the finding without
+sensitive content, say so and describe the shape instead.
+
+### What to expect
+
+Maintenance is small and deliberate, so these are honest targets rather than
+guarantees:
+
+- Acknowledgement within 3 business days.
+- An initial assessment — accepted, needs more information, or out of scope,
+  with reasoning — within 10 business days.
+- Fixes released as a new tagged version. Where a fix changes a published
+  contract, it follows the same compatibility rules as any other change:
+  a new contract version and a recorded migration.
+- Credit in the advisory and changelog under the name you choose, or no
+  credit if you prefer. You will be asked before being named.
+
+Coordinated disclosure is the expectation. Give a fix a reasonable window
+before publishing; you keep the right to publish, and there is no embargo
+you have to sign.
+
+## In scope
+
+These are the claims the package makes. Defeating any of them is a
+vulnerability, and the more quietly it can be defeated, the more severe:
+
+- **Egress.** Any network send path in first-party code, or any way to make
+  the local sidecar reachable off loopback or serve a policy that authorizes
+  an external origin.
+- **Boundary guard.** Any way to get private or sensitive source into a
+  shared repo, to stage a protected local file, or to promote private-domain
+  material without the required disclosure record — while the guard reports
+  clean.
+- **Disclosure scanners.** Any way to get denylisted or structurally
+  forbidden content past `repo:check` or `release:audit`, including through
+  encoding, line splitting, file types the scanner skips, or symlinks.
+- **Audience and visibility.** Any export accepted as `public` that
+  references a source whose audience is not public.
+- **Attestation.** Signature or verification flaws in `attestation verify`,
+  or announcement verification accepting content the published key did not
+  sign.
+- **Upgrade.** Any path where `upgrade --apply` overwrites authored content,
+  weakens boundary policy, or runs an unregistered migration.
+- **Contract compatibility.** Any way to widen a schema outside `ext`
+  containers without the compatibility gate refusing it.
+
+Supply-chain reports about this repository's own release and CI machinery are
+in scope: workflow injection, secret exposure to untrusted code, or a way to
+make a released tarball differ from the reviewed tag.
+
+## Out of scope
+
+- **The sidecar is loopback-only and unauthenticated by design.** Someone who
+  already has a local account and can reach loopback is inside the trust
+  boundary. A way to reach it from off-host is in scope; using it from on-host
+  is not.
+- **Local file access.** The Atelier reads and writes files you point it at,
+  with your own permissions. That is the design.
+- **Vulnerabilities in your own authored content** or in extension packs and
+  distributions maintained outside this repository.
+- **Dependency advisories with no reachable path** through this package.
+  Report them anyway if you are unsure — but a bare scanner dump against
+  `ajv` with no exploitation path is not a finding.
+- **Missing hardening with no demonstrated impact.** Show the mechanism.
+
+## Supported versions
+
+The package is alpha. Only the latest tagged release receives fixes; there
+are no backports to earlier tags. Published contracts carry a separate and
+stronger promise — `docs/contract-stability.md` and `docs/continuity.md`
+record it — and that promise is not weakened by a security fix.
+
+## Received advisories
+
+None to date.

package/TRADEMARKS.md

@@ -0,0 +1,88 @@
+# MNSTRY trademarks
+
+The names MNSTRY and MNSTRY Atelier, and the associated logos, are trademarks
+of MNSTRY. The Apache-2.0 license for this package (see LICENSE section 6, "Trademarks")
+grants no trademark rights: you may use, modify, and redistribute the code
+without any right to use these marks except as described in this document.
+
+## What this document binds
+
+These terms are conditions on using the MNSTRY marks and on claiming
+Distribution status. They are not conditions on the code. Apache-2.0 governs
+copying, modification, and redistribution, section 4 states those conditions
+in full, and this document adds none: you may redistribute this package,
+modified or not, without displaying the attribution string, so long as you
+make no use of the MNSTRY marks and claim no Distribution status. Everything
+below is the price of carrying the marks, not the price of using the
+software — including the attribution that `atelier distribution check`
+verifies, which checks distributions that have chosen to carry the marks.
+
+## Required attribution
+
+Distributions built on this package must display the exact attribution string
+
+    powered by MNSTRY Atelier
+
+in two places:
+
+- the distribution's root `README.md` (byte-for-byte match on the phrase;
+  the surrounding text is free), and
+- the distribution's user-facing credits or about surface.
+
+The README requirement is normative and mechanically checked by
+`atelier distribution check`. As an advisory (reported, non-blocking) signal,
+a distribution's extension-pack manifest may also carry
+`ext["mnstry.atelier/attribution"]` set to the same attribution string, using
+the reserved `ext` container — no schema change is involved. Attribution in
+`--version` output is a distribution-side test convention, not a runtime
+check.
+
+## Quiet software
+
+The kit, and anything carrying the "powered by MNSTRY Atelier" attribution, must not
+emit commercially motivated interruptions: no upsells, no calls-to-action, no
+prompts to sign up, upgrade, rate, subscribe, or purchase. Attribution stays a
+passive line — it identifies, it never solicits. MNSTRY binds itself to the
+same standard, including this channel policy: outbound communication is
+limited to user-initiated artifacts, inbound communication is pull-only, and
+there is no telemetry, ever. Violating this clause forfeits the right to carry
+the MNSTRY marks.
+
+## Applications
+
+An application powered by this package that ships no CLI carries the
+attribution in its user-facing credits or about surface. The wording
+requirements mirror the distribution rule above: the exact attribution string,
+byte for byte, with the surrounding text free.
+
+## Naming your distribution
+
+MNSTRY marks may not appear in product names, package names, or domain names.
+Nominative use is permitted in the form "<YourName> for MNSTRY Atelier", which
+names the compatibility target without implying that MNSTRY publishes or
+endorses your distribution.
+
+## Compatibility claims
+
+The sanctioned phrasing for a compatibility claim is:
+
+    implements atelier contracts v1
+
+Conformance is public and offline: anyone can run the published validators in
+this package and reach the same answer (see `docs/attestation.md`). No
+permission is needed to make a truthful compatibility claim in this form, and
+no attestation can substitute for it.
+
+## Certification and admission
+
+The phrases "MNSTRY certified" and "MNSTRY admitted" (and equivalents) are
+reserved to holders of a signed MNSTRY attestation that verifies per the
+procedure in `docs/attestation.md`. Self-issued or unsigned attestations
+confer no such claim: an attestation with `"signature": null` is
+non-authoritative by definition, and a signature is only meaningful under a
+key the relying party recognizes as MNSTRY's.
+
+## Questions
+
+For trademark questions or permission requests beyond what this document
+covers, contact MNSTRY through the channels listed in the package README.

package/announcements/2026-08-06-announcements-channel.v1.json

@@ -0,0 +1,12 @@
+{
+  "schema": "mnstry.announcement@v1",
+  "announcementId": "announcement:2026-08-06:announcements-channel",
+  "publishedAt": "2026-08-06",
+  "title": "Signed announcements channel",
+  "body": "MNSTRY now publishes announcements as signed JSON documents committed\nunder `announcements/` in this repository. This is a pull-only channel:\nyou receive announcements by running `git pull`, and pulling is the\nconsent act. There is no push channel, no subscription, and no tracking —\nthe kit never fetches announcements or anything else over a network.\n\nEvery announcement is signed with the MNSTRY announcements key. The\npublic half is committed at\n`announcements/keys/mnstry-announcements.public.v1.json`; verify any\nannouncement with:\n\n    atelier announcements verify announcements/<file>.json\n\nor list and verify everything at once with\n`atelier announcements list`. A document that does not verify should be\ntreated as not from MNSTRY. See docs/announcements.md for the full\nconvention.",
+  "signature": {
+    "algorithm": "ed25519",
+    "keyId": "mnstry-announcements-2026",
+    "value": "iiSYs00uJMhFEb6VSovZohv4zNrdEt3tBv4sqjs7v6XMN7EpxJnzHdBwb8jBGZ5zWp3SZEKsA76VYbarWfvBBA"
+  }
+}

package/announcements/keys/mnstry-announcements.public.v1.json

@@ -0,0 +1,9 @@
+{
+  "keyId": "mnstry-announcements-2026",
+  "algorithm": "ed25519",
+  "publicKeyJwk": {
+    "crv": "Ed25519",
+    "x": "vU_2IhY0vdnvMl9i4pI3N3s77ZReYc3tAujldyG_6Ng",
+    "kty": "OKP"
+  }
+}

package/bin/atelier.mjs

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import './mnstry-atelier.mjs'

package/bin/mnstry-atelier.mjs

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+import { runCli } from '../src/cli/run.mjs'
+process.exit(await runCli({ argv: process.argv.slice(2) }))