Salvato in:
| Autore principale: | |
|---|---|
| Natura: | Recurso digital |
| Lingua: | |
| Pubblicazione: |
Zenodo
2026
|
| Accesso online: | https://doi.org/10.5281/zenodo.20112693 |
| Tags: |
Aggiungi Tag
Nessun Tag, puoi essere il primo ad aggiungerne!!
|
Sommario:
- <h1>CAE-Cert v0.1 — First official certificate</h1> <p>ADR-036 <strong>ACCEPTED</strong> by the project lead on 2026-05-10. First *build-to-destroy* certified protocol of the Pulsaride project.</p> <h2>Cornerstone artefacts</h2> <ul> <li><strong><code>research/cae-cert-v0.6.0.v01.json</code></strong> — first official certificate <ul> <li><code>formal_verdict : KAPPA_INCONCLUSIVE</code></li> <li><code>operational_verdict : KAPPA_BAND_LIMITED_UPPER_OPEN</code></li> <li>Signature: Ed25519 (RFC 8032) over JCS-canonicalised payload (RFC 8785)</li> </ul> </li> <li><strong><code>research/cae-cert-v0.6.0.v01.json.sig</code></strong> — detached binary signature</li> <li><strong><code>keys/cae-cert-issuer.pub</code></strong> — issuer public key <ul> <li>Fingerprint SHA-256 (DER SubjectPublicKeyInfo) : <code>6c153dc3dddb9738347c587e107399e3ed714f715f0e7716761436b748dcbb65</code></li> </ul> </li> </ul> <h2>Reproducible verification (< 30 s)</h2> <pre><code class="language-bash">git clone https://github.com/pulsaride/cae-research-kit.git cd cae-research-kit && git checkout v0.7.0-cert-protocol pip install cryptography==42.0.8 jcs==0.2.1 PyYAML PYTHONPATH=. python -m src.cert.verify \ --cert research/cae-cert-v0.6.0.v01.json \ --sig research/cae-cert-v0.6.0.v01.json.sig \ --public-key keys/cae-cert-issuer.pub \ --repo-root . # Expected: OVERALL: PASS (fingerprint + signature + schema + integrity) </code></pre> <h2>Normative documents</h2> <ul> <li><code>docs/adr/ADR-036-cae-cert-v01-protocol.md</code> — protocole CAE-Cert v0.1 (ACCEPTED)</li> <li><code>paper/cae-cert-v01/paper.md</code> — companion preprint</li> <li><code>research/MANIFEST.v0.7.0.yaml</code> —<code>certification:</code> section per protocol §7.2</li> </ul> <h2>Sovereignty note</h2> <p>The issuing private key is held offline in a single custodial environment and is never transmitted, copied to CI, or embedded in container images. Any rotation requires a dedicated ADR-037; all future certificates will chain back to this fingerprint as the long-term trust anchor.</p>