certificate-protocol/1.1.0 · updated Jul 9, 2026

Trust certificates

Issuing, verifying, and maintaining certificates under CAPACERO.ar authority.

ADDA certificates support institutional trust, integration integrity, and traceability of the signal framework across ecosystem domains and actors.

Mature issuance requires validating the subject, domain, validity, and context. It is also useful to show whether the certificate is routine recognition, reinforced trust, or an outcome after an incident.

If a certificate accompanies a sensitive measure, the best practice is to link it to evidence, an incident, or a report to preserve the historical assessment.

Checklist

• Validate the subject, domain, and trustLevel before issuing.
• Check validity and the verification code.
• Publish complementary evidence if the certificate responds to an incident.

Quickstart

1. Issue only when the trust can already be justified.
2. Check verification and validity before sharing the certificate.
3. Link evidence if issuance accompanies a response or sensitive milestone.

Operational flow

Validate the basis

Review the subject, domain, and expected trust level.

Avoid issuance without an operational basis.

Issue

Generate a verifiable code and leave the minimum context needed for an audit.

Ensure future traceability.

Relate

Connect issuance to evidence or an incident when appropriate.

Do not leave certificates without context.

flowchart LR
  S1["Validate the basis"]
  S2["Issue"]
  S3["Relate"]
  S1 --> S2
  S2 --> S3

Validators and checks

They run a contextual reading for this surface and return suggested steps with an operational focus.

Validate the certificate workflow

Returns operational guidance for issuance and verification.

Examples

Issuance payload

{
  "subject": "capacero.ar",
  "domain": "capacero.ar",
  "trustLevel": "institutional"
}

Links and references

APIs

/api/adda/v1/certificates/[id]
/api/adda/v1/certificates/issue
/api/adda/v1/governance

Docs and supporting routes

docs/ADDA_CERTIFICATES.md
docs/ADDA_API.md

Common issues

• Issuing under time pressure without reviewing context degrades institutional trust.
• Failing to link a certificate to the originating case makes it difficult to explain.

Suggested actions

• Use a trustLevel consistent with the available evidence.
• If issuance accompanies an incident, link artifacts from the beginning.

Useful reason codes

Score dictionary

severity

Institutional priority of the signal on the ADDA scale.

action

Next operational step recommended by the engine.

reasonCodes

Explainable reasons that justify the assessment.

Protocol notes

• Certification also communicates trust; do it with verifiable context.

Article history

Jul 9, 2026

Added an issuance payload and notes linking it to evidence.