Security & Trust

CRAFT is built around a local execution model with explicit trust boundaries. This page summarizes the security architecture for users and reviewers.

Local Execution Boundary

Automations execute inside your CAD host (Revit or Civil 3D), on your machine. CRAFT does not send your model data, design files, or execution results to any external server.

Cloud services provide three functions only:

• Artifact registry — stores and serves signed automation packages (passive, read-only)
• Licensing — issues and refreshes machine-bound activation tokens
• Signing — signs artifacts at publish time using the CRAFT signing key

None of these services execute automations, interpret execution plans, or access your host environment.

Artifact Signing and Hashing

Every published artifact is signed using ES256 (ECDSA with the P-256 curve). The signature binds to the SHA-256 hash of the raw zip bytes — the exact bytes that were uploaded at publish time.

• Content hashes use SHA-256 for artifact identity
• Deterministic serialization ensures identical content always produces the same hash
• Deterministic packaging ensures identical content always produces the same artifact

This means that if you download a published artifact and compute its hash, you can verify it matches the published signature independently. No trust in the transport layer is required.

Immutability

Published artifacts are immutable. Once an artifact version is published to the registry, it cannot be modified, overwritten, or deleted through normal operations. Modifications require publishing a new version.

Trust Anchors

CRAFT clients verify artifact signatures against trust anchors — public keys embedded in the client or loaded from a configured trust store. The default policy uses embedded trust anchors only, with no silent network calls to fetch keys.

If your organization needs to manage trust anchors (for example, rotating keys or adding enterprise-specific anchors), this is handled through the admin interface. See IT / Admin Notes for details.

Client-Side Verification

Signature and hash verification happens on the client — your machine — not on the server. When you import an automation package, CRAFT verifies:

• Zip archive integrity
• Content hashes match the manifest
• Vendor signature verifies against known trust anchors

If any verification step fails, the import is blocked. This is enforced by the Gate — there is no override.

Egress Disclosure

CRAFT does not make silent network calls. Any operation that involves network communication — including license refresh, registry access, or any other server call — is surfaced through the Gate's egress disclosure panel before it happens.

The egress disclosure covers three categories:

Network egress

Whether the operation contacts an external server, and which URLs

Host context egress

Whether host environment data (model info, file paths, machine state) will leave the device

Telemetry

Whether usage data will be collected, and where it is stored

All three default to disabled. Acknowledgment is per-operation and does not persist.

Telemetry

Telemetry is off by default. No usage data, analytics, or diagnostic information leaves your machine unless you explicitly opt in through the egress disclosure flow. When telemetry is disabled, data retention is local-only.

No Host Context Egress by Default

Host context — information about your open model, file paths, environment variables, and machine state — never leaves your device without explicit opt-in. This is a locked default that cannot be changed silently.