Configure write and list authority

Set root authority so the Enterprise Compiler knows which Business Entity is the preferred write/list candidate for a shared resourceType when multiple writable Connected Systems exist.

Why this matters (product story): Write and list authority across systems — multi-system participation with preferred writes from metadata, not custom glue. This page is only the configure how-to.

Do not confuse this with syncBridge (disabled / master / bidirectional), which only controls enterprise synchronization participation. See Configure sync bridge.

Use authority when two or more Connected Systems expose the same Resource Type with writable capabilities and operators need one preferred system for create/update/list routing in Enterprise Knowledge compilation. If only one writable datasource exists for that Resource Type, you can usually omit the flag and rely on implicit authority.

Prerequisites

entityType: recordStorage with a stable resourceType
Writable CIP operations when this entity should accept updates (update / create as required)
Awareness of other published datasources that share the same resourceType
Login and validate/upload rights for the Connected System package

Where it lives

Layer	Location
Authority flag	`<datasourceKey>.json` → root `authority` (boolean, default `false`)
Sync participation	Same file → root `syncBridge` (separate concern)
Compiled effect	Enterprise Knowledge / COM write routing and compiler findings

How to set

Inventory writable entities that share the same resourceType across Connected Systems.
Choose one preferred write/list authority for that resource type (or rely on implicit authority when only one writable source exists).
Set the flag on the preferred datasource root:

{
  "authority": true
}

Leave contributors at authority: false (or omit — default false).
Validate and upload:

aifabrix validate <systemKey>
aifabrix upload <systemKey>

Re-check compiler / online findings if writes are disabled after multi-system publish.

When you change which system is authoritative, clear the previous authority: true (set false or omit) before marking the new preferred datasource. Leaving two authorities true for the same Resource Type produces compiler conflict findings.

Defaults and examples

Value	Meaning
`false` (default)	Not the preferred write/list authority candidate
`true`	Preferred write/list authority for this `resourceType` when several writable sources exist
Omitted on sole writable	Implicit authority is allowed when only one writable datasource exists for the resource type

Illustrative fragments (two systems, same resource type):

{
  "key": "crm-a-customers",
  "resourceType": "customer",
  "authority": true
}

{
  "key": "crm-b-customers",
  "resourceType": "customer",
  "authority": false,
  "syncBridge": "bidirectional"
}

In that pattern, crm-a-customers is the preferred write/list candidate while crm-b-customers can still participate in sync without claiming authority.

Validate

aifabrix validate <systemKey>
aifabrix upload <systemKey>
aifabrix show <systemKey> --online

Expect compiler findings when multiple writable sources lack a clear preferred authority, or when authorities conflict for the same resourceType. After a successful upload, confirm the preferred system still exposes the expected write capabilities under Operational Trust — authority is metadata routing, not a permission bypass.

Common mistakes

Mistake	Fix
Treating `syncBridge: master` as COM authority	Set root `authority` separately
Multiple `authority: true` for one resource type	Keep a single preferred authority
Expecting Role Assistant catalogs to pick write targets	Catalog membership ≠ write routing
Setting authority without writable CIP ops	Enable and certify update/create as needed

Limits

Authority is a preferred write/list routing candidate for Enterprise Knowledge compilation. It does not bypass Operational Trust, RBAC, or ABAC at execute time. Sync bridge modes remain independent. Role Assistant package promote and Evidence authoring do not set Connected System authority — configure it on Business Entity datasources as shown above.

Documentation Index