Sanctuary v1.3.0-rc.1: Preview of the Castle Architecture stack

Sanctuary v1.3.0-rc.1 is an opt-in preview on the npm next tag. It starts the v1.3 soak while the stable channel stays on the v1.2 line.

Install the preview:

npm install @sanctuary-framework/mcp-server@next

Default installs continue to resolve to npm latest, which remains v1.2.x stable.

What is shippable in this RC

• Castle Wall enforcement: Castle Wall Linux Phase 1 remains the production enforcement baseline, and Castle Wall macOS Phase 1 joins the preview window. (Correction, 2026-08-07: Linux Phase 1 was never a production enforcement baseline, and this RC did not ship Linux kernel enforcement. Open defect: IC-02, IC-03, IC-04. Later evidence, 2026-10-04: a package outside this release was proven on Ubuntu 24.04 (x86-64): a fresh install of the shipped package enforces a signed operator policy per user account: blocked destinations stay blocked and allowed ones connect, through five reboots, on three fresh servers, with the evidence checked by two independent reviewers.)
• Sentinels observation: the Sentinel Baseline Pack is structurally complete, and the Anomaly Detection Pipeline has local classifier state, operator registration UX, feature extractors, and audit-event-class drift detection.
• Charter cooperative MCP: coordination handoff visualization, unified inbox bridge producer wiring plus encrypted persistence, concierge depth, and cross-harness approval inbox surfaces are present for operator evaluation.
• Operator authoring and safety: honeypot authoring includes http_endpoint, filesystem, tool_call, and credential trap classes; English-authored policy gates include compile, activation, and conflict detection; auto-trigger calibration includes ladder state, action classes, and operator-accepted recommendations.
• Principle-closing v1.x work: query-layer anonymity is structurally complete across Tier A and Tier B smart mode; did:web Path C recognition has key rotation on top of issuance, exit-bundle integration, and fortress-config auto-inclusion.
• Infrastructure: the RC includes Sigma hardening waves and Concordia v0.5.1 composition semantics, including RFC 8785 canonicalization, mandate_verification, and DISPUTE_RESOLVED.

Preview-grade areas

This release is not v1.3.0 GA. The RC is meant to soak the Castle Architecture stack under opt-in operators while the coordinator finishes the remaining v1.3 closeout path.

Preview areas to watch closely:

• Anomaly Detection Pipeline behavior under real operator histories.
• Unified inbox noise level and source-class routing.
• Honeypot authoring ergonomics and trap-class false positives.
• Auto-trigger recommendation quality. Promotion remains operator-driven and never autonomous.
• Castle Wall macOS Phase 1 behavior across macOS host configurations.

How to report issues

Open a GitHub issue with:

• Sanctuary version: 1.3.0-rc.1
• Install channel: next
• Host OS and architecture
• Fortress configuration shape, with secrets removed
• Relevant audit event IDs or unified inbox entry IDs
• Whether the issue affects Castle Wall enforcement, Sentinels, anomaly detection, inbox, concierge, honeypots, policy gates, auto-trigger calibration, query anonymity, did:web recognition, or Concordia composition

Do not include raw secrets, private prompts, tokens, or production credentials in the issue body.

Soak criteria before v1.3.0 GA

Before GA, the RC line should show:

• No critical findings in Castle Wall enforcement or no-outbound-by-default behavior.
• No privacy regressions in query-layer anonymity or did:web recognition flows.
• Acceptable operator signal quality in Sentinels, anomaly detection, and unified inbox surfaces.
• No release-blocking persistence, encryption, migration, or fortress-isolation defects.
• Coordinator confirmation that all nine v1.3 work packages meet the GA threshold.

Publish note

The npm publish for this RC must use:

npm publish --access public --tag next

Using --tag next keeps default installs on the v1.2 stable channel while preview operators opt in with @next.