SES begins with a simple question: who is allowed to determine what may validly become effective inside a concrete effect space?
The sovereign sets the rules. The SES machine applies them without normative discretion of its own. The operator and the sovereign may be the same or different sources.
A technical event is not yet valid SES effect.
The sovereign is the explicitly bound normative rule source for one concrete effect space. Code, AI, providers, admins, and technical control do not create sovereignty.
- O — Operator-sovereign
- U — User-sovereign
- M — Mixed root sovereignty
- O/U — Instance-selectable topology
Operating, hosting, administering, supporting, or distributing a solution does not create sovereignty.
A root sovereign may delegate a clearly bounded sub-domain as its own sovereignty domain. Authority delegation only permits action under already-set rules.
Operator, sovereign, delegated sovereign domains, authorities, and non-claims are separately bound.
Third systems supply input and receive output. They do not need to support SES and do not become sovereign by technical capability.
Scope is the complete set of effect-relevant technical, human, organizational, external, manual, and delayed paths.
For existing effect spaces, TBYD recommends SEBG. This is not a universal SES mandate.
Validity is binary and claim-specific. Evidence integrity is not semantic truth.
A new valid attack or material effect-relevant change reopens the affected claim.
C0 architecture, C1 artifact closure, C2 binding, carrier, C3 readiness, and C4 productive activation remain distinct.
Path A — Self-build
Qualified Domain, Quality, Process, and Systems engineers form the machine directly.
Path B — Prepared formation/installation through SSMFF
A sovereign may be fully competent to decide without being an SES engineer. SSMFF carries the formation/discovery burden, closes the concrete Scope, and forms the required bindings as far as the formation can validly close them. When a sovereign decision is required, it asks the sovereign.
For a prepared solution:
solution operator/publisher provides Target rule templates -> sovereign selects/authorizes -> SSMFF binds
Factory Formation Rules are not Target-domain rules.
Rules(Factory) != Rules(Target)
Prepared formation can be largely repeatable. It never means automatic Target validity, automatic rule choice, ordinary software installation, or PASS inheritance.
- Effect is what receives consequences inside a bound domain.
- The sovereign is the bound normative rule source.
- Operator and sovereign may be the same or different.
- Sovereignty may be delegated to exact sub-domains.
- Scope covers every effect-relevant path.
- Third systems can supply without becoming normative authority.
- A concrete machine may be self-engineered or formed as a prepared Target through SSMFF.
- SSMFF carries formation/binding but not Target sovereignty, Target rule authorship, or Target PASS.
Machines · Apply · Verify
Start small — but close the claim completely
A SES machine does not have to claim an entire digital environment at once. A first useful effect space may deliberately be small. Inside that claim, however, the same condition applies: every effect-relevant path must be bound or formally excluded. A small complete claim is possible; a large claim with unknown effect paths is not.
Evidence does not create authority. An integrity-bound Evidence Chain shows what was bound and can be reconstructed; it does not automatically prove that every input was semantically true. Rule source, decision authority, evidence ownership and execution remain separate questions.
Effect scale is not compute-load scale
The scale of controlled effect and the scale of intrinsic SES compute work are different things. SES binds rules, states, decisions, consequences, evidence and revalidation. How much additional compute a concrete technical carrier requires depends on that carrier and use case.
There is therefore no universal SES hardware size. An AI- or GPU-heavy carrier does not automatically make SES itself an AI or GPU system. Conversely, a smartphone-class architecture such as PSEB demonstrates architectural possibility, not a universal device guarantee.