____15DS — The Act as a State Transition: Protocol Interpretation of the GVB

Trigger S6, Finding AP8

From the first use follows the dual interpretation of the terms, which is what makes verifiability comprehensible in the first place:

A GCPN is a form of protocol. In the GCBoK, with Compliance as the main topic, there is often talk of shareholder meetings with resolutions that are summarized in a GVB: The GVB is the protocol — the Acts are the resolutions. And: An Act also describes the change between two states.

The Dual Interpretation

The Act between Two States

An Act (resolution) is a state transition:

Zustand VORHER                          Zustand NACHHER
"Anrufungsauskunft-Auftrag              "Auftrag aufgehoben; Pauschalen
aktiv (GVB 260819 TOP 6.3)"             werden ab 01.09.2026 ausgezahlt"
        │                                       ▲
        └────── ACT (TOP 1: Aufhebung) ─────────┘
                    │
              (revisionssicher: referenced_doc.sha256,
               events_result, Git-Historie)

The Act is anchored by three levels of evidence:

1. Before — via the SHA-256 chain (Referenced-Doc, Sidecars): the state before the Act is verifiable as a document.
2. After — via the flags expression (events_result, e.g. 11) and the embedded artifact: the new state is described deterministically.
3. Chronology — via the Git history of the container: which steps were added when is recorded in the commit log in a revision-safe manner (commit hash = proof of integrity).

In the Schema

"actor": {
  "actor_id": "PARTNER-ORG",
  "kind": "gvb",
  "…",
  "act": {
    "kind": "shareholder-meeting-resolution",
    "note": "Das GVB ist das Protokoll der Gesellschafterversammlung — die Acts sind die Beschlüsse. Ein Act beschreibt auch die Veränderung zwischen zwei Zuständen (Vorher/Nachher); der GCPN dokumentiert genau diese Zustandsübergänge (Events als Flags, referenced_doc.status) revisionssicher.",
    "acts": [ … ]
  }
}

referenced_doc.status shows the state of the Referenced-Doc after the transaction (immutable after signing); events.events_result shows the steps traversed; summary.immutable_from shows the point in time of the immutable transition.

GVB ≠ GCPN — The Roles in the Process

The container accompanies the transaction (creation → signing); the signed Referenced-Doc becomes immutable afterwards. The container continues to document the process — the Git history is the proof.

Research Gain Protocol (AP8)

---

Created: 260913 | Part III, Article ____15DS | Series: digital-signage