GitCover Symbol GCBoKGitCover Body of Knowledge

Part III — GCPN Container Schema: Research Gain from the First Signature Transaction

Trigger S6 (The first real transaction): The series documented the procedures in Parts I/II — then came the first real signature transaction: a shareholders' meeting resolution (placeholder shareholder-meeting-resolution, anonymized) was executed with facsimile signing and a complete chain. The insights gained in the process (research gain) flow into a normative JSON schema: gcpn-container-1.0.

Overview of the Articles (DS12–DS15)

Art. Title (DE) Core Question
DS12 The Schema gcpn-container-1.0 — Overview How is the container normatively structured, without internal redundancy?
DS13 Referenced-Doc, Actor, Attendees, Persons Who is who — act of the shareholders vs. attendees vs. PII bridge?
DS14 Events as Flags Enum and events_result How do bits express the steps traversed?
DS15 The Act as State Transition — Protocol Interpretation What does an "Act" between two states mean — and GVB as protocol?

The Insights at a Glance (Research Gain)

Four insights from the first transaction flowed into the schema — each one is an AP insight for the research report (BSFZ/FZul project GitCover.IdP):

  1. Artifact Uniqueness (DS12): Each entity (referenced_doc, actor, retention) is described exactly once; further references are sha256-based or run via actor_ref — internal redundancy and repo bloat (standalone .json files) are avoided.
  2. Role Layering (DS13): The Actor is the act of the shareholders (the meeting/sole shareholder — shareholder-meeting-resolution), the Attendee is the person as participant (MD, signing); persons forms the pseudonymized PII bridge (canonical mapping in the gitignored PII circle).
  3. Flags Semantics (DS14): The event steps (offered/accepted/denied/ sign/withdraw) are bits (1/2/4/8/16), the events_result is the bitmask of the steps traversed (e.g., 11 = offered + accepted + sign) — deterministically verifiable, no free text.
  4. Protocol/State Interpretation (DS15): The GVB is the protocol, the Acts are the resolutions; an Act describes the change between two states (before → after) — the GCPN documents exactly these state transitions in a revision-safe manner (Git history = chronology).

Connection to Parts I/II

Parts I/II describe the procedure (How do you sign?); Part III distills the Model from it (How do you describe the procedure in a machine-readable way?). The series thus follows the GCBoK principle: procedure (Saga) → insight (research gain) → schema (normative).

Next: Part IV — PII, GPG & Governikus (planned).

Created: 260913 | Part III of the digital-signage series