01
Content-addressed release
Publish canonicalizes the bundle to stable JSON and SHA-256 hashes it; identical content re-publishes as a no-op. The hash is the identity of the release.
Glossary
Definitions for the governance terms Relpin uses literally.
Governance language is easy to claim and hard to verify. This glossary defines each term Relpin uses by the exact mechanism behind it, not the marketing label.
Search intent
what is a content-addressed release what is a schema-pinned release what is approval-gated promotion
Release record
pinned
- ARTIFACT
- sha256:9f2c4e81…d41a1
- PLATFORM SCHEMA
- v41 · pinned
- ORG SCHEMA
- v7 · pinned
- APPROVALS
- bound to artifact hash
identical content re-publishes as a no-op · version records append-only
Category position
Use this glossary to check claims against mechanics. Each term maps to a concrete behavior in Relpin: a hash, a pinned version record, an approval bound to an artifact, a dedicated database, a publish-time gate, or a database-enforced audit table.
How to evaluate
02
Schema-pinned release
Append-only version records pinned to exact platform and org schema versions, so a release is tied to the schema it was built against rather than the latest editor state.
03
Approval-gated promotion
DEV, TEST, and PROD form a gated state machine. TEST requires one approval and PROD requires two with separation of duties, the requester cannot self-approve, approvals are bound to the artifact hash, and the promotion fails closed on schema drift.
04
Per-org Postgres isolation
A dedicated Postgres database per organization, with per-workspace and per-environment schemas and least-privilege runtime versus DDL roles.
05
Publish-time pushdown gating
SQL executes server-side, and publish fails if a filter is not server-side, so data access stays governed instead of leaking into browser-side code.
06
Row-level append-only audit
Database triggers capture field-level before and after diffs with the actor on every user table; the audit table is append-only, enforced by database privileges.
Evaluation checklist
- Content-addressed release: SHA-256 hash of the canonicalized bundle
- Schema-pinned release: pinned to exact platform and org schema versions
- Approval-gated promotion: separation of duties, bound to the artifact hash
- Per-org Postgres isolation: dedicated database, least-privilege roles
- Publish-time pushdown gating: server-side SQL, publish fails on non-server-side filters
- Row-level append-only audit: DB triggers, before and after diffs with the actor
Related pages
Guides & Tutorials
All category guides for internal tool builders, AI agents, low-code limits, and production data.
Deterministic ReleasesContent-addressed, schema-pinned releases in depth.
Governed Internal ToolsHow these terms combine into a governed release path.
Audit-Ready Internal ToolsRow-level append-only audit in operational tools.
Code-First Internal ToolsThe code-first authoring model these releases are built from.
FAQ
Frequently asked questions.
What is a content-addressed release?
A content-addressed release is a publish whose identity is the SHA-256 hash of its canonicalized bundle. Relpin canonicalizes the bundle to stable JSON, hashes it, and re-publishes identical content as a no-op.
What is approval-gated promotion?
Approval-gated promotion is a DEV, TEST, and PROD state machine where TEST requires one approval and PROD requires two with separation of duties. Approvals are bound to the exact artifact hash, and the promotion fails closed on schema drift.
What is per-org Postgres isolation?
Per-org Postgres isolation means each organization runs on a dedicated Postgres database with per-workspace and per-environment schemas and least-privilege runtime versus DDL roles.
Relpin