1 · Operator
Concrete technical/organizational operator of the instance. Root sovereignty is separately bound as: Bank Sovereign; technical operation alone does not create it.
Payment · PUBLIC C0 REFERENCE ARCHITECTURE
Make payment effect controllable ex ante
Bank Payment Acceptance and Execution Machine — Binds payment-related effect, authority, states, evidence and consequences inside a closed SES effect space.
100/100 is binary: an unresolved constitutive condition does not create partial PASS and must not be completed by implementation assumptions.
This page describes a source-bound C0 machine architecture. It is not software, not a platform, and not proof of an already bound or productively activated operator instance.
SOVEREIGNTY + FORMATION · A6 v1.2
Who operates? Who is sovereign? How is the instance formed?
Roles are bound separately. Operation, authority, sovereignty and formation are not the same thing.
2 · Root sovereignty: O
- Bank Sovereign: The source binds an exact bank acceptance and execution effect; providers, connectors, models, queues or interfaces may not add effect classes at effect time.
3 · Delegated sovereignty
No additional delegated sovereignty domain is claimed at C0 level.
4 · Authority-only roles
- Bank operational roles with bounded authority
- payment providers/carriers
- customer sovereignty remains foreign to bank-side machine claim
5 · Target rule source
Engineering path: the machine-specific Target rule set is defined/authorized in the Target’s own sovereign binding. Prepared SSMFF path: solution operator/publisher supplies Target rule templates -> sovereign selects/authorizes -> SSMFF binds. SSMFF does not author Target rules.
6 · Formation path
Both: Engineering or prepared SSMFF formation
SSMFF role: Optional prepared formation path: SSMFF may carry discovery/scope/binding/formation burden for a prepared Target while sovereign decisions stay with the Target sovereign.
7 · Factory/Target boundary
SSMFF Formation Rules != Target Rules. Sovereign decisions stay with the sovereign. Factory result/verification/validation/readiness != Target C2/C3/C4/PASS. Missing Target rule or sovereign decision remains non-PASS.
1 · EFFECT PROBLEM
Make payment effect controllable ex ante
Binds payment-related effect, authority, states, evidence and consequences inside a closed SES effect space.
Source-bound reading
This bank-sovereign machine decides whether one exact customer-authorized payment may obtain a valid bank acceptance effect and governs the resulting execution commitment through one qualified external payment boundary.
2 · MACHINE DEFINITION
What is this machine?
This bank-sovereign machine decides whether one exact customer-authorized payment may obtain a valid bank acceptance effect and governs the resulting execution commitment through one qualified external payment boundary.
This page describes a source-bound C0 machine architecture. It is not software, not a platform, and not proof of an already bound or productively activated operator instance.
4 · EFFECT MODEL
What effect is bound?
The source binds an exact bank acceptance and execution effect; providers, connectors, models, queues or interfaces may not add effect classes at effect time.
The effect/result model remains source-local; no foreign machine model is imposed on it.
5 · SCOPE
Scope is causal completeness, not an inventory.
The v1.3 claim is deliberately narrow: one immediate outgoing cash-funded corporate EUR payment with exact current claims and qualified rail capability.
New or previously unresolved effect-relevant paths reopen the affected claim and must be revalidated.
6 · EXTERNAL SYSTEMS AND CARRIERS
Carriers may carry — not invent normative meaning.
External systems may supply input, carry technical functions, contribute receipts or evidence, or execute bound consequences. Participation, access, provider status, model output, or technical capability does not create normative authority. The concrete role remains source- and instance-bound.
7 · BASELINE / DOMAIN RELATION
Baseline semantics remain machine-specific.
The source does not define an operational SEBG baseline for BPAE; the exact payment scope is governed directly by its source-defined guard and state model.
SEBG-first is TBYD guidance for existing effect spaces, provided it is not confused with the machine source’s own architecture.
8 · RULES · STATE · JUDGMENT
Rule, state, and judgment must be closed before positive reliance.
This A6 does not impose a generic result model. The source-specific rule/state/judgment model remains controlling. Missing authority, missing required state, conflict, UNKNOWN/OPEN, or another source-defined non-PASS state must not be converted into validity by runtime guessing or programmer defaults.
9 · EVIDENCE
Evidence proves only the claim it actually carries.
Evidence is reconstructive or constitutive only within its bound claim; a receipt does not prove external realization unless its contract carries exactly that claim.
Evidence integrity is not automatically semantic or external truth.
10 · FAILURE AND REVALIDATION
Failure is not reinterpreted as PASS.
A source-defined failure is not merely a warning. It binds the specified non-PASS consequence. A material source, scope, authority, rule, state, evidence, or dependency change reopens affected gates; prior PASS is not silently inherited.
11 · FORMATION AND CARRIERS
The machine order is formed before carrier implementation.
The constitutive order remains: Sovereign / Domain → Quality / Process / Systems Engineering → Domain Assurance → Technical Carrier Engineering. Carriers come after normative and machine closure; they may not invent missing rules, authority, or consequences.
1 · Sovereign / Domain
Effect space, authority, and acceptance boundaries.
2 · Quality · Process · Systems
Close scope, rules, state, failure, evidence, and revalidation.
3 · Domain Assurance
Review domain meaning and claim-relevant assurance.
4 · Technical Carrier
Technically carry the already closed order.
12 · C0 BOUNDARY
Public C0 is architecture — not your finished machine.
The public page binds the machine-type architecture. C1 closes concrete artifacts, C2 binds one operator instance, technical carriers carry the already closed machine, C3 proves activation readiness, and C4 productively activates that exact instance. Public C0 does not transfer PASS to an operator instance.
C0 → C1 → C2 → Technical Carrier → C3 → C4
13 · PUBLICATION STATE
A6 is fully readable without IPFS linking.
v1.3 · A7_NOT_BOUND · NO_CID_LINK
Source-bound C0 version: v1.3. This A6 publishes no CID, no IPFS link, and no A7/version route. Publication integrity will be closed later as a separate project and is not a substitute for C0/C1/C2/C3/C4.
14 · CHECKPOINT
Six statements against the most common misreadings.
- This bank-sovereign machine decides whether one exact customer-authorized payment may obtain a valid bank acceptance effect and governs the resulting execution commitment through one qualified external payment boundary.
- The constituted bank organization is sovereign for bank-side acceptance and execution; customer authorization, financial position, security, compliance and rail qualification remain foreign constitutive claims owned by their respective effect spaces.
- The source binds an exact bank acceptance and execution effect; providers, connectors, models, queues or interfaces may not add effect classes at effect time.
- The v1.3 claim is deliberately narrow: one immediate outgoing cash-funded corporate EUR payment with exact current claims and qualified rail capability.
- The source does not define an operational SEBG baseline for BPAE; the exact payment scope is governed directly by its source-defined guard and state model.
- Public C0 is not an operator instance; A7/IPFS remains without active links in this build.
15 · NEXT STEP
Continue to operator formation, the catalogue, or verification.
Apply
Place concrete operator formation from C0 through C1/C2 and carriers to C3/C4.
Go to Apply →Machines
Return to the public catalogue and compare other generic C0 architectures.
Go to Machines →Verify
Place Quality, Process and Systems Engineering for the next closure step.
Go to Verify →