# System

One system the group builds and maintains: an Airtable base, an app, an automation or an API.

One System row is a piece of software the group builds and maintains, typed `schema:SoftwareApplication`. A version or an environment is not a second system. The tool it runs on, such as Airtable or n8n, is a separate fact kept in Tool.

## What a row is

On 2026-10-28 the table has eight rows, all Lifecycle Status Active:

| System | Kind | Sync Key |
| --- | --- | --- |
| Core Record Types | Airtable base | Core Record Types |
| KPIs & OKRs | Airtable base | Operations |
| CRM | Airtable base | CRM |
| Communication | Airtable base | Communication |
| Tooling and Access | Airtable base | Tooling and Access |
| Products & Services | Airtable base | Products & Services |
| Systems Central | Airtable base | Systems Central |
| Cal.com Booking Intake | Automation | (blank) |

[![System lists the seven Airtable bases and one n8n workflow.](/systems/systems-central/screens/sc-system-grid.png)](/systems/systems-central/screens/sc-system-grid.png)

Cal.com Booking Intake is the n8n workflow that turns Cal.com bookings into CRM records. It is documented in Automations, in [Cal.com Booking Intake](/automations/calcom-booking-intake). It has no Sync Key, so it cannot receive feedback through routing. KPIs & OKRs keeps the key `Operations` from its former name; see [Architecture](/systems/systems-central/architecture#the-operations-key).

## Fields

### Identity

| Field | Type | Meaning |
| --- | --- | --- |
| Name | Text, primary | The name the group uses; unique in the list |
| Kind | Single select | Airtable base, Web app, Mobile app, Automation, API, Other |
| Description | Long text | What the system is for, in a sentence or two |
| URL | URL | Where people open the system |
| External Identifier | Text | The id the platform assigns, such as a base id |
| Version | Text | Version in use; blank when not versioned |
| Lifecycle Status | Single select | Draft, Active, On Hold, Archived |
| Tags | Links → Tags (mirror) | Optional labels from Core |

### Routing and ownership

| Field | Type | Meaning |
| --- | --- | --- |
| Sync Key | Text | Must equal one System Key option in Feedback, exactly |
| Maintainer | Links → Membership (mirror) | One membership; the default Accountable for new feedback |
| Maintainer (Name) | Lookup | Broken: points at Member (Name), which the mirror no longer has |
| Tool | Links → Tool (mirror) | The platform the system runs on |

### Feedback health (computed)

| Field | Type | Calculation |
| --- | --- | --- |
| Feedbacks | Links → Feedback | Inverse of Feedback → System |
| Open Feedbacks | Rollup | Sum of Is Open over linked feedback |
| Overdue Feedbacks | Rollup | Sum of Is Overdue over linked feedback |
| Oldest Open | Rollup | Earliest Open Since over linked feedback |

### Inverse links (edit on the other row)

System Rules, Record Types (Original), Record Types (Mirrored), Architecture Decisions and Work Items. Each one lists the rows that point to this system. Change them on the System Rule, Record Type, Architecture Decision or Work Item row.

## Current state

Six of the eight rows link a Maintainer. KPIs & OKRs and Cal.com Booking Intake have none. KPIs & OKRs shows 3 open and 3 overdue feedbacks; every other system shows 0. Tool is blank on every row. Each System row links between 6 and 60 Work Items, and one Work Item can link several systems.

## Example

A fictitious new base: Name `Field Service`, Kind `Airtable base`, Sync Key `Field Service`, URL the base address, External Identifier the base id, Version `v1`, Lifecycle Status `Draft`, Maintainer the membership that will change it, Tool `Airtable`.

## Related

[Register a system](/systems/systems-central/register-system) · [Feedback](/systems/systems-central/entity-feedback) · [Record Type](/systems/systems-central/entity-record-type)