Glossary

Shared Language Across the Network

When every team member uses the same vocabulary with the same definitions, alignment follows. This glossary is canonical — shared across all Jubilee sites. Teams add domain-specific terms as needed; foundational terms remain consistent network-wide.

Last updated: 2026-04-18
Owner: Gabe — CTO, Jubilee Software, Inc.
Scope: All Jubilee websites and InspireCortex-hosted properties

Terms

Artifact

A single unit of content managed by JubileeArtifacts — typically one .md file with YAML front matter and Markdown body. Examples: sermon, song, podcast, book chapter, Torah insight.

Auditable History

The principle that every change is traceable to who made it, when, and why. In Jubilee, Git commit history is the sole source of truth for auditing.

Canonical URL

The authoritative URL for a piece of content. Preferred by search engines and link-sharing. For artifacts, the URL structure mirrors the file path.

Covenant Statement

A 4–6 sentence mission paragraph framing a site's stewardship responsibility and stakes. Required on every Jubilee site's home page.

Definition of Done (DoD)

A boxed list of binary, testable criteria that must all pass before a scope is declared complete. No criterion is vague; all are measurable.

Ecosystem

The network of Jubilee sites and services: JubileeInspire, JubileeVerse, FiveFoldTest, BornAgainDNA, JubileeCertifications, JubileeArtifacts, InspireCortex, and the JSV Bible Society.

Ecosystem Map

A hub-and-spoke visualization showing a site's position relative to its siblings in the Jubilee network. Shows data direction and integration types.

Faithful Transmission

The stewardship principle that what the content author intended is what the visitor receives. The platform does not distort, soften, or embellish.

Front Matter

The YAML block at the top of every artifact .md file declaring structured metadata: title, author, date, tags, category, type, references.

Git

The version control system that maintains the authoritative history of all artifacts. Every change is a commit; every commit has author, timestamp, and message.

Jubilee Inspire SSO

The single sign-on identity provider that gates every authenticated Jubilee site. OIDC-based. No secondary auth methods exist.

Kingdom

The reign of Yahuah — both present reality and future fulfillment. The core theme and conviction undergirding Jubilee content.

Markdown

The authoring format for all Jubilee artifacts. Files use the .md extension. Format: YAML front matter + GitHub-Flavored Markdown body.

Preservation

The stewardship principle that every artifact of content is treated as entrusted material. Nothing is lost, overwritten silently, or deprioritized for convenience.

Reader Path

A role-specific recommended journey through a site. Examples: Seeker path (10 min), Operator path (20 min), Builder path (45 min).

Rebuild

The operation of truncating all database artifact tables and re-scanning the repository from scratch. Safe, idempotent, and the guarantor that the database is never the source of truth.

Ruach HaKodesh

The Holy Spirit. Takes feminine pronouns in Jubilee usage. Article rule: use "the Ruach Kodesh" (English article + drop Ha-) or "Ruach HaKodesh" (no English article with Ha-). Never "the Ruach HaKodesh."

Source of Truth

The authoritative location of data. In Jubilee, the .md file in Git is always the source of truth for content. The database is always downstream.

Stewardship Pillars

The three non-negotiable commitments of every Jubilee platform: Preservation, Faithful Transmission, and Auditable History.

Sync Engine

The long-running service that watches the Git working tree for changes. On file change or commit, it parses front matter and upserts the database. Typical latency: 5–10 seconds.

Tree Node

An entry in the tree_nodes database table representing either a directory or an artifact in the navigable hierarchy of JubileeArtifacts.

Tree Override

A user-curated reordering or pinning decision stored separately from source artifacts. Writable by the web layer; does not modify content source files.

ULID

Universally Unique Lexicographically Sortable Identifier. The ID format for artifacts: time-ordered, 26 characters, URL-safe.

Yahuah

The covenant name of God. Preferred in Jubilee content over YHWH, Yahweh, or LORD. Represents the relational, covenantal character of God.

Yeshua

The Hebrew name of the Messiah. Preferred in Jubilee content over Jesus. Preserves the Hebraic heritage and Kingdom-centered identity.

Using This Glossary

For documentation authors: First-occurrence of any glossary term should be hyperlinked to this page. The system auto-links these on publish.

For teams onboarding: New team members should read the Stewardship Pillars, Core Principles, and the ten component definitions before beginning work.

For product managers & operators: The "Reader Path," "Artifact," "Ecosystem," and "Definition of Done" entries are your essential reference set.

For technical architects: The "Sync Engine," "Source of Truth," "Tree Node," and "Rebuild" entries define the non-negotiable constraints.

Adding New Terms

Domain-specific terms are encouraged. To add a term:

Add the entry to glossary.tsx in your site's codebase.
Create a pull request with the entry, clearly marked as "domain-specific" or "candidate for ecosystem-wide glossary."
If the term should be shared across the ecosystem, the CTO will merge it into this canonical version.
Site instances regenerate their glossaries from the canonical copy.