Adopt updated policies and simplify release publication

docs/policy/architecture.md

@@ -1,7 +1,21 @@
-# Architecture
+# Architecture Policy
 
-This document defines Scriptorium's current application architecture and
-durable development boundaries.
+**Base Policy Version:** 1.1
+
+**Last Updated:** 2026-09-26
+
+## Purpose And Ownership
+
+This policy defines Scriptorium's purpose, responsibility and dependency
+boundaries, established invariants, and non-goals. Concrete component inventory
+and implementation mechanics belong in [internal documentation](../internal/overview.md);
+public behavior belongs in its canonical contracts.
+
+Adopted constraints govern future development without implying that every
+capability they could govern exists or is planned. Keep proposed structure and
+implementation status in roadmaps, and decision rationale in ADRs. Acceptance
+of a decision is not proof of implementation. Do not turn incidental choices
+into architectural invariants.
 
 ## System Shape
 
@@ -21,6 +35,16 @@ deployment policy.
 The concrete package inventory is maintained in the
 [internal overview](../internal/overview.md).
 
+As established by [ADR 0004](../adr/0004-definition-boundary.md), Scriptorium
+aims to support the complete set of features in valid Promptkit prompt and
+profile definitions for its selected upstream version. Promptkit remains the
+canonical parser and validator. Library-only features are considered
+individually against the simple predefined-prompt execution model.
+
+Maintain adapter boundaries with proportionate, idiomatic code. This approach
+does not require an interface for every type, additional wrappers, or a fixed
+directory tree for integrations that do not exist.
+
 ## Dependency Direction
 
 ```text
@@ -46,6 +70,10 @@ gitea.maximumdirect.net/eric/promptkit
 The repository architecture guard enforces these import and removal
 invariants.
 
+Cross-project changes land and release in Promptkit before Scriptorium adopts
+the tagged dependency. Do not commit Go workspaces, local replacements,
+vendored Promptkit implementation, or unpublished dependency assumptions.
+
 ## Retained Boundaries
 
 - `internal/adapter/cli` owns commands, flags, configuration precedence,
@@ -71,6 +99,13 @@ That reader denies file references without an artifact root, enforces the
 configured byte limit, and applies Scriptorium's lexical root-containment rule.
 The operating system still follows symlinks after the lexical check.
 
+This boundary handles untrusted request references under the documented
+deployment model; it is not a filesystem sandbox. Defending against a
+privileged actor concurrently modifying the host filesystem is outside the
+adopted scope, not a claim that such activity cannot occur. Do not infer
+additional defenses or guarantees from hypothetical threats; raise unsettled
+scope decisions under the [agent policy](agents.md).
+
 The [HTTP API](../api.md) owns observable request outcomes, and
 [operations](../operations.md) owns deployment permissions and root selection.
 
@@ -80,6 +115,14 @@ Scriptorium has no durable run-state store, checkpoint, cache, or resume
 mechanism. Recovery is a new request after correcting inputs, configuration, or
 environment.
 
+Each request is self-contained from the caller's perspective, without
+conversation or workflow state retained from completed requests. This does
+not mean the process is internally stateless. Shared engines, backend capacity
+and queue accounting, in-flight coordination, cancellation, and server
+lifecycle resources are permitted and must be shared where necessary to
+enforce configured backend limits across concurrent requests. Such state must
+be concurrency-safe and does not create a durable user-workflow contract.
+
 Adapters map Promptkit public error identities into CLI exits or HTTP statuses
 without classifying by message text. Raw API keys are not accepted in
 Scriptorium configuration, CLI arguments, or HTTP payloads, and resolved
@@ -102,5 +145,7 @@ secrets must not be emitted.
   into Scriptorium.
 - Do not move CLI, inbound HTTP, process, or deployment policy into Promptkit.
 - Do not add durable workflow, archive, or resume behavior.
+- Do not add application-managed prompt modification, follow-up message flows,
+  conversation management, or multi-step workflow orchestration.
 
 Work that is not implemented belongs in `docs/roadmap/`.