GitCover Symbol GCBoKGitCover Body of Knowledge

Part II — FES & Facsimile

Trigger S3/S4: An external contractual partner requires an advanced electronic signature; the signature should appear as a positioned graphic in the PDF layer (DocuSign-style).

Overview of articles (DS06–DS11)

Art. Title (DE) Core question
DS06 eIDAS foundations: simple, advanced, qualified eS Which levels exist, and when is which sufficient?
DS07 The facsimile procedure: positioned graphic in the PDF layer How does the signature graphic get to the right place in the PDF?
DS08 Signature plate and hash anchoring How does the graphic become a verifiable signature declaration?
DS09 The FES envelope report How do we document a DocuSign-style process repo-natively?
DS10 The FES container package (gcpn.zip) How is the entire signature chain delivered physically?
DS11 Connecting external partners: Gitea, GitCover.IdP, API/MCP How does the small entrepreneur scale access to permissions and evidence for partners (customers, principals, co-workers)?

The levels of electronic signature

einfache eS ────► FES/ADES ────► QES
   │                 │             │
Grafik/E-Mail    Signaturplatte   Zertifikat der
(Facsimile)      + Kryptobindung  EU-Trust-Liste
   │                 │             │
"Textform"        "fortgeschritten" "qualifiziert"
(GCBoK Teil I)    (Teil II)        (extern, § 126a BGB)

Part I ended at text form — the graphic is simple eS. Part II connects FES: the signature graphic (facsimile) is positioned in a PDF layer and anchored with a signature plate (certificate hash, timestamp, signing role) — DocuSign-style, but documented repo-natively.

The role of the repo remains

This also applies in Part II: The repo is the evidence layer. The FES service (or the organization's own PDF signature software) generates the signed PDF; the repo documents:

  1. The FES envelope report (who was asked, when signed, with which certificate hash) — DS09
  2. The physical version (signed PDF) in the container package — DS10
  3. The link to the text-form container from Part I (same source document SHA, extended chain)

Reading order

  1. DS06 — eIDAS levels and their evidentiary value (AdES, AdEE, QES).
  2. DS07 — The facsimile procedure: PNG/SVG, positioning, height=40.
  3. DS08 — Signature plate: certificate, hash, timestamp, roles.
  4. DS09 — The envelope report: DocuSign-style process documentation in the repo.
  5. DS10 — The container package: *.gcpn.zip as a deliverable verification set.
  6. DS11 — Connecting external partners: the three scaling levels (offline package → Gitea via Internet → GitCover.IdP/API/MCP).

Next: Part III — GCPN container schema (research gain from the first process: JSON schema gcpn-container-2.7).

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