P4AZ · Platform for A → Z Organisation documentation

Prepare, sign,
check and publish.

Your signing key stays in your certificate provider’s application.

Preparing your documents

  1. Select the certificate country and wait for authenticated registry metadata.
  2. Enter the subject, identifier, registry and publication host. Add contact details and payment proofs if needed.
  3. Select a process directory. Generate only the documents you want to change using their individual buttons. Keep work and work/new: they contain saved drafts and the data needed to resume editing.
  4. Sign each payload externally as detached XAdES with SHA-256. Preserve the exact UTF-8 bytes and filename reference. Follow the subject-prefixed SIGNING-INSTRUCTIONS.txt in work/new for signature filenames. Save signatures alongside the payloads.
  5. Read signatures from work/new, then use Assembly. All signed changes are checked before writing. Unsigned drafts and unchanged publications stay in place. Mark optional documents explicitly when you want to remove them; Assembly archives their existing copies before removal.
  6. Upload only the resulting P4AZ directory to the signed HTTPS host, then run HTTPS verification. Comparison with local files is optional. Generate default.json and the server access file separately when needed.

What these checks mean

Technical checks cover the supported signature profile, payload binding, certificate identity and authenticated CA policy. Revocation (CRL/OCSP), trusted timestamps, registry entries and legal ownership are not checked.

A bank, digital euro (DEAN) or Solana proof is the subject’s signed statement. It does not confirm an active bank account, a balance or possession of a blockchain private key.

The closed XAdES profile accepts RSA-SHA256 or ECDSA-SHA256, SigningTime and SigningCertificate/V2. Other signature variants require separate implementation and testing.

Never publish work, work/new, workspace-archives or private keys. Public JSON needs application/json and anonymous CORS access. The application changes local files, including explicitly marked or technically invalid copies removed by Assembly after archiving. It does not upload them. If your earlier working directory contains temp, rename it to work in your file manager before opening it here.

Return to Organisation