Skip to main content

Topology

Typed specification

Generated by the pinned ess generate --kind docs from ess. Structural validation establishes consistency; behaviour, storage and cross-record predicates remain implementation obligations.

Runtime requirements, stated semantically. None of this is a deployment and nothing generates a manifest from it: a replica floor of two is a claim that the system is not correct with one instance, which is a fact about the design and survives every change of hosting.

Components that run nowhere​

Declared as a unit of ownership, with nothing in the topology running it. That is legal — a context can be owned by a library — but it is the kind of legal worth reading twice.

  • feed-binding
  • local-metadata-authority
  • tool-contract-publisher

Back to the index.

Generated from connectors v1 · model digest e1e1672d0af4753cb8f2da6c0b22a7f6ae8ce9f7abc168f86169babdf1325787 · contract digest cbce0c8be561de4d2219e841ef73ebdd9e72eac7e83c3cfc1355cac651001d13. Do not edit this file; change the specification and regenerate it with ess generate.