> ## Documentation Index
> Fetch the complete documentation index at: https://docs.standardcomputers.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Bulletins: Keeping Distributed Standard Nodes in Sync

> Understand how the Standard System bulletin mechanism propagates record changes to all relay-connected nodes, keeping every system automatically in sync.

The bulletin is how relay-connected Standard System(s) keep records updated across all nodes connected to the relay. When records are created, modified, or removed on the relay, a bulletin packages those changes and distributes them to every connected node so that all systems stay in sync without manual intervention.

## How Bulletin Generation Works

Standard only generates a bulletin when it is set to `relay` mode. You can control how often bulletins are produced by setting the `release_cadence` property in your `config.conf` — a bulletin will be generated every X seconds as defined by that value.

When generating a bulletin, Standard checks the **history records** to determine which records have been created, updated, or deleted since the last bulletin. The bulletin contains a list of record IDs that need to be acted upon by the connected Standard System(s), along with the associated standards. Connected systems then begin downloading, updating, or deleting those records accordingly.

### Generate a Bulletin Manually

If you need to push changes to connected nodes immediately without waiting for the next scheduled bulletin, run the following command from the Standard CLI:

```sh theme={null}
bulletin
```

## Bulletin Format

A bulletin lists each affected standard by name, followed by brackets containing the record IDs and the action to be taken for each. The three possible actions are `add`, `update`, and `delete`.

Below is an example bulletin:

```text theme={null}
articles {
    ajs8ue8wla add
    j09ds7asyd update
    ha8sduiaok delete
}
```

Each line inside the brackets represents a single record. Connected nodes process every entry in the bulletin sequentially — fetching new records, applying updates, and removing deleted ones — until their local state matches the relay.