Secure Quickstart

This quickstart demonstrates the minimum integrity workflow without assuming a stable DigiEmu Secure CLI.

Goal

Protect an artifact with a reproducible cryptographic identity and verify that the artifact has not changed.

1. Create a test artifact

In PowerShell:

$artifact = @{
    artifact = "example"
    version  = 1
    status   = "ready"
}

$artifact |
    ConvertTo-Json |
    Set-Content ".\artifact.json" -Encoding utf8

2. Calculate SHA-256

Get-FileHash ".\artifact.json" -Algorithm SHA256

Record the reported hash.

3. Modify the artifact

$artifact.status = "modified"

$artifact |
    ConvertTo-Json |
    Set-Content ".\artifact.json" -Encoding utf8

4. Calculate SHA-256 again

Get-FileHash ".\artifact.json" -Algorithm SHA256

The hash should now differ.

What this demonstrates

A cryptographic hash can identify a specific artifact representation.

It does not prove:

• who created the artifact
• whether its content is true
• whether an action was authorized
• whether a decision is legally valid

Those properties require additional evidence and explicit trust boundaries.

Secure workflow

Artifact
   ↓
Canonical Representation
   ↓
Hash
   ↓
Evidence Record
   ↓
Optional Signature
   ↓
Independent Verification

Next

Continue with Secure Architecture.