Skip to main content

Arca Suite Vault GO: Production Signing Backed by an In-Cluster Vault

The cryptographic trust root of Arca Suite moves one level down. In this release, arca-decision-room 0.3.7 and arcax 0.6.7 no longer hold signing material in the application layer: decisions, per-vote signatures, field encryption and human approvals are signed and sealed by a dedicated in-cluster HashiCorp Vault (transit engine). Same behavior, stronger root — and every signature now says which key produced it.

Key Takeaways

  • arca-decision-room 0.3.7 — production mode restored: decisions, per-vote signatures and field encryption are now backed by the in-cluster Vault (HashiCorp Vault, transit engine). Vote signatures verify against kid vault-transit:decision-room-votes; cryptographic sealing runs on decision-room-sealing. Boot-time Postgres migrations shipped with 0.3.6 are included.
  • arcax 0.6.7 — the human-approval surface (4-eyes with content-bound signatures) now signs via Vault Transit (arcax-approvals). A tampered or replayed approval is refused with a named rule — unchanged behavior, stronger trust root.
  • Keys live in Vault, not in application configuration: the platform can name the key that signed a vote or an approval, instead of merely asserting that something was signed.
  • Honest scope: production signing backed by an in-cluster Vault — not a third-party certification, and we don't call it one.

What changed

Arca Suite's doctrine — propose, decide, prove — only holds if the proof itself has a root of trust that the application cannot rewrite. Until now, signing keys for votes and approvals lived in the application layer. Vault GO moves that root into a dedicated, in-cluster Vault (HashiCorp Vault, transit engine): the application asks Vault to sign or verify; the key material never leaves it.

  • arca-decision-room 0.3.7 — production mode restored. Decisions, per-vote signatures and field encryption are backed by the in-cluster Vault. A vote signature now verifies against a named key: kid vault-transit:decision-room-votes. Cryptographic sealing of decisions runs on decision-room-sealing. Boot-time Postgres migrations (shipped with 0.3.6) are included.
  • arcax 0.6.7 — the human-approval surface keeps its 4-eyes discipline with content-bound signatures, but the signing itself now goes through Vault Transit (arcax-approvals). The behavior you rely on is unchanged: a tampered or replayed approval is refused, with a named rule. What changes is where the trust sits.

Why it matters

  • A named key, not a vague signature. Verification now returns the key identity (kid) behind a signature — an auditor can check which key signed, not just that something signed.
  • Compromise surface shrinks. Rotating or retiring a signing key is an operation on the Vault, independent of application deployments — no key material in environment variables or config maps.
  • Approval replay resistance, kept explicit. The 4-eyes contract binds the approval to its exact content; under Vault GO, a modified or replayed approval still fails closed, with the same named rule as before.

Version marker

  • arca-decision-room — 0.3.7.
  • arcax — 0.6.7.
  • Arca Suite — Vault GO (2026-11-10), this release. Previous release: Slice 0 (2026-11-09).

What we do not claim

  • No third-party certification: production signing is now backed by an in-cluster Vault — it is not "certified" by an external body, and we don't use that word.
  • No change to approval semantics: the 4-eyes, content-bound rules are identical; only the trust root moved.
  • No key material is ever published: release notes describe key names (kid, transit key references), never keys.

Availability & what's next

The same release mechanic as Slice 0 applies: end-to-end green, documentation, and the four sites updated in the same cycle — arcaq.com, getarcasuite.com, arcax.ai, talentys.eu — with the version marker moving each time.

Explore the platform: What is ArcaQ, Decision Intelligence, Operational Ontology Contracts, and Explainability.