BDS0.1

Record Type

One kind of record, the system that keeps its original and the systems that mirror it.

Reviewed 2026-10-28Markdown

One Record Type row is one kind of record the systems keep, such as Membership, Deal or Metric, typed schema:Class. It names the single system where people create and correct that record, the System of Record, and every system that shows a synced copy, Mirrored In. A synced copy is never a second record type, whatever the table is called in the base that holds it.

What a row is

On 2026-10-28 the table has 62 rows. Per System of Record: Core Record Types 16, KPIs & OKRs 17, Tooling and Access 9, CRM 5, Products & Services 6, Systems Central 5, Communication 4. Organization and Tag are mirrored in six systems and Membership in five; most kinds have no mirror.

per System groups each record type under the system that keeps its original.

The build rule “Every record type is registered in Systems Central” makes this table the register that new tables must enter. Work Item, created on 2026-10-28, is not registered yet; see Known gaps.

Fields

Field Type Meaning
Name Text, primary Singular name as the group calls it; unique
BDS Type Long text The vocabulary type the source table declares, short form (bds:Membership)
System of Record Link → System, single The one system that keeps the original
Table ID Text The id of the original table inside the System of Record
Mirrored In Links → System Every system with a synced copy
Checked Checkbox Type, owner and every mirror were reviewed
Review Note Long text One open issue per line, naming base and table; blank when Checked
System Rules Links → System Rule Inverse of Applies To
Architecture Decisions Links → Architecture Decision Inverse of Record Types on the decision
Work Items Links → Work Item Inverse of Record Types on the work item

Record Type has no Tags link yet; a Work Item asks for it.

Review state

49 rows are Checked. 13 are not, and each has a Review Note: Organization, Person, Membership, Team, Department, Position, Campaign, Tag, Classification Term, Organization Relationship, Tool Account, Lead Source Automation and Architecture Decision. Most notes are about mirrors in other bases with a misleading name or no description, for example a CRM copy named after its vocabulary type. The Membership note records the broken name lookups in this base. These notes point at problems; the fixes happen in the bases concerned.

The Relationship row is removed from the model: the CRM table it points to was deleted on 2026-11-04 and leads are now Deals at stage Lead. The row itself is still Checked and has not been retired yet.

Rules

  • Exactly one System of Record. The link is single, so the picker enforces it.
  • Table ID opens a table inside the System of Record. Mirror tables keep their own ids, which are not listed.
  • A two-way copy is still listed in Mirrored In. Its edits return to the System of Record.
  • Unticked Checked means not reviewed yet, not wrong.

Example

A fictitious new kind: Name Service Visit, BDS Type ops:ServiceVisit, System of Record Field Service, Table ID the new table’s id, Mirrored In CRM, Checked unticked, Review Note CRM: mirror not created yet.

Register a record type · System · System Rule