rcf-lite 0.29.0 → 0.31.0

package/blueprints/object-storage-s3/contributions/user-stories/object-storage-s3-us-28105.json

@@ -20,7 +20,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-2903-object-storage-s3-event-sink",
-        "field": "interfaces.onEvent"
+        "field": "interfaces[onEvent]"
       }
     },
     {
@@ -33,7 +33,7 @@
       "scope": "runtime",
       "ownerRef": {
         "tacId": "TAC-2903-object-storage-s3-event-sink",
-        "field": "interfaces.onEvent"
+        "field": "interfaces[onEvent]"
       },
       "disposition": "fixed"
     }

package/blueprints/object-storage-s3/contributions/user-stories/object-storage-s3-us-28106.json

@@ -20,7 +20,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-2901-object-storage-s3-facade",
-        "field": "interfaces.createObjectStore"
+        "field": "interfaces[createObjectStore]"
       }
     },
     {

package/blueprints/object-storage-s3/contributions/user-stories/object-storage-s3-us-28110.json

@@ -29,7 +29,7 @@
       "scope": "runtime",
       "ownerRef": {
         "tacId": "TAC-2904-object-storage-s3-hetzner-endpoint-helper",
-        "field": "interfaces.composeHetznerEndpoint"
+        "field": "interfaces[composeHetznerEndpoint]"
       },
       "disposition": "template"
     }

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-001.json

@@ -5,7 +5,7 @@
   "description": "The application serves a liveness probe endpoint at a project-supplied HTTP path. A 2xx response means the process is running its event loop and is not wedged; a 5xx response means the process is stuck and the orchestrator should restart it. The endpoint answer never depends on any external dependency: a database outage, a broker outage or a partner API outage never turns liveness red on its own. The endpoint runs entirely inside the process boundary. The liveness path is supplied by project configuration under probeInterface.paths.liveness; when observability-probe-endpoints is composed on the same project the resolved profile liveness path binds automatically (Kubernetes profile default /live). Essentials-alone projects supply the one config line at boot and the blueprint refuses boot with a stable-coded error when it is missing.",
   "deliveredBy": {
     "tacId": "TAC-801-observability-essentials-liveness-probe",
-    "field": "interfaces.createLivenessHandler"
+    "field": "interfaces[createLivenessHandler]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-002.json

@@ -5,7 +5,7 @@
   "description": "The application serves a readiness probe endpoint at a project-supplied HTTP path distinct from the liveness path. A 2xx response means the process is ready to accept request traffic; a 5xx response means the orchestrator should stop routing traffic to this replica while the process itself remains up. The readiness answer aggregates the health of the specific dependencies the process needs to serve requests correctly, evaluated through non-blocking cached checks that never hang the endpoint on a slow dep. The readiness path is supplied by project configuration under probeInterface.paths.readiness; when observability-probe-endpoints is composed on the same project the resolved profile readiness path binds automatically (Kubernetes profile default /ready). Essentials-alone projects supply the one config line at boot and the blueprint refuses boot with a stable-coded error when it is missing.",
   "deliveredBy": {
     "tacId": "TAC-802-observability-essentials-readiness-probe",
-    "field": "interfaces.createReadinessHandler"
+    "field": "interfaces[createReadinessHandler]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-003.json

@@ -5,7 +5,7 @@
   "description": "The set of dependencies whose health contributes to the readiness answer is declared at boot from application configuration. Each declared dependency has a stable string name that appears in the readiness probe's structured response body under a checks field, alongside its individual pass/fail state and the timestamp of the last check evaluation. Dependencies not declared in the readiness set never appear in the probe response, never affect readiness, and are surfaced to operators only through the status page or the notification outcome record.",
   "deliveredBy": {
     "tacId": "TAC-802-observability-essentials-readiness-probe",
-    "field": "interfaces.dependencyRegistry"
+    "field": "interfaces[dependencyRegistry]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-004.json

@@ -5,7 +5,7 @@
   "description": "The application serves a public status page at a stable HTTP path intended for external readers (users, partners, unauthenticated visitors). The page renders a list of declared components (subsystems the project chooses to publish state for), each with a current state field from a fixed enum (operational, degraded, outage, maintenance) and a human-readable component name. The page has no login gate. The component list, the enum, and the display order are declared at boot from application configuration; no component appears on the page that was not declared.",
   "deliveredBy": {
     "tacId": "TAC-803-observability-essentials-status-page",
-    "field": "interfaces.componentRegistry"
+    "field": "interfaces[componentRegistry]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-005.json

@@ -5,7 +5,7 @@
   "description": "When the operator has posted one or more active incident notices, the status page renders them above the component list. Each notice carries a title (short human string), a body (longer human string), a severity from a fixed enum (info, warning, critical), a startedAt ISO-8601 timestamp, and an optional componentIds array naming which declared components the notice relates to. When no notices are active, the notice region is either absent from the rendered page or clearly labelled as empty; no phantom notices, no stale notices carried over from a previous incident.",
   "deliveredBy": {
     "tacId": "TAC-803-observability-essentials-status-page",
-    "field": "interfaces.noticeReader"
+    "field": "interfaces[noticeReader]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-006.json

@@ -5,7 +5,7 @@
   "description": "The application records the outcome of every notification it attempts to send (email, SMS, push, webhook, or any other channel the project ships) as a structured record on a durable outcome sink. Each record carries a notification identifier, a channel name from a fixed enum, a recipient identifier, an outcome from a fixed enum (delivered, failed, pending, suppressed), an attemptedAt ISO-8601 timestamp, and an optional errorCode string when the outcome is failed. An operator queries the sink by recipient identifier and time window and receives the outcome records that match. Notifications never succeed silently: an attempt with no recorded outcome is a defect the project must gate against. The elicited notification-outcome-substrate is one of three named values whose runtime behaviour this blueprint pins: `sqlite` persists outcome records to a process-local SQLite file at the project-configured path and MUST survive a process restart (AC-7106-4 exercises the restart path against a sqlite path); `postgres` persists outcome records to a PostgreSQL server the project connects to and MUST survive a stop-and-start of that server (AC-7106-4 exercises the restart path against a postgres server); `custom` accepts a project-supplied substrate module conforming to the sink interface on TAC-804 whose implementation guarantees the same restart-survival semantics as the shipped `sqlite` and `postgres` branches (AC-7106-4 and AC-7106-5 exercise the branch through the same TAC-804 interface). Every substrate value the elicit accepts is backed by this runtime clause; a substrate not named here is not accepted at boot.",
   "deliveredBy": {
     "tacId": "TAC-804-observability-essentials-notification-outcome",
-    "field": "interfaces.createOutcomeSink"
+    "field": "interfaces[createOutcomeSink]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-007.json

@@ -5,7 +5,7 @@
   "description": "The liveness and readiness probe endpoints respond with a JSON body carrying a stable shape: a status field (one of pass or fail), a checkedAt field with an ISO-8601 timestamp of when the probe body was evaluated, and, on the readiness probe, a checks field mapping declared-dependency name to that dependency individual pass/fail. The response header naming the media type is the one owned on TAC-801-observability-essentials-liveness-probe.responsibilities[1]. Field names do not change across patch or minor versions of the blueprint; a change is a major version bump.",
   "deliveredBy": {
     "tacId": "TAC-802-observability-essentials-readiness-probe",
-    "field": "interfaces.createReadinessHandler"
+    "field": "interfaces[createReadinessHandler]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-008.json

@@ -5,7 +5,7 @@
   "description": "The liveness probe, the readiness probe, and the public status page respond to unauthenticated HTTP requests. No cookie, no header, no source-IP allowlist gates access to these three surfaces. The three paths are declared at boot as auth-exempt in whatever authentication middleware the application uses, and that exemption is the only auth policy the surfaces run under.",
   "deliveredBy": {
     "adrId": "ADR-804-observability-essentials-probe-secrecy",
-    "field": "decision.probeSecrecy"
+    "field": "decision"
   },
   "category": "nonFunctional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-009.json

@@ -5,7 +5,7 @@
   "description": "The public status page renders only the declared component list and their per-component states, plus the active incident notices. It never renders internal identifiers (host names, replica ids, database identifiers, queue names), never renders raw metric values (request counts, latency numbers, error rates), and never names the specific dependencies that failed a readiness check. The status enum values, the component names, and the incident notice fields are the public vocabulary; anything more granular is operator-only surface, exposed through the readiness probe body or an authenticated operator dashboard.",
   "deliveredBy": {
     "adrId": "ADR-803-observability-essentials-status-page-contract",
-    "field": "decision.statusPageContract"
+    "field": "decision"
   },
   "category": "security",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/requirements/observability-essentials-req-010.json

@@ -5,7 +5,7 @@
   "description": "The liveness probe handler completes its evaluation entirely in-process and returns without issuing any network call. The readiness probe handler completes within a bounded ceiling (the readiness evaluation budget, declared at boot with a documented default) and never blocks on a synchronous network round trip to a declared dependency: readiness checks read from a per-dependency last-known state that a background evaluator refreshes on its own cadence. A slow or hanging downstream dependency causes the last-known state for that dependency to age or fail, not the probe handler itself to hang.",
   "deliveredBy": {
     "tacId": "TAC-802-observability-essentials-readiness-probe",
-    "field": "interfaces.createReadinessHandler"
+    "field": "interfaces[createReadinessHandler]"
   },
   "category": "nonFunctional",
   "domain": "observability",

package/blueprints/observability-essentials/contributions/tacs/tac-801-observability-essentials-liveness-probe.json

@@ -17,13 +17,13 @@
   "interfaces": [
     {
       "name": "createLivenessHandler",
-      "kind": "factory",
-      "description": "createLivenessHandler({ path, now }) -> { path, handler }. Returns the configured probe path and a stateless async handler for it. Called once at boot; the returned handler is bound at the HTTP router. `path` is a REQUIRED configuration input with no shipped default; when it is missing the caller refuses boot with PROBE_INTERFACE_PATHS_MISSING."
+      "kind": "other",
+      "description": "createLivenessHandler({ path, now }) -> { path, handler }. Returns the configured probe path and a stateless async handler for it. Called once at boot; the returned handler is bound at the HTTP router. `path` is a REQUIRED configuration input with no shipped default; when it is missing the caller refuses boot with PROBE_INTERFACE_PATHS_MISSING. (legacy kind: factory)"
     },
     {
       "name": "livenessPath",
-      "kind": "config",
-      "description": "Configured liveness HTTP path supplied by the project under probeInterface.paths.liveness. There is no shipped default in essentials v2.0.0. When observability-probe-endpoints is composed, the resolved profile liveness path substitutes for this configuration entry automatically; essentials-alone projects supply it explicitly at boot."
+      "kind": "other",
+      "description": "Configured liveness HTTP path supplied by the project under probeInterface.paths.liveness. There is no shipped default in essentials v2.0.0. When observability-probe-endpoints is composed, the resolved profile liveness path substitutes for this configuration entry automatically; essentials-alone projects supply it explicitly at boot. (legacy kind: config)"
     }
   ],
   "dependencies": [],

package/blueprints/observability-essentials/contributions/tacs/tac-802-observability-essentials-readiness-probe.json

@@ -18,33 +18,33 @@
   "interfaces": [
     {
       "name": "createReadinessHandler",
-      "kind": "factory",
-      "description": "createReadinessHandler({ path, registry, budgetMs, now }) -> { path, handler }. Returns the configured readiness path and a handler that reads only from the evaluator snapshot(); never blocks on a network call. `path` is a REQUIRED configuration input with no shipped default; when it is missing the caller refuses boot with PROBE_INTERFACE_PATHS_MISSING."
+      "kind": "other",
+      "description": "createReadinessHandler({ path, registry, budgetMs, now }) -> { path, handler }. Returns the configured readiness path and a handler that reads only from the evaluator snapshot(); never blocks on a network call. `path` is a REQUIRED configuration input with no shipped default; when it is missing the caller refuses boot with PROBE_INTERFACE_PATHS_MISSING. (legacy kind: factory)"
     },
     {
       "name": "createEvaluator",
-      "kind": "factory",
-      "description": "createEvaluator({ registry, cadenceMs, checkFor, now }) -> { start, stop, snapshot }. The background evaluator; start() and stop() control the loop, snapshot() exposes the last-known state to the handler."
+      "kind": "other",
+      "description": "createEvaluator({ registry, cadenceMs, checkFor, now }) -> { start, stop, snapshot }. The background evaluator; start() and stop() control the loop, snapshot() exposes the last-known state to the handler. (legacy kind: factory)"
     },
     {
       "name": "dependencyRegistry",
-      "kind": "config",
-      "description": "Declared readiness dependency set loaded at boot: a list of { name, evaluateBudgetMs? } entries. The names are the probe response checks-object keys."
+      "kind": "other",
+      "description": "Declared readiness dependency set loaded at boot: a list of { name, evaluateBudgetMs? } entries. The names are the probe response checks-object keys. (legacy kind: config)"
     },
     {
       "name": "readinessPath",
-      "kind": "config",
-      "description": "Configured readiness HTTP path supplied by the project under probeInterface.paths.readiness. There is no shipped default in essentials v2.0.0. When observability-probe-endpoints is composed, the resolved profile readiness path substitutes for this configuration entry automatically; essentials-alone projects supply it explicitly at boot."
+      "kind": "other",
+      "description": "Configured readiness HTTP path supplied by the project under probeInterface.paths.readiness. There is no shipped default in essentials v2.0.0. When observability-probe-endpoints is composed, the resolved profile readiness path substitutes for this configuration entry automatically; essentials-alone projects supply it explicitly at boot. (legacy kind: config)"
     },
     {
       "name": "checkFor",
-      "kind": "callback",
-      "description": "Project-supplied per-dependency probe: (name) -> Promise<{ state: pass or fail, checkedAt: <ISO-8601> }>. Called by the evaluator, not by the handler."
+      "kind": "other",
+      "description": "Project-supplied per-dependency probe: (name) -> Promise<{ state: pass or fail, checkedAt: <ISO-8601> }>. Called by the evaluator, not by the handler. (legacy kind: callback)"
     },
     {
       "name": "probeBodyShapeCompatibility",
-      "kind": "compatibility-contract",
-      "description": "Cross-probe response body shape compatibility. Owns the release-time check that compares a candidate release's /live and /ready response bodies against the checked-in v2 baseline snapshot at blueprints/observability-essentials/assets/probe-samples/probe-response-baseline.v2.json. A field name or JSON type present on the baseline that a candidate renames or removes is refused with the stable error code PROBE_BODY_SHAPE_DRIFT naming the offending field; a candidate that adds fields without renaming or removing any passes. TAC-802 hosts the contract because the readiness body is the richer of the two shapes; TAC-801's liveness body is jointly covered by the same contract."
+      "kind": "other",
+      "description": "Cross-probe response body shape compatibility. Owns the release-time check that compares a candidate release's /live and /ready response bodies against the checked-in v2 baseline snapshot at blueprints/observability-essentials/assets/probe-samples/probe-response-baseline.v2.json. A field name or JSON type present on the baseline that a candidate renames or removes is refused with the stable error code PROBE_BODY_SHAPE_DRIFT naming the offending field; a candidate that adds fields without renaming or removing any passes. TAC-802 hosts the contract because the readiness body is the richer of the two shapes; TAC-801's liveness body is jointly covered by the same contract. (legacy kind: compatibility-contract)"
     }
   ],
   "dependencies": [],

package/blueprints/observability-essentials/contributions/tacs/tac-803-observability-essentials-status-page.json

@@ -16,18 +16,18 @@
   "interfaces": [
     {
       "name": "createStatusPageHandler",
-      "kind": "factory",
-      "description": "createStatusPageHandler({ path, componentRegistry, noticeReader, now }) -> { path, handler }. Returns the configured status path and a handler that renders the declared components and the notices reader's current notices."
+      "kind": "other",
+      "description": "createStatusPageHandler({ path, componentRegistry, noticeReader, now }) -> { path, handler }. Returns the configured status path and a handler that renders the declared components and the notices reader's current notices. (legacy kind: factory)"
     },
     {
       "name": "componentRegistry",
-      "kind": "config",
-      "description": "Declared component list loaded at boot: an ordered list of { name, currentState? } entries. currentState may be static (operator-updated via a project-authored side channel) or read via a per-component reader function the project supplies."
+      "kind": "other",
+      "description": "Declared component list loaded at boot: an ordered list of { name, currentState? } entries. currentState may be static (operator-updated via a project-authored side channel) or read via a per-component reader function the project supplies. (legacy kind: config)"
     },
     {
       "name": "noticeReader",
-      "kind": "callback",
-      "description": "Project-supplied async () -> Notice[] returning the current active notice list. Each Notice has { title, body, severity, startedAt, componentIds? } fields."
+      "kind": "other",
+      "description": "Project-supplied async () -> Notice[] returning the current active notice list. Each Notice has { title, body, severity, startedAt, componentIds? } fields. (legacy kind: callback)"
     }
   ],
   "dependencies": [],

package/blueprints/observability-essentials/contributions/tacs/tac-804-observability-essentials-notification-outcome.json

@@ -16,23 +16,23 @@
   "interfaces": [
     {
       "name": "createOutcomeSink",
-      "kind": "factory",
-      "description": "createOutcomeSink({ substrate, channelEnum, now }) -> { recordOutcome, queryByRecipient }. Returns the sink's write and read verbs bound to the project-owned substrate."
+      "kind": "other",
+      "description": "createOutcomeSink({ substrate, channelEnum, now }) -> { recordOutcome, queryByRecipient }. Returns the sink's write and read verbs bound to the project-owned substrate. (legacy kind: factory)"
     },
     {
       "name": "recordOutcome",
-      "kind": "write-api",
-      "description": "recordOutcome({ notificationId, channel, recipient, outcome, attemptedAt, errorCode? }) -> Promise<void>; refuses on unknown channel or unknown outcome with a stable error code."
+      "kind": "other",
+      "description": "recordOutcome({ notificationId, channel, recipient, outcome, attemptedAt, errorCode? }) -> Promise<void>; refuses on unknown channel or unknown outcome with a stable error code. (legacy kind: write-api)"
     },
     {
       "name": "queryByRecipient",
-      "kind": "read-api",
-      "description": "queryByRecipient(recipient, { from, to }) -> Promise<OutcomeRecord[]>; returns matching records; empty array on no match."
+      "kind": "other",
+      "description": "queryByRecipient(recipient, { from, to }) -> Promise<OutcomeRecord[]>; returns matching records; empty array on no match. (legacy kind: read-api)"
     },
     {
       "name": "substrate",
-      "kind": "callback",
-      "description": "Project-supplied durable writer: { append(record) -> Promise<void>, queryByRecipient(recipient, window) -> Promise<OutcomeRecord[]> }. When composing with the persistence-data-sqlite blueprint, this is a facade verb on that store."
+      "kind": "other",
+      "description": "Project-supplied durable writer: { append(record) -> Promise<void>, queryByRecipient(recipient, window) -> Promise<OutcomeRecord[]> }. When composing with the persistence-data-sqlite blueprint, this is a facade verb on that store. (legacy kind: callback)"
     }
   ],
   "dependencies": [],

package/blueprints/observability-essentials/contributions/user-stories/observability-essentials-us-7101.json

@@ -60,7 +60,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-801-observability-essentials-liveness-probe",
-        "field": "interfaces.createLivenessHandler"
+        "field": "interfaces[createLivenessHandler]"
       }
     }
   ],

package/blueprints/observability-essentials/contributions/user-stories/observability-essentials-us-7103.json

@@ -50,7 +50,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-802-observability-essentials-readiness-probe",
-        "field": "interfaces.dependencyRegistry"
+        "field": "interfaces[dependencyRegistry]"
       }
     },
     {
@@ -64,7 +64,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-802-observability-essentials-readiness-probe",
-        "field": "interfaces.dependencyRegistry"
+        "field": "interfaces[dependencyRegistry]"
       }
     },
     {
@@ -78,7 +78,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-802-observability-essentials-readiness-probe",
-        "field": "interfaces.dependencyRegistry"
+        "field": "interfaces[dependencyRegistry]"
       }
     }
   ],

package/blueprints/observability-essentials/contributions/user-stories/observability-essentials-us-7106.json

@@ -50,7 +50,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-804-observability-essentials-notification-outcome",
-        "field": "interfaces.createOutcomeSink"
+        "field": "interfaces[createOutcomeSink]"
       }
     },
     {
@@ -64,7 +64,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-804-observability-essentials-notification-outcome",
-        "field": "interfaces.recordOutcome"
+        "field": "interfaces[recordOutcome]"
       }
     }
   ],

package/blueprints/observability-essentials/contributions/user-stories/observability-essentials-us-7107.json

@@ -40,7 +40,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-802-observability-essentials-readiness-probe",
-        "field": "interfaces.probeBodyShapeCompatibility"
+        "field": "interfaces[probeBodyShapeCompatibility]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-001.json

@@ -5,7 +5,7 @@
   "description": "Every log emission from the applying application passes through the logger factory contract TAC-1601 produces, writes one JSON object per line to standard output, and includes at minimum the fields message (string), level (one of the level vocabulary in ADR-1604), timestamp (ISO-8601 with millisecond precision), correlationId (string, may be null when no ambient context), environment (string), serviceName (string) and serviceVersion (string). This stream is the shelf provider of the `auditLog` capability: applied consumers (application-admin-console at AC-21105-1) read audit-relevant emissions from the same stream, so an audit-shaped payload with the caller-supplied actor, target, before and after fields folds onto the top level of the same JSON object. A log emission that fails to serialise (a function reference, a circular reference) is caught, dropped with a one-time stderr notice, and the calling code path continues; a BigInt value is folded to its decimal string form per ADR-1605 and the emission proceeds; a serialisation failure never crashes the service.",
   "deliveredBy": {
     "tacId": "TAC-1601-observability-logging-logger-factory",
-    "field": "interfaces.Logger"
+    "field": "interfaces[Logger]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-002.json

@@ -5,7 +5,7 @@
   "description": "The application reads a correlation identifier from an inbound request header (name governed by ADR-1602; default X-Correlation-Id, elicited per project), threads it through the request-scoped context using the mechanism the TAC exposes, includes it on every log line emitted during that request, and reflects it on any outbound request initiated inside the same context. When no inbound identifier is present, the application mints a v4 UUID and treats it as the ambient value. Requests processed with no ambient context (a scheduled task boot, a background worker startup line) log with correlationId equal to null; the field is always present.",
   "deliveredBy": {
     "tacId": "TAC-1601-observability-logging-logger-factory",
-    "field": "interfaces.correlationHeader"
+    "field": "interfaces[correlationHeader]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-003.json

@@ -5,7 +5,7 @@
   "description": "The logger factory exposes a redaction contract (ADR-1603 recommended-default categories: credential, pii.email, pii.name, pii.address, token, bearer; elicited additions per project). A field named or path-labelled with a category is replaced with the string [REDACTED:<category>] before the line is serialised, whether the log call site remembered to redact or not. Redaction happens at the emission boundary (TAC-1602): a rogue field name in a caller-supplied object is redacted by rule, not by hope. The redaction pass never mutates the caller's original object; the emission pipeline copies the object first.",
   "deliveredBy": {
     "tacId": "TAC-1602-observability-logging-redaction-boundary",
-    "field": "interfaces.createRedactionBoundary"
+    "field": "interfaces[createRedactionBoundary]"
   },
   "category": "nonFunctional",
   "domain": "observability",

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-004.json

@@ -5,7 +5,7 @@
   "description": "The logger factory reads a minimum level per environment (ADR-1604 recommended default vocabulary: trace, debug, info, warn, error, fatal; the minimum level per environment is elicited at apply). Emissions below the minimum are dropped before serialisation; emissions at or above the minimum land on stdout. The environment name is supplied at boot (REQ-005) and the level filter is applied per line, not batched. Changing the minimum level mid-run through a documented hook (SIGHUP re-read, admin endpoint, config reload) is out of scope for v1; the minimum is fixed for the process lifetime.",
   "deliveredBy": {
     "adrId": "ADR-1604-observability-logging-level-vocabulary",
-    "field": "decision.levelVocabulary"
+    "field": "decision"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-005.json

@@ -5,7 +5,7 @@
   "description": "The three fields (environment, serviceName, serviceVersion) are supplied to the logger factory at boot from operator-elicited configuration (environment variables, config file, deployment manifest); the factory refuses to construct a logger when any of the three is missing or blank. Every emitted line carries all three at fixed field names so log ingestion can partition by environment and service without prose parsing.",
   "deliveredBy": {
     "tacId": "TAC-1601-observability-logging-logger-factory",
-    "field": "interfaces.createLoggerFactory"
+    "field": "interfaces[createLoggerFactory]"
   },
   "category": "functional",
   "domain": "observability",

package/blueprints/observability-logging/contributions/requirements/observability-logging-req-006.json

@@ -3,12 +3,18 @@
   "prdId": "PRD-001",
   "title": "The applied logger emits an audit-log stream backing the shelf auditLog capability with the correlation identifier already threaded",
   "description": "The blueprint declares the auditLog capability on blueprint.json and delivers it through the same emission stream REQ-001 defines. An audit event lands as one JSON object per line carrying the shared minimum field set plus caller-supplied actor, target, before and after payload fields on the top level of the same object. The correlationId REQ-002 threads is present on every audit line so the consumer (application-admin-console AC-21105-1) can join a role-change audit entry to the request that produced it. The line is subject to the REQ-003 redaction pass and the REQ-004 minimum-level filter; an audit event emitted at info or above lands, an audit event emitted at debug or trace is filtered out in production per the elicited minimum-level-per-environment.",
-  "deliveredBy": { "tacId": "TAC-1601-observability-logging-logger-factory", "field": "interfaces.Logger" },
+  "deliveredBy": {
+    "tacId": "TAC-1601-observability-logging-logger-factory",
+    "field": "interfaces[Logger]"
+  },
   "category": "functional",
   "domain": "observability",
   "priority": "must",
   "rationale": "The shelf routes auditLog through observability-logging (application-admin-console-ADR-2201, application-account-settings-ADR-2601). Without a must-priority REQ naming that capability token, the delivery is a prose promise: consumer probe packs can be shipped but the chain does not have a load-bearing anchor. Making it explicit closes the section 7c gap on the auditLog token.",
-  "tags": ["blueprint:observability-logging", "category:06-audit-log-capability"],
+  "tags": [
+    "blueprint:observability-logging",
+    "category:06-audit-log-capability"
+  ],
   "version": "1.0.0",
   "status": "approved",
   "createdAt": "2026-09-09T00:00:00Z",

package/blueprints/observability-logging/contributions/tacs/tac-1601-observability-logging-logger-factory.json

@@ -17,18 +17,18 @@
   "interfaces": [
     {
       "name": "createLoggerFactory",
-      "kind": "factory",
-      "description": "createLoggerFactory({ environment, serviceName, serviceVersion, minimumLevel, correlationHeader, redactionCategories, now, sink }) -> { getLogger(name), capturedLines() }. The factory is constructed exactly once at boot; getLogger returns a per-module logger with .trace/.debug/.info/.warn/.error/.fatal methods each taking (message, payload?)."
+      "kind": "other",
+      "description": "createLoggerFactory({ environment, serviceName, serviceVersion, minimumLevel, correlationHeader, redactionCategories, now, sink }) -> { getLogger(name), capturedLines() }. The factory is constructed exactly once at boot; getLogger returns a per-module logger with .trace/.debug/.info/.warn/.error/.fatal methods each taking (message, payload?). (legacy kind: factory)"
     },
     {
       "name": "Logger",
-      "kind": "interface",
-      "description": "One method per level; each takes (message: string, payload?: object). Emits one JSON line carrying message, level, timestamp, correlationId, environment, serviceName, serviceVersion, and every payload field folded onto the top level."
+      "kind": "other",
+      "description": "One method per level; each takes (message: string, payload?: object). Emits one JSON line carrying message, level, timestamp, correlationId, environment, serviceName, serviceVersion, and every payload field folded onto the top level. (legacy kind: interface)"
     },
     {
       "name": "correlationHeader",
-      "kind": "config",
-      "description": "Operator-elicited inbound header name governing the correlation identifier acceptance and outbound propagation; recommended default X-Correlation-Id per ADR-1602."
+      "kind": "other",
+      "description": "Operator-elicited inbound header name governing the correlation identifier acceptance and outbound propagation; recommended default X-Correlation-Id per ADR-1602. (legacy kind: config)"
     }
   ],
   "dependencies": [

package/blueprints/observability-logging/contributions/tacs/tac-1602-observability-logging-redaction-boundary.json

@@ -15,8 +15,8 @@
   "interfaces": [
     {
       "name": "createRedactionBoundary",
-      "kind": "factory",
-      "description": "createRedactionBoundary({ categories: string[] }) -> { redact(payload: object): object }. Called once at boot from the logger factory; the factory holds the returned redact function and applies it on every emission."
+      "kind": "other",
+      "description": "createRedactionBoundary({ categories: string[] }) -> { redact(payload: object): object }. Called once at boot from the logger factory; the factory holds the returned redact function and applies it on every emission. (legacy kind: factory)"
     }
   ],
   "dependencies": [],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15101.json

@@ -20,7 +20,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.Logger"
+        "field": "interfaces[Logger]"
       }
     },
     {
@@ -48,7 +48,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "adrId": "ADR-1605-observability-logging-serialisation-refusal",
-        "field": "decision.bigIntFold"
+        "field": "decision"
       }
     },
     {
@@ -62,7 +62,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.Logger"
+        "field": "interfaces[Logger]"
       }
     },
     {
@@ -76,7 +76,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15103.json

@@ -40,7 +40,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-1602-observability-logging-redaction-boundary",
-        "field": "interfaces.createRedactionBoundary"
+        "field": "interfaces[createRedactionBoundary]"
       }
     },
     {
@@ -54,7 +54,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1602-observability-logging-redaction-boundary",
-        "field": "interfaces.createRedactionBoundary"
+        "field": "interfaces[createRedactionBoundary]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15104.json

@@ -30,7 +30,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.Logger"
+        "field": "interfaces[Logger]"
       }
     },
     {
@@ -44,7 +44,7 @@
       "disposition": "template",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15105.json

@@ -40,7 +40,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15106.json

@@ -30,7 +30,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15107.json

@@ -30,7 +30,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     },
     {
@@ -44,7 +44,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1601-observability-logging-logger-factory",
-        "field": "interfaces.createLoggerFactory"
+        "field": "interfaces[createLoggerFactory]"
       }
     }
   ],

package/blueprints/observability-logging/contributions/user-stories/observability-logging-us-15108.json

@@ -30,7 +30,7 @@
       "disposition": "fixed",
       "ownerRef": {
         "tacId": "TAC-1602-observability-logging-redaction-boundary",
-        "field": "interfaces.createRedactionBoundary"
+        "field": "interfaces[createRedactionBoundary]"
       }
     }
   ],