@mnstry/atelier 0.2.0-alpha.14 → 0.2.0-alpha.15

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # Changelog
 
+## 0.2.0-alpha.15
+
+- Patch the fast-uri dependency and override from 3.1.8 to 3.1.9, the patched 3.x release for GHSA-w74x-v6f9-j3xg, GHSA-xhq7-xmqj-769h, GHSA-wjr9-j795-jxcr and GHSA-333x-w4r6-6crp (3.1.8 is in each affected range; whether Atelier's use was exploitable is not established). Ajv's own `^3.0.1` range resolves to the same copy, so a bare consumer installs 3.1.9 only, and `npm audit` reports no runtime advisory.
+- Add the graph workspace (`@mnstry/atelier/graph-workspace` and `/graph-workspace/browser`): one graph in three rooms, a constellation of every readable record on a night-sky canvas with folder zones and collision-free labels, a workbench of sparse cards beside a focused authoring sheet, and a review that shows before and proposed and leaves the decision to a person. Work recipes choose the room, lens and primary action, and compose across Atelier, coach and owner layers with per-field provenance; themes compose the same way and refuse unsafe values and low contrast. Scale helpers show the whole as zones beyond 12,000 records and open one zone at a time with every omission counted. Drafts live behind a storage port (this browser by default, and the interface says so). A shareable-content gate finds fingerprints of private graphs in shareable text. Renderer packages are injected by the host; Atelier adds no runtime dependency. See the [graph workspace guide](docs/guides/graph-workspace.md).
+- Add renderer-neutral graph views (`atelier.graph-view@v1`), a reader-bound graph access port, repository-qualified Markdown source contributions, a source-bound edge eligibility policy and adapters that bind source contributions through edge policy to graph access. Hosts still own authentication, grants, revalidation and keys.
+- Add a structured graph explorer with a provenance inspector, an optional Babylon graph-view consumer, source-bound ontology guidance drafts, and an authorized projection refresh lifecycle with scoped impact comparison.
+- Refuse aliases of Git metadata, a root Git metadata entry that disappears before capture, and impossible UTF-16 or UTF-8 locator offsets in repository contributions, and resolve outgoing links from uppercase `.MD` sources. Knowledge Health pins the bytes of the knowledge-graph file, so its rule identity is regenerated for it: the `check` each assessment carries names a new `version` and `sourceTree`, and the rule it applies is unchanged.
+
+- Accept a longer personal-selection history without a fresh confirmation only when it still holds the accepted record at its position. After a confirmed shortening, a divergent history at or above the earlier maximum refuses until it is confirmed again; ordinary appends and exact restoration are unchanged.
+
+- Check the private-state location before a first use writes the workspace pointer, and check the persisted identity again before any further write. A refused location now leaves no pointer and no local state behind.
+
+- Write no refusal bookkeeping for a private-state location refusal (a lock held or just taken is still released or withdrawn), and none unless the state root is still outside every root declared now, for a cached store as well as a newly located one. A configured locator that refuses leaves current roots unknown, so nothing is written. Retained selection-continuity writes, freshness writes and every engine phase that writes after a cooperative wait (vault-edit preservation, pending edits, automatic apply, preparation and publication) prove the location again against the roots declared now, as do engine-lock acquisition after its inspection, vault allocation after reading the app's list, and the publisher after each wait for the app, its list of vaults, its comparison of kept notes or its quiet period. Neither a location refusal nor a failure that leaves the location unproven (a wait for the app that gave up) writes a publication failure entry. A service started by a login item no longer falls back to the workspace the unit names when locating its workspace refuses, and prints a location refusal instead of logging or recording it there; a tick the engine refuses outright for the location of private state leaves the service's error record as it was. A refusal of the private state's own location found in one view (`managed-root-unproven`) stops the whole tick, so no later view goes on under roots that can no longer be trusted; a view whose own vault is in a bad place is still refused alone. These proofs are made at named points in the engine and the publisher, not at every write. Roots "declared now" are a personal home's manifest read again at each proof; an ordinary project's are those of the project as last loaded, until it is loaded again. The service process's own records, its plugin state and the built-in proposal store are not proven against the roots declared now; Known limits in the Obsidian guide lists them.
+
+- Never let an unpersisted selection acceptance replace a newer durable one: a retained observation keeps its maximum and identities, but the checkpoint's accepted head wins once another writer has changed it.
+
+- Refuse `obsidian uninstall` when the workspace location or identity cannot be established, instead of reporting that nothing was installed. No login-item or service action is taken.
+
+- Create every workshop directory and file exclusively when initializing a new workshop, so a directory or file that arrives meanwhile refuses instead of being merged, and refuse before Git initialization if an unknown entry appears inside a directory the initialization created. Nothing is overwritten and nothing unknown is removed.
+
+- Order journey runs by their validated creation instant, with run identity as the deterministic tie-break. Latest-per-protocol summaries and tenant packets share that rule; malformed times refuse rather than inherit hash-filename order. Clarify that a review-workspace decision concerns its run claims and source linkage alone does not establish logical support.
+
+- Refuse a view as mixed-read when a previously observed source becomes a directory or changes during its pinned read, or a graph-declared sidecar disappears during the build. Other views can proceed; never-observed and unreadable sources retain their own errors.
+- Cover the Astro presentation example in weekly dependency updates. Update Astro to 7.3.8 and refresh its locked sharp and HTTP cache-semantics dependencies to their patched releases.
+
+- Event-loop benchmark results record the host logical CPU count and the one-, five- and fifteen-minute load averages at the start and end, including failed runs, so responsiveness evidence can be read with its host conditions.
+- Keep all enrolled repository roots outside private service state when locating a personal workspace. Locating an existing home now requires its readable authored manifest, including an explicitly empty enrollment; the lower-level service API refuses a bare home instead of assuming no repository exclusions. Login-item removal and uninstall can retain their off choice before any generation is confirmed, and report the actual kept workspace pointer. Clarify which generation reads and assembly still run on the caller thread.
+
+- Persist personal-selection continuity across service starts. A shortened history stays refused until its removed records return or a fresh confirmation accepts it; previously observed records cannot stand in for a new confirmation. A missing checkpoint with retained private ownership evidence refuses instead of becoming a first start.
+- Initialize an undecided personal vault audience as owner only in machine settings. Explicit choices and clears keep their meaning; personal bindings permit `audience set me` and `audience clear`, and refuse custom audience lists. Initialization rereads under the same lock as setting writes so a concurrent clear stays empty.
+- Keep blocking boundary diagnostics visible before warnings, report one aggregate evidence limit, and pin path quoting in Git evidence. Staged acquisition refuses missing or incomplete repository evidence and covers type changes without rename collapse. Conservative semantic assignment detection and runner-error handling preserve classified-document deletion review. Boundary checks flush complete JSON diagnostics through pipes before returning their refusal exit code.
+
+- Allow projects to deselect the bundled MNSTRY readiness pack with tracked `ext["mnstry.atelier"].readiness.includeBundled: false`. Generic graph, project and readiness checks and selected custom protocols remain available; bundled journey, packet and readiness export commands refuse. Selection changes require an explicit lock write. Absent or `true` preserves the existing default, IDs and APIs.
+
+- Name the practical-judgment responsibility Phronesis, with practical judgment as its plain-language description. Existing catalog identity, English lookup alias, judgment API and skill identities remain compatible. Keep Knowledge Stewardship distinct from the shared Knowledge Graph representation; move the current guide to `docs/reference/phronesis.md`.
+
+- The boundary push check names its reason when a push's refs together exceed the evidence budget (`push-evidence-too-large`, with `limitBytes`, as when one ref's commits do), where before that refusal carried no reason. The text output of `atelier boundary check` and `atelier boundary push-check` lists a scan that could not finish (`content-scan-incomplete`, `semantic-field-scan-incomplete`, `repo-unscannable`) before the content findings and says how many findings past the first 50 it leaves out, so a long list no longer hides why a commit or push was refused. The guard documentation says the 1000-commit limit applies to each ref update and what to do with a single commit over the budget on its own.
+
+- Add the optional native Convex backend adapter and TypeScript starter through the existing extension init/seal/validate/bundle workflow. HTTP admission and private native mutations reuse the delegation contract; indexed operation results commit with custom writes. Native provider qualification remains separate from reactive lifecycle and complete host/customer acceptance.
+
+- Add native Drizzle DB-first/code-first and Prisma 7 project profiles, prepared scoped transactions and provider receipt recovery. Optional provider dependencies stay in the generated app; Root and supported-host acceptance remain separate gates.
+
+
+- Organize current documentation into start, guides, reference and maintainer folders with one index. Remove superseded planning/review and event walkthrough files. Remove the retired Obsidian publication experiment, retaining its active isolated-app test fixture in the maintained harness with read-only inspection and refusal coverage. Required packed-document and inbound references follow the new paths.
+
+- Repository cleanup groups vault test helpers under `test/support/vault/` and imports consumer-closure diagnostics directly from their existing source module. CLI help describes `mnstry-atelier` as a supported npm alias. The repository-local reconsideration tool now measures only the explicitly marked Maintained implementation decisions section of the architecture reference; definition revision four retains predicate v3 and all original measurement records.
+
+- Add portable typed extension contracts, authenticated host clients, signed server admission and native Postgres transaction/receipt helpers under the existing package.
+- Add `atelier extension init|validate|seal` for a customer-owned Postgres TypeScript project. Generation and sealing do not deploy or authorize an installation. Provider and supported-host qualification carry separate evidence.
+
 ## 0.2.0-alpha.14
 
 - The Obsidian maintenance service's log no longer gets a `status-project-loaded` line for every failure and recovery, or every slow load, of the plugin's status read while its loads come less than a minute apart and fail, or are slow, every other load or every third. Before, any load that answered ended a row of failures, and any load in time a row of slow loads. Now a row of failures ends only at a load that answers a minute or more after its last failure, with a line that names how many failures it held, and a row of slow loads only at a load in time a minute or more after the last slow one. Such a loader writes one row, less and less often. While a project is kept, it is loaded again every two and a half minutes, so there a row of failures ends at the next reload that answers. A loader that answers at least one reload between two failures still writes each failure and the load that ends its row, and one that fails at every reload and answers only at its retry keeps one row. Each slow load is still written there. A load at every request is now written too, when each load names the files it started over. That happens while a file that decides the views vouches for nothing, or while loads never agree, and before it showed only as a growing count. A load after which nothing is kept, though it named the files it started over, is written from the second in a row, on the same doubling row (`notKept`, with `vouched`); a load that named other files, as after a new confirmed selection, neither counts nor ends that row. `statusLoads` in the status document counts these loads as `notKept`, one at a start and one after each change on a healthy service.

package/README.md

@@ -1,5 +1,7 @@
 # MNSTRY Atelier
 
+`0.2.0-alpha.15` adds a [graph workspace](docs/guides/graph-workspace.md) (a constellation of every readable record, a focused authoring workbench and a review room, built from primitives coaches and owners can compose), renderer-neutral graph views and an [extension SDK and Postgres project workflow](docs/guides/extensions.md). Native host qualification remains a separate gate.
+
 **Turn a repository into a living, governed system.**
 
 Important bodies of work often begin as files: methods, research, programs,
@@ -31,11 +33,15 @@ that must stay legible, internally connected, privacy-aware, and usable across
 many interfaces. Methodology authoring is one application of the system, not
 its definition or ceiling.
 
-See the [responsibility architecture](docs/architecture.md) for Inquiry, Knowledge
-Stewardship, Practical Judgment, Creation and Delivery, Capability Stewardship,
+See the [responsibility architecture](docs/reference/architecture.md) for Inquiry, Knowledge
+Stewardship, [Phronesis — practical judgment](docs/reference/phronesis.md), Creation and Delivery, Capability Stewardship,
 Reflection, Interaction and Coordination. Start a provider-neutral research
-workflow with the [research starter](docs/research-starter.md).
-Use [portable template profiles](docs/template-profile.md) to bind semantic and
+workflow with the [research starter](docs/guides/research-starter.md).
+Knowledge Stewardship is the broader responsibility; the Knowledge Graph is a
+shared representation used across responsibilities. Phronesis draws on and
+contributes to that graph through existing owners. It supplies no automatic
+wisdom or universal score.
+Use [portable template profiles](docs/reference/template-profile.md) to bind semantic and
 surface roles to canonical sources, with optional advisory decisions and
 separate host and release validation.
 
@@ -59,23 +65,23 @@ when a maintainer starts it by hand.
 ## From files to a working system
 
 Start with a question that changes useful work. The
-[knowledge setup workflow](docs/knowledge-setup.md) supplies an editable ontology
+[knowledge setup workflow](docs/start/knowledge-setup.md) supplies an editable ontology
 plan, a fictional starter, and CLI checks that connect concepts to questions.
 `atelier knowledge context` selects complete, source-linked evidence within a
 byte budget; `atelier knowledge evaluate` compares lexical and graph retrieval
 without provider calls. A passing check is structural evidence; useful answers
 and efficient token usage still need measurement in real work.
 
-For local-harness authoring, see [durable coauthor sessions](docs/coauthor-session.md)
-and [skill stewardship and managed installation](docs/skill-steward.md).
-The next-release [capability stewardship foundation](docs/capability-stewardship.md)
+For local-harness authoring, see [durable coauthor sessions](docs/reference/coauthor-session.md)
+and [skill stewardship and managed installation](docs/guides/skill-steward.md).
+The next-release [capability stewardship foundation](docs/guides/capability-stewardship.md)
 adds portable packages, repository-owned adoption and version-bound evidence
 alongside existing skills and tools.
-[Learning from feedback](docs/learning.md) connects private observations to
+[Learning from feedback](docs/guides/learning.md) connects private observations to
 reviewed lessons and explicitly activated harness context, with a local CLI.
-[Progressive local ingestion](docs/ingestion.md) preserves selected sources and
+[Progressive local ingestion](docs/guides/ingestion.md) preserves selected sources and
 provides bounded text, CSV and JSON evidence search before interpretation.
-[Immutable intake and guide contracts](docs/intake-and-guides.md) extend existing
+[Immutable intake and guide contracts](docs/reference/intake-and-guides.md) extend existing
 processing and hosted-tool adapters without adding remote execution or publication
 authority. These alpha capabilities require explicit consumer integration.
 
@@ -169,6 +175,42 @@ That distinction matters whenever several interfaces share one body of work.
 A public site, an internal review tool, and an agent session can all use the
 same graph while receiving different, mechanically checked projections.
 
+## Readable by people, checkable by machines
+
+A governed file is plain text with a small header. The text is the author's:
+they open, read and correct it with no tool between them and the words. The
+header is the machine's: what the file is, who it is written for and what it
+depends on, compiled by the builder into the graph. The graph check refuses a
+header that names a node which does not exist (configured external targets
+aside), and an agent follows the same
+lines to every file declared to depend on it. One artifact is both the human
+record and the machine index, versioned by Git, diffable line by line, and
+portable by copying the folder that holds the record and its history.
+
+## One working surface
+
+The day-to-day surface is the coding harness you already use, Claude Code,
+Codex or another coding harness, opened on the repository with the Atelier's
+skills installed in the workspace. Behind it sits the projection served from your files, and
+beyond it whatever systems you connect through the harness. From one
+conversation an agent reaches the local files, the projected pages, and your
+connected tools. The files are yours. The package supplies the graph, the
+checks and the pages. The harness supplies the model, the tools and the
+conversation.
+
+Skills carry the workflows an agent runs: opening a source, guiding an
+authoring session, running a readiness review, keeping the public boundary.
+They are delivered from the package as an audited set of skill files,
+installed into the workspace by a plan whose content digest is confirmed
+before it applies, and pinned by a lock, so the installed skill files are known
+and reviewable. Whether a given harness discovers and follows them is separate
+evidence. Enforcement never rests in a skill. Where they are wired into the
+commit path or CI, the graph check, the boundary guard and the export validator
+run whether or not an agent followed its instructions, and they fail closed. See
+[Co-authoring with agents](docs/guides/co-authoring.md) for the loop this makes
+reliable, and [Describing the Atelier](docs/maintainers/describing-the-atelier.md) for
+the judgment behind these sentences.
+
 ## The system beneath it
 
 ### 1. The repository becomes an ontology
@@ -224,7 +266,7 @@ graph. The library exposes the same project, graph, validation, and projection
 primitives to code.
 
 Consumer-owned authoring or review services that need a separate durable
-lifecycle follow [the managed local-service contract](./docs/local-services.md).
+lifecycle follow [the managed local-service contract](docs/reference/local-services.md).
 That contract standardizes process ownership, private local state, and browser
 recovery without putting a tenant's service details into Atelier.
 
@@ -237,7 +279,7 @@ The separate headless repository supervisor can observe one explicitly
 enrolled Git repository, fetch and fast-forward it, and prepare a bounded
 commit plan. A commit still requires an exact user confirmation and an
 unchanged re-observation; the loopback browser receives no apply endpoint.
-See [Atelier Sync: Deliverable Zero](docs/atelier-sync.md).
+See [Atelier Sync: headless repository supervisor](docs/guides/atelier-sync.md).
 
 ### 5. The repository can power another product
 
@@ -250,9 +292,9 @@ That tool may be private, open source, or commercial. Apache-2.0 permits all
 three. Conformance to the public Atelier contracts does not require a MNSTRY
 account or service.
 
-Read [the design document](./docs/design.md) for the five-part architecture and
-[the ontology](./docs/ontology.md) and
-[contract-stability policy](./docs/contract-stability.md) for the stable
+Read [the design document](docs/reference/design.md) for the five-part architecture and
+[the ontology](docs/reference/ontology.md) and
+[contract-stability policy](docs/reference/contract-stability.md) for the stable
 boundaries.
 
 ## Build your own tool on it
@@ -295,11 +337,11 @@ const navigation = renderActionGroup([
 
 The package exports change over the alpha series, so pin the exact prerelease
 version and treat the package export map and shipped source modules as the
-executable API reference. [Distribution contracts](./docs/distributions.md) explain
+executable API reference. [Distribution contracts](docs/guides/distributions.md) explain
 how a governed subset can be packaged for another surface without widening its
 audience.
 
-The [advisory decision contract](./docs/decisions.md) gives hosts bounded
+The [advisory decision contract](docs/reference/decisions.md) gives hosts bounded
 choice, score and boolean questions with evidence references and recorded
 uncertainty. `@mnstry/atelier/decisions` validates these records offline.
 The host supplies optional provider execution and retains authorization;
@@ -327,7 +369,7 @@ host evaluation and human acceptance require their own evidence. This source
 capability has shipped as the `capability` command since 0.2.0-alpha.13.
 <!-- atelier:block:capability-stewardship:end -->
 
-See [capability stewardship](docs/capability-stewardship.md) for the operating guide.
+See [capability stewardship](docs/guides/capability-stewardship.md) for the operating guide.
 
 ## Discovery and research
 
@@ -353,7 +395,7 @@ pack retains its Discovery Engine title, identifiers and original digest, so
 existing release locks can use the governed upgrade path without a separate repin.
 <!-- atelier:block:inquiry-harnesses:end -->
 
-See [Discovery and Research Harnesses](docs/inquiry-harnesses.md) for the local workflow.
+See [Discovery and Research Harnesses](docs/guides/inquiry-harnesses.md) for the local workflow.
 
 ## Where the Atelier stops
 
@@ -389,7 +431,7 @@ platform logins must uniquely match declared login mappings. Repository identity
 checks may invoke `gh api repos/...` to resolve a canonical GitHub identity.
 Those authenticated requests use your own `gh` credentials. Recorded repository
 identities let identity checks keep working when the provider is unavailable.
-See `docs/install.md` for the full attribution precedence and mode semantics.
+See `docs/start/install.md` for the full attribution precedence and mode semantics.
 Explicitly enrolled Atelier Sync may also run bounded Git fetches
 for observation/reconciliation and one non-force push only when the exact
 reviewed commit plan requested and confirmed it, no earlier local commit is
@@ -444,7 +486,7 @@ service, no network:
 atelier dry-run ./atelier-export.json
 ```
 
-`docs/continuity.md` records the distribution commitments behind these
+`docs/reference/continuity.md` records the distribution commitments behind these
 claims, including the perpetual Apache-2.0 grant on every tagged release you
 receive.
 <!-- atelier:block:claims:end -->
@@ -486,7 +528,7 @@ Admission is a narrower, opt-in decision: whether a MNSTRY governed runtime
 accepts a document for delivery to the people it serves. That is what
 admission buys — delivery through a runtime that enforces consent and
 visibility at serve time — and it takes the form of a signed MNSTRY
-attestation against criteria this package publishes (`docs/attestation.md`).
+attestation against criteria this package publishes (`docs/reference/attestation.md`).
 The criteria are public, the checker is private, and the rejection message
 is part of the contract. You can build on the Atelier without ever talking
 to MNSTRY, and a document MNSTRY declines can still be fully conformant.
@@ -501,19 +543,10 @@ Pin the prerelease while the package remains in alpha:
 npm install --save-dev @mnstry/atelier@0.2.0-alpha.14
 ```
 
-Then choose the path that matches what you are building:
-
-- [Installation and first run](./docs/install.md)
-- [Design and architecture](./docs/design.md)
-- [Knowledge graph and source model](./docs/knowledge-graph.md)
-- [Local runtime and agent boundary](./docs/atelier-runtime.md)
-- [Distribution contracts](./docs/distributions.md)
-- [Conformance and attestation](./docs/attestation.md)
-- [Continuity commitments](./docs/continuity.md)
-- [Assurance controls and evidence map](./docs/assurance-controls.md)
-- [Upgrade notes](./docs/upgrade.md)
-- [Upgrade with your agent](./docs/guided-upgrades.md)
-- [Obsidian projection](./docs/obsidian.md)
+Start with [independent setup](./docs/start/independent-start.md) or
+[installation and first run](./docs/start/install.md). The
+[documentation index](./docs/README.md) organizes the maintained guides,
+API and architecture references, and maintainer controls.
 
 ## Status and command reference
 
@@ -558,7 +591,7 @@ MNSTRY Atelier is released under [Apache-2.0](./LICENSE).
 
 ## Experimental hosted vault contract
 
-An optional [private artifact vault service](docs/vault-service.md) supplies a
+An optional [private artifact vault service](docs/reference/vault-service.md) supplies a
 provider-independent ownership boundary and explicit Vercel/Cloudflare storage
 bindings. It is not enabled by local CLI commands. Hosting adapters can perform
 network I/O only when explicitly installed and invoked by a consuming host.
@@ -573,12 +606,12 @@ to its source manually or under a scoped policy the user installs; anything
 structural stays a copy-only proposal. Atelier never commits to Git for it.
 It is disabled unless a project enables it, and it is proven on one platform
 and one app version. Every vault it publishes carries
-[Atelier's own Obsidian plugin](docs/obsidian-plugin.md), which Obsidian asks
+[Atelier's own Obsidian plugin](docs/reference/obsidian-plugin.md), which Obsidian asks
 you to trust once per vault; it shows whether the view is current, writes
 nothing, and talks only to the local maintenance service, and the projection
-works the same without it. Read [what it does and its known limits](docs/obsidian.md),
-the [contract](docs/obsidian-contract.md) and the
-[maintenance service](docs/local-services.md) before relying on it. The
+works the same without it. Read [what it does and its known limits](docs/guides/obsidian.md),
+the [contract](docs/reference/obsidian-contract.md) and the
+[maintenance service](docs/reference/local-services.md) before relying on it. The
 package subpaths are `@mnstry/atelier/obsidian` and
 `@mnstry/atelier/obsidian/*`.
 
@@ -602,15 +635,15 @@ Recorded acceptance is not authenticated authority, and local checks do not prov
 research quality or recipient acceptance. Hosted execution remains adapter-owned.
 <!-- atelier:block:learning-harnesses:end -->
 
-Read the [Knowledge and Build Harness guide](docs/learning-harnesses.md) for the complete local learning cycle.
+Read the [Knowledge and Build Harness guide](docs/guides/learning-harnesses.md) for the complete local learning cycle.
 
-The [research quickstart](docs/research-starter-quickstart.md) explains how to use
+The [research quickstart](docs/start/research-starter-quickstart.md) explains how to use
 a supplied candidate packet with existing tools and skills. See
-[Trackables](docs/trackables.md), [Interaction and Reflection](docs/interaction-and-reflection.md)
-and [Coordination](docs/coordination.md) for portable runtime profiles and host obligations.
+[Trackables](docs/reference/trackables.md), [Interaction and Reflection](docs/reference/interaction-and-reflection.md)
+and [Coordination](docs/reference/coordination.md) for portable runtime profiles and host obligations.
 
-The optional [knowledge workspace](docs/knowledge-workspace.md) connects
+The optional [knowledge workspace](docs/guides/knowledge-workspace.md) connects
 onboarding, ontology modeling, evidence deepening, application, and outcome
 learning with shared private coauthor sessions for people and agents.
 
-The [public workshop profile](docs/knowledge-health/devday/public-default.md) uses the existing Knowledge host to retain ordinary drafts and one copy-only source-owner handoff as a local proposal.
+The [public workshop profile](docs/knowledge-health/quickstart.md) uses the existing Knowledge host to retain ordinary drafts and one copy-only source-owner handoff as a local proposal.

package/SECURITY.md

@@ -90,7 +90,7 @@ make a released tarball differ from the reviewed tag.
 
 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`
+stronger promise — `docs/reference/contract-stability.md` and `docs/reference/continuity.md`
 record it — and that promise is not weakened by a security fix.
 
 ## Received advisories

package/TRADEMARKS.md

@@ -69,7 +69,7 @@ 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
+this package and reach the same answer (see `docs/reference/attestation.md`). No
 permission is needed to make a truthful compatibility claim in this form, and
 no attestation can substitute for it.
 
@@ -77,7 +77,7 @@ no attestation can substitute for it.
 
 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
+procedure in `docs/reference/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.