diff --git a/.machine_readable/contractiles/README.adoc b/.machine_readable/contractiles/README.adoc index 952a247b..f37c27bd 100644 --- a/.machine_readable/contractiles/README.adoc +++ b/.machine_readable/contractiles/README.adoc @@ -6,16 +6,18 @@ This directory contains the generalized contractiles templates. Copy the `.machine_readable/contractiles/` directory into a new repo to establish a consistent operational, validation, trust, recovery, and intent framework. -== Fill-In Instructions - -1. Update the Mustfile to reflect your real invariants (paths, schema versions, ports). -2. Replace Trustfile.hs placeholders with your actual key paths and verification commands. -3. Adjust Dustfile handlers to match your rollback and recovery tooling. -4. Update Intentfile to mirror the roadmap you want the system to evolve toward. - == Contents -* `must/Mustfile` - required invariants and validations. -* `trust/Trustfile.hs` - cryptographic verification steps. -* `dust/Dustfile` - rollback and recovery semantics. -* `lust/Intentfile` - future intent and roadmap direction. +Each verb directory holds a Nickel runner, `/.ncl`. The runner names +its paired edict, `file.deed` in the same directory (A7 8.1). None of the +edicts is written yet: the legacy `file.a2ml` contractiles were retired on +2026-11-14 with no mapping spec to translate them +(`docs/history/A2ML-REMOVED.adoc`). Until the edicts exist, the generated +recipes in `contractile.just` stand. + +* `must/must.ncl` - required invariants and validations (edict `Mustfile.deed`). +* `trust/trust.ncl` - provenance, integrity and trust-boundary verification (edict `Trustfile.deed`). +* `dust/dust.ncl` - cleanup policy and recovery paths (edict `Dustfile.deed`). +* `bust/bust.ncl` - declared failure modes and their recovery paths (edict `Bustfile.deed`). +* `intend/intend.ncl` - declared purpose and scope (edict `Intentfile.deed`). +* `adjust/adjust.ncl` - accessibility of user-facing interfaces (edict `Adjustfile.deed`). diff --git a/0-AI-MANIFEST.deed b/0-AI-MANIFEST.deed index ad923de9..1b122998 100644 --- a/0-AI-MANIFEST.deed +++ b/0-AI-MANIFEST.deed @@ -3,13 +3,11 @@ ;; ;; The machine front door of boj-server: pointer-only (A7 ruling Q15). It names ;; where to read and carries no facts of its own. Repository facts are in -;; boj-server_chora.deed; agent conventions are in .claude/CLAUDE.md. It -;; replaces 0-AI-MANIFEST.a2ml, retired 2026-11-14 (docs/history/A2ML-REMOVED.adoc). +;; boj-server_chora.deed, which carries the identity fields; agent conventions +;; are in .claude/CLAUDE.md. It replaces 0-AI-MANIFEST.a2ml, retired 2026-11-14 +;; (docs/history/A2ML-REMOVED.adoc). (repo-deed :schema-version "1.0.0" - :canonical-name "boj-server" - :repo-uuid #u8"gv-clade-index:github.com/hyperpolymath/boj-server" - :beholding-chora #u8"chora:estate/github.com/hyperpolymath" (front-doors :machine "boj-server_chora.deed" :human "README.adoc" diff --git a/docs/EXTENSIBILITY.adoc b/docs/EXTENSIBILITY.adoc index 26d81633..0986618f 100644 --- a/docs/EXTENSIBILITY.adoc +++ b/docs/EXTENSIBILITY.adoc @@ -15,7 +15,7 @@ project itself. > The capability matrix, lifecycle, proof requirements, HAT model, and cartridge > manifest schema are specified normatively in -> link:specification/cartridges/README.md[`docs/specification/cartridges/README.md`]. +> link:specification/cartridges/README.adoc[`docs/specification/cartridges/README.adoc`]. > This document covers the optional *backend (third axis)* extension mechanism only. BoJ organises server capabilities as a sparse matrix: @@ -41,10 +41,17 @@ BoJ organises server capabilities as a sparse matrix: == The Third Axis: Backend -Every cartridge has a `backend` field that defaults to `"universal"`. +Every catalogue entry has a `backend` label that defaults to `"universal"` +(the `backend` field of the `Cartridge` record in `src/abi/Boj/Catalogue.idr`, +set by `boj_catalogue_register` in `ffi/zig/src/catalogue.zig`). Core BoJ cartridges are all universal — they define the capability abstraction without committing to a specific provider. +NOTE: The label lives in the catalogue (Idris2 ABI and Zig FFI), not in +`cartridge.json`. The manifest schema (`schemas/cartridge-v1.json`) has no +`backend` property, so a backend is set at registration time with +`boj_catalogue_set_backend` (see <>). + Community extensions can *specialise* this axis. For example: [cols="1,1,1,1",options="header"] @@ -59,12 +66,12 @@ Community extensions can *specialise* this axis. For example: | universal | Generic database operations -| database-mcp-pg +| database-pg-mcp | Database | postgresql | PostgreSQL-native operations -| database-mcp-sqlite +| database-sqlite-mcp | Database | sqlite | SQLite-native operations @@ -74,7 +81,7 @@ Community extensions can *specialise* this axis. For example: | universal | Generic container operations -| container-mcp-podman +| container-podman-mcp | Container | podman | Podman-specific tooling @@ -95,99 +102,182 @@ and the cartridge behaves exactly as the existing 2D model. To extend BoJ with a backend-specific cartridge: -=== 1. Write an Extension Descriptor +=== 1. Write the Cartridge Manifest -> *Manifest format note (2026-04-17):* The closed decision -> `boj-cartridge-manifest-format-dd.md` establishes *Nickel* (`.ncl`) as the -> authoritative cartridge manifest format. Current on-disk manifests are -> `cartridge.json`. Migration from JSON to Nickel is tracked as future work. -> Until migration is complete, both formats coexist; the JSON schema at -> `https://boj.dev/schemas/cartridge/v1.json` remains the operative validator. +> *Manifest format note:* the cartridge specification +> (link:specification/cartridges/README.adoc[§6, Cartridge Manifest (Nickel)]) +> names *Nickel* (`.ncl`) as the authoritative manifest format; migration is pending. The +> manifests read today are `cartridge.json`. The Elixir catalog +> (`elixir/lib/boj_rest/catalog.ex`) validates each one against the bundled +> schema mirror `schemas/cartridge-v1.json` (see `schemas/SCHEMA-MIRROR.adoc`) +> and rejects a manifest that fails it. -Create a manifest file describing your extension (currently `cartridge.json`; Nickel -`.ncl` is the planned authoritative format): +Create a `cartridge.json` for your extension. Start from +`templates/cartridge-template/cartridge.json`. The name must end in its role +suffix (`-mcp`, `-lsp`, `-dap`, …), so a PostgreSQL specialisation of +`database-mcp` is `database-pg-mcp`, not `database-mcp-pg`. Community +extensions are always the `Ayo` tier. This example validates against +`schemas/cartridge-v1.json`: -[source,toml] +[source,json] ---- -# my-extension.cartridge.json — Extension descriptor for BoJ catalogue -# (Future: migrate to my-extension.ncl in Nickel format) -[extension] -name = "database-mcp-pg" -version = "0.1.0" -domain = "database" # Must match a CapabilityDomain -backend = "postgresql" # Your specialisation -tier = "ayo" # Community extensions are always Ayo tier -protocols = ["mcp", "rest"] # Which protocol columns this fills - -[metadata] -author = "Your Name " -description = "PostgreSQL-native database cartridge for BoJ" -homepage = "https://github.com/you/database-mcp-pg" -hash = "" # SHA-256 of the .so — filled at build time - -[capabilities] -tools = [ - "pg_query", - "pg_schema", - "pg_migrate", -] +{ + "$schema": "https://hyperpolymath.dev/standards/cartridges/cartridge-v1.json", + "spdx": "MPL-2.0", + "copyright": "Copyright (c) 2026 Your Name", + "name": "database-pg-mcp", + "version": "0.1.0", + "description": "PostgreSQL-native database cartridge for BoJ", + "domain": "Database", + "category": "domain", + "tier": "Ayo", + "protocols": ["MCP", "REST"], + "auth": { + "method": "none", + "env_var": null, + "credential_source": null + }, + "api": { + "base_url": "local://database-pg-mcp", + "content_type": "application/json" + }, + "tools": [ + { + "name": "pg_query", + "description": "Run a read-only SQL query.", + "inputSchema": { + "type": "object", + "properties": { + "query": { "type": "string", "description": "SQL query string" } + }, + "required": ["query"] + } + } + ] +} ---- -=== 2. Build a Shared Library +=== 2. Build the Cartridge Library -Your extension compiles to a `.so` (or `.dylib` on macOS) that exports -C-ABI functions matching the BoJ cartridge invoke contract: +A cartridge is three layers: an *Idris2* ABI (the verified contract), a *Zig* +FFI and a *Zig* adapter. The FFI compiles to a shared library (`.so`, or +`.dylib` on macOS) that exports the five C-ABI symbols of ADR-0006 +(`docs/decisions/0006-cartridge-invoke-abi.adoc`). This is the shape of +`templates/cartridge-template/ffi/cartridge_ffi.zig`, built with that +directory's `build.zig`: -[source,c] +[source,zig] ---- -// Required export: -int boj_ext_invoke(const char* tool, const char* params_json, - char* result_buf, size_t result_len); +const shim = @import("cartridge_shim.zig"); + +export fn boj_cartridge_init() callconv(.c) c_int { + return 0; +} + +export fn boj_cartridge_deinit() callconv(.c) void {} + +export fn boj_cartridge_name() callconv(.c) [*:0]const u8 { + return "database-pg-mcp"; +} + +export fn boj_cartridge_version() callconv(.c) [*:0]const u8 { + return "0.1.0"; +} + +// Return codes are frozen by ADR-0006: 0 success, -1 unknown tool, +// -2 bad arguments, -3 buffer too small (*in_out_len set to the size needed). +export fn boj_cartridge_invoke( + tool_name: [*c]const u8, + json_args: [*c]const u8, + out_buf: [*c]u8, + in_out_len: [*c]usize, +) callconv(.c) i32 { + _ = json_args; + if (shim.invokeArgsNull(tool_name, out_buf, in_out_len)) return shim.RC_BAD_ARGS; + const body: []const u8 = if (shim.toolIs(tool_name, "pg_query")) + "{\"result\":{}}" + else + return shim.RC_UNKNOWN_TOOL; + return shim.writeResult(out_buf, in_out_len, body); +} ---- -=== 3. Register via the REST API +`cartridge_shim.zig` is `ffi/zig/src/cartridge_shim.zig`. Cartridges +themselves live in the `boj-server-cartridges` repository; its +`cartridges/templates/gossamer-mcp/` is the minting template, and its +`cartridges/domains/config/k9iser-mcp/adapter/` is the reference unified Zig +adapter. + +=== 3. Submit via the REST API + +The submission endpoint is specified in `docs/specification/openapi.yaml` +(`POST /community/submit`, body `CommunitySubmission`), and +`config/gateway-policy-boj.yaml` exposes it only to authenticated callers. + +IMPORTANT: The Elixir REST server (`elixir/lib/boj_rest/router.ex`) does not +serve this route yet; a request falls through to its `route-not-found` 404. +The review state machine itself is implemented in `ffi/zig/src/community.zig`. -Submit your extension to a running BoJ node: +Once the route is served, a submission looks like this, with `BOJ_URL` the +node's REST endpoint (see `.env.example`): [source,bash] ---- -curl -X POST http://localhost:7700/community/submit \ +curl -X POST "$BOJ_URL/community/submit" \ -H 'Content-Type: application/json' \ -d '{ - "name": "database-mcp-pg", + "name": "database-pg-mcp", "author": "Your Name ", - "description": "PostgreSQL-native database cartridge", - "hash": "a1b2c3...64-char-sha256" + "repository": "https://github.com/you/database-pg-mcp" }' ---- -The node operator reviews the submission via the Ayo tier state machine -(submitted → under_review → approved/rejected). +The node operator reviews the submission through the Ayo-tier review state +machine in `ffi/zig/src/community.zig` +(submitted → under_review → approved / rejected, or suspended). +[[register-ffi]] === 4. Register Programmatically (FFI) -If you are building against the BoJ static library: +If you link against the BoJ catalogue library, call the C ABI that +`ffi/zig/src/catalogue.zig` exports. From Zig: -[source,c] +[source,zig] ---- -#include "boj_catalogue.h" - -boj_catalogue_register("database-mcp-pg", 15, "0.1.0", 5, - 1, /* ready */ - 2, /* ayo tier */ - 3); /* database domain */ -boj_catalogue_set_backend("postgresql", 10); -boj_catalogue_add_protocol(1); /* MCP */ -boj_catalogue_add_protocol(9); /* REST */ +extern fn boj_catalogue_init() c_int; +extern fn boj_catalogue_register( + name_ptr: [*]const u8, + name_len: usize, + version_ptr: [*]const u8, + version_len: usize, + status: c_int, // BOJ_STATUS_*: 1 = ready + tier: c_int, // BOJ_TIER_*: 2 = ayo + domain: c_int, // BOJ_DOMAIN_*: 3 = database +) c_int; +extern fn boj_catalogue_set_backend(backend_ptr: [*]const u8, backend_len: usize) c_int; +extern fn boj_catalogue_add_protocol(protocol: c_int) c_int; + +fn registerPg() bool { + if (boj_catalogue_init() != 0) return false; + const name = "database-pg-mcp"; + const version = "0.1.0"; + const backend = "postgresql"; + if (boj_catalogue_register(name.ptr, name.len, version.ptr, version.len, 1, 2, 3) != 0) return false; + if (boj_catalogue_set_backend(backend.ptr, backend.len) != 0) return false; + if (boj_catalogue_add_protocol(1) != 0) return false; // BOJ_PROTO_MCP + return boj_catalogue_add_protocol(9) == 0; // BOJ_PROTO_REST +} ---- +The constant values are those in `generated/abi/boj_catalogue.h`. + == What This Is Not This extensibility mechanism is *not*: * A plugin system with dynamic loading (extensions are static .so files) * A marketplace or registry (BoJ does not host or distribute extensions) -* A scope increase (core BoJ remains the 18 universal cartridges) +* A scope increase (core BoJ cartridges stay universal) * A commitment to support arbitrary backends It is simply a *designed seam* in the type system that allows the @@ -198,39 +288,44 @@ on the backend dimension. == Querying Extensions -The Teranga menu JSON includes the `backend` field: +The catalogue's menu JSON, written by `boj_menu_json` in +`ffi/zig/src/catalogue.zig`, carries each entry's `backend` label: [source,json] ---- { "menu": "teranga", + "version": "0.1.0", "cartridges": [ { "name": "database-mcp", - "backend": "universal", + "version": "0.1.0", "tier": "teranga", + "status": "ready", + "backend": "universal", + "available": true, "protocols": ["mcp", "rest"] }, { - "name": "database-mcp-pg", - "backend": "postgresql", + "name": "database-pg-mcp", + "version": "0.1.0", "tier": "ayo", + "status": "ready", + "backend": "postgresql", + "available": true, "protocols": ["mcp", "rest"] } ] } ---- -The REST API also supports backend queries: - -[source,bash] ----- -# List all database cartridges (any backend) -curl http://localhost:7700/cartridges?domain=database +To read one entry's label, call `boj_menu_backend` (below). In the Idris2 ABI, +`byBackend` filters a list of cartridges by label. -# List only PostgreSQL-specialised cartridges -curl http://localhost:7700/cartridges?domain=database&backend=postgresql ----- +NOTE: The REST surface does not expose the backend label yet. `GET /menu` in +`elixir/lib/boj_rest/router.ex` groups manifests by tier with no `backend` +field, and `GET /cartridges` returns only the cartridge names and a count; it +takes no `domain` or `backend` query parameters. == Idris2 ABI @@ -260,11 +355,16 @@ byBackend : String -> List Cartridge -> List Cartridge == Zig FFI +The two backend exports of `ffi/zig/src/catalogue.zig`, as a caller declares +them: + [source,zig] ---- -// Set backend for the last registered cartridge (default: "universal") -pub export fn boj_catalogue_set_backend(ptr: [*]const u8, len: usize) c_int; +// Set the backend label (at most 32 bytes) of the last registered cartridge. +// The label is "universal" until this is called. Returns 0, or -1 on error. +extern fn boj_catalogue_set_backend(backend_ptr: [*]const u8, backend_len: usize) c_int; -// Query backend label for a cartridge by index -pub export fn boj_menu_backend(index: usize, out_ptr: [*]u8, out_len: usize) usize; +// Copy the backend label of the cartridge at `index` into out_ptr. +// Returns the number of bytes copied, or 0 on error. +extern fn boj_menu_backend(index: usize, out_ptr: [*]u8, out_len: usize) usize; ---- diff --git a/docs/integration/gateway-load-profile.adoc b/docs/integration/gateway-load-profile.adoc index 19910436..09aebd4c 100644 --- a/docs/integration/gateway-load-profile.adoc +++ b/docs/integration/gateway-load-profile.adoc @@ -64,7 +64,9 @@ gateway treats BoJ as a single backend with opaque cost; the gateway-side perf contract isolates gateway-attributable cost only. * Cloudflare-edge load shaping (tier 1) and BEAM-supervisor back-pressure (tier 3). Both are covered separately in -`+Trustfile.a2ml [CLOUDFLARE_EDGE_SECURITY]+`. +the `+[CLOUDFLARE_EDGE_SECURITY]+` section of the retired `+Trustfile.a2ml+` +(`+docs/history/A2ML-REMOVED.adoc+`; its successor `+Trustfile.deed+` is not +yet written). ''''' diff --git a/docs/integration/gateway-observability-spec.adoc b/docs/integration/gateway-observability-spec.adoc index 7a75ecac..d33e05d3 100644 --- a/docs/integration/gateway-observability-spec.adoc +++ b/docs/integration/gateway-observability-spec.adoc @@ -79,7 +79,9 @@ URL, the on-call rota). This spec gives the operator the queries; choosing the dashboard tool (Grafana / Cloudflare analytics / something else) is owner-driven per the runbook’s existing scoping. * Cloudflare-edge metrics (tier 1). Covered separately in -`+Trustfile.a2ml [CLOUDFLARE_EDGE_SECURITY]+`. +the `+[CLOUDFLARE_EDGE_SECURITY]+` section of the retired `+Trustfile.a2ml+` +(`+docs/history/A2ML-REMOVED.adoc+`; its successor `+Trustfile.deed+` is not +yet written). * BoJ-internal cartridge or cartridge-tool metrics. The gateway sees BoJ as a single backend; cartridge-level observability is downstream. * Long-term storage / retention policy. The spec defines what to scrape; diff --git a/docs/integration/http-capability-gateway-boj-contract.adoc b/docs/integration/http-capability-gateway-boj-contract.adoc index 69878a07..47e59139 100644 --- a/docs/integration/http-capability-gateway-boj-contract.adoc +++ b/docs/integration/http-capability-gateway-boj-contract.adoc @@ -12,7 +12,8 @@ ____ (`+http-capability-gateway-policy-authoring.md+`) are kept as `+.md+`, not `+.adoc+`, deliberately: the integration plan normatively prescribes the path `+docs/integration/http-capability-gateway-boj-contract.md+`, -the Phase C Trustfile `+[SEAMS]+` entry will reference that exact path, +the Phase C seam declaration (the `+gateway-boj-gnosis+` entry, planned for +`+Trustfile.deed+`, not yet written) will reference that exact path, and the entire `+docs/integration/+` + `+docs/decisions/+` doc-set is Markdown. Faithfulness to the normatively-referenced path outweighs the estate `+.adoc+` default here. @@ -195,7 +196,7 @@ signal. verbatim |BoJ unreachable / connection refused |circuit breaker trips → *503 -Service Unavailable* |fail-closed; matches Trustfile `+[SEAMS]+` +Service Unavailable* |fail-closed; matches the Phase C seam declaration `+failure_mode: "fail-closed (circuit breaker)"+` |Verb not permitted by policy |*403* (or stealth status, see §6) diff --git a/docs/integration/http-capability-gateway-plan.adoc b/docs/integration/http-capability-gateway-plan.adoc index 9cf29cab..5766df0d 100644 --- a/docs/integration/http-capability-gateway-plan.adoc +++ b/docs/integration/http-capability-gateway-plan.adoc @@ -264,9 +264,12 @@ successfully, `+compile/2+` succeeds and `+lookup/3+` never returns path+verb denied under trust level T, it is also denied under any T’ < T (monotonicity of denial preserved through the full pipeline). -*C3 — Seam declaration in BoJ Trustfile* +*C3 — Seam declaration in the BoJ trust edict* -Add to `+[SEAMS]+` in `+Trustfile.a2ml+`: +Declare the seam in `+Trustfile.deed+`, the trust edict paired with +`+.machine_readable/contractiles/trust/trust.ncl+` (not yet written). The +entry below stood in `+[SEAMS]+` of the retired `+Trustfile.a2ml+` +(`+docs/history/A2ML-REMOVED.adoc+`) and is the content to carry over: [source,yaml] ---- @@ -287,7 +290,7 @@ Add to `+[SEAMS]+` in `+Trustfile.a2ml+`: * Seam test (C1) exercises the HTTP contract from Phase A: headers set correctly, trust level forwarded, response returned to caller. * Property tests (C2) pass with at least 200 samples. -* Seam declared in Trustfile. +* Seam declared in `+Trustfile.deed+`. ==== Risks @@ -445,8 +448,8 @@ hours without circuit breaker trips or elevated error rates. once in staging before production rollout). * Production rollout complete with no SLA regression (latency at p99 within D2 declared overhead + 20% safety margin). -* `+[HTTP_CAPABILITY_GATEWAY]+` section in BoJ Trustfile updated to -`+status: "DEPLOYED"+` with `+deployed_at+` timestamp. +* The "Tier-2 gateway status" item in `+docs/status/ROADMAP.adoc+` flipped to +`+DEPLOYED+`, with the date, per the rollout runbook §6.4. ==== Risks diff --git a/docs/maintenance/MAINTENANCE-CHECKLIST.adoc b/docs/maintenance/MAINTENANCE-CHECKLIST.adoc index eb1fddae..a02362cf 100644 --- a/docs/maintenance/MAINTENANCE-CHECKLIST.adoc +++ b/docs/maintenance/MAINTENANCE-CHECKLIST.adoc @@ -120,7 +120,8 @@ compatibility) ** `+bot_directives/+` for bot control files * [ ] Keep contractiles/invariants present and wired: ** root `+Mustfile+` (or equivalent) with enforceable checks -** `+Trustfile+` and `+Intentfile+` present +** the `+trust+` and `+intend+` contractile runners present, with their edicts +(`+Trustfile.deed+`, `+Intentfile.deed+`) once written * [ ] Keep security metadata present: ** `+.well-known/security.txt+` and relevant policy metadata ** CI security scanning configured and runnable @@ -478,7 +479,8 @@ to `+docs/+` subtrees). * [x] Human-readable docs synchronized (`+README+`, `+QUICK_STATUS+`, roadmap, wiki home). * [x] `+Mustfile+` invariants present and enforceable in CI. -* [x] `+Trustfile+` and `+Intentfile+` present and complete. +* [ ] `+Trustfile.deed+` and `+Intentfile.deed+` present and complete (not yet +written; the `+.a2ml+` forms were retired 2026-11-14). * [x] FFI/ABI purity policy enforced (`+*.zig+` for FFI, `+*.idr+`/Idris2 for ABI). * [x] `+panic-attack+` findings triaged with explicit severity budget diff --git a/docs/planning/v1-critical-chain-2026-06-11.adoc b/docs/planning/v1-critical-chain-2026-06-11.adoc index 9f722161..73112c55 100644 --- a/docs/planning/v1-critical-chain-2026-06-11.adoc +++ b/docs/planning/v1-critical-chain-2026-06-11.adoc @@ -186,7 +186,8 @@ unblocks the entire tier-2 story. B3. *HCG Phase E rollout* per the existing runbook (`docs/integration/hcg-tier2-rollout-runbook.md`) — staging cut-over, -soak, 10/50/100%, Trustfile flip. The `!OWNER:` markers in §1.3/§4 need +soak, 10/50/100%, tier-2 status flip (now in `docs/status/ROADMAP.adoc`; +the Trustfile that held it was retired 2026-11-14). The `!OWNER:` markers in §1.3/§4 need owner decisions (on-call rota, cert paths, traffic-shift mechanism). B4. *Credential forwarding stays Options A+B for v1.* Option C (RGTV diff --git a/elixir/README.adoc b/elixir/README.adoc index 2cca9dd8..365d0571 100644 --- a/elixir/README.adoc +++ b/elixir/README.adoc @@ -106,4 +106,6 @@ Configure via env vars: *Accepted; production-wiring is a tracked programme — ADR-0004 estimates 8–12 weeks (mTLS-as-primary, E2E, benchmarks). Until then this core stays internal/loopback-bound.* -. **Phase 4 — mTLS / SDP.** Per `Trustfile.a2ml` `[SDP_RULES]`. +. **Phase 4 — mTLS / SDP.** Per the `[SDP_RULES]` section of the retired + `Trustfile.a2ml` (`docs/history/A2ML-REMOVED.adoc`); its successor, + `Trustfile.deed`, is not yet written.