stzServiceRegistry

(no comment in the source: the name reads as a sentence) initno extension

(no comment in the source: the name reads as a sentence) nameno extension

the dependency surface ------------------------------------------- Declare a service this solution depends on, before anything is bound. This is what turns "what does this touch?" from archaeology into a query -- and it is what lets an UNBOUND dependency be a finding rather than a surprise.QCSXTZZZIBWUMany

(no comment in the source: the name reads as a sentence) is declaredno extension

(no comment in the source: the name reads as a sentence) declared servicesno extension

(no comment in the source: the name reads as a sentence) number of declaredno extension

binding ---------------------------------------------------------- Bind an implementation. The posture is asked OF THE OBJECT: anything with IsSandbox() answering true is a sandbox. Declaring itself beats guessing from a class name, and it means a third-party double can opt in.QCSXTZZZIBWU

...say it explicitly when the object cannot.QCSXTZZZIBWU

Bind a genuine LOCAL equivalent -- sqlite, the filesystem, a local model. Not a fake, so unlike a sandbox this may ship; see the posture note above.QCSXTZZZIBWU

Bind the real thing, naming the STORE SECRET its credential lives in. The name, not the key: a registry that held credentials would be one more place they leak from.QCSXTZZZIBWU

Remove the IMPLEMENTATION but keep the dependency. The service is then declared-and-unbound, which IS a finding -- your solution still needs the thing, it just has nothing to serve it. To retire the dependency itself, use Undeclare.no extension

Retire the dependency altogether -- the solution no longer needs this service. Unbinds it too, so nothing is left half-declared.no extension

resolution (what the application actually calls) ------------------ The service by name. RAISES when nothing is bound -- an unbound dependency that silently returned NULL would fail later, somewhere else, as a null-call with no hint of the real cause.no extension

(no comment in the source: the name reads as a sentence) hasno extension

(no comment in the source: the name reads as a sentence) bound servicesno extension

(no comment in the source: the name reads as a sentence) number of boundno extension

(no comment in the source: the name reads as a sentence) posture ofno extension

(no comment in the source: the name reads as a sentence) is sandboxedno extension

(no comment in the source: the name reads as a sentence) secret name ofno extension

every service still bound to a fake -- the "what is not real yet" list.no extension

the genuinely-local ones: real, self-hosted, shippable.no extension

(no comment in the source: the name reads as a sentence) is localno extension

(no comment in the source: the name reads as a sentence) live servicesno extension

(no comment in the source: the name reads as a sentence) unbound servicesno extension

the phase -------------------------------------------------------- :development / :emulated -> sandboxes are expected. :production -> they are a violation. The phase is the SAME switch stzDelivery already uses, so nothing new decides what is real.QCSXTZZZIBWU

(no comment in the source: the name reads as a sentence) phaseno extension

(no comment in the source: the name reads as a sentence) is productionno extension

governance ------------------------------------------------------- [ [ :invariant, :severity, :where, :message ], ... ] -- the same shape stzSecurityPosture and the graph rules use, so one CI gate covers all three. poStore may be NULL when there is no keyring to check against. NOTE: each _Check returns its OWN list and this LOOPS to append the elements. Haro's `+` on a list appends the whole list as ONE element, so `_aF_ + This._Check...()` would nest rather than accumulate -- and a nested findings list silently reports zero errors. Same shape as stzSecurityPosture.no extension

(no comment in the source: the name reads as a sentence) findingsno extension

(no comment in the source: the name reads as a sentence) is sound viano extension

(no comment in the source: the name reads as a sentence) is soundno extension

(no comment in the source: the name reads as a sentence) number of findingsno extension

(no comment in the source: the name reads as a sentence) report viano extension

(no comment in the source: the name reads as a sentence) reportno extension

ASKED IN THE PRODUCTION FRAME, whatever the current phase. "May I go LIVE?" IS the production question, so answering it from a :development phase would have said YES with a fake still bound -- the phase-dependent invariants (sandbox-in-production, ephemeral-in-production) simply had not fired yet. The phase is set, the surface judged, the phase restored: asking is not declaring. (Found while writing the narration; the guard had only ever asked after setting production, so the honest answer and the convenient one agreed.)no extension

the surface judged as production would judge it, then put backno extension

(no comment in the source: the name reads as a sentence) findings for productionno extension

...and the same, but explaining itself.no extension

NOTE this does NOT duplicate the invariants above. Findings from Findings() already carry the report's shape, so the registry joins the shared CI gate directly: oReport.IngestLegacy(oReg.Findings(), "services"). What the GRAPH adds is the question a flag check cannot ask -- which PART of a solution depends on a fake -- and that needs the delivery's parts joined to these nodes (see stzDelivery.AsRuleGraph and stzServiceRuleSet).no extension

(no comment in the source: the name reads as a sentence) showno extension