Architecture and ownership
What Systems Central owns, what it mirrors and how feedback reaches each system's base.
Systems Central owns six kinds of record: System, Record Type, System Rule, Architecture Decision, Work Item and Feedback. It reads people, organizations and tags from Core and tools from Tooling and Access. It sends Feedback rows out to the base of the system they are about.
Mirrors in
| Local table | Source | Local columns added here |
|---|---|---|
| Membership (mirror) | Core Record Types → Membership | Feedbacks (Reporter), Feedbacks (Accountable), Systems (Maintainer), Architecture Decisions (Decided By), Work Items (Assignee), Tags |
| Organization (mirror) | Core Record Types → Organizations | Tags (local) |
| Tool (mirror) | Tooling and Access → Tool | Systems (Runs On), Tags |
| Tags (mirror) | Core Record Types → Tags | Links back from Feedback, System, the mirrors, Architecture Decision and Work Item |
Correct shared facts at the source: a person’s name or a membership’s status in Core, a tool’s name in Tooling and Access. Only the link columns added in this base are local. The sync settings, such as refresh interval and whether source deletions are kept, are not visible through the API; confirm them in each sync’s settings in Airtable.
Feedback routing
Every system keeps one Sync Key on its System row. Every Feedback row carries a System Key, a single select with one option per key. The same key does two jobs:
- Out to the system’s base. A filtered view in Feedback is the source of a sync into that system’s base. On 2026-10-28 the only such view is CRM - Feedback (dont change the filter), filtered on System Key = CRM. CRM - Pedro shows it as its Feedback table. The 2026-10-26 schema notes it as a two-way mirror, so a row typed in the CRM arrives here with System Key = CRM.
- Back to the System row. The System link should match the key. Key Check shows
⚠ key mismatchwhen the linked system’s Sync Key differs from System Key, and⚠ no system linkedwhen a key is set but no system is linked.
No automation links System from System Key today: the only Airtable automation is undeployed and does something else. See Automations. Link System by hand at triage.
The Operations key
The System KPIs & OKRs was formerly named Operations and still has Sync Key Operations. Its 14 linked feedback rows use System Key Operations and show a blank Key Check, which is consistent. The legacy base appBUharASqfMgOFc “Operations” is not one of our systems. Those 14 rows were moved from it on 2026-09-17, so their pages and wording refer to the legacy base. Read Operations as the routing key of KPIs & OKRs, never as a current system.
The System Key options Fintable, Snack Access, Snack Sync and Snack Connect have no System row. No feedback uses them.
What Systems Central does not do
It does not create, change or check the records of other bases. A Record Type row says where a table lives, but it does not create the table. A System Rule records a rule, but enforcement happens elsewhere (a formula, an automation, a script or a person; see Enforced By). A Work Item records work, but nothing here executes it.