---
type: ApplicationType
title: local-first-forge (application type)
description: Canonical data lives locally; remote forges are replication mirrors. Writes land on the local canonical store first and fan out.
tags: [application-type, catalog, rfc-114, local-first-forge]
timestamp: 2026-07-03T00:00:00Z
---

# local-first-forge (application type)

The **local-first-forge** type marks a forge-shaped system whose canonical data
store is LOCAL (a docs store / local DB in the operator's filesystem); the
remote forges (GitHub / Forgejo / GitLab) are replication mirrors. Writes land
locally first and fan out; a degraded remote queues, never blocks. The local-
first tradition's defining invariant applied to forge data.

## Entry (structured — the judgment-carrying-catalog schema)

```yaml
kind: application-type
id: local-first-forge
question: application-type
features:
  - id: canonical-local-mirror-remote
    signal: "the canonical store is local (docs repo / local DB); remote forges are replication mirrors — writes land locally first, replication_order lists the canonical first"
    observed_via: file-content
    probe: ".claude/forge-config.json::replication_order"
counter_features:
  - id: remote-canonical
    signal: "the remote service is the single source of truth; local state is a cache/clone"
    observed_via: judgment
lineage:
  tradition: "local-first software"
  exemplars: ["Ink & Switch local-first", "git (distributed canonical history)", "fossil (repo-local forge)"]
  reference: "RFC #114 / Discussion #114 derivation 2026-07-03"
examples:
  - "forge-manager server constituent (this repo), classified 2026-07-03 operator-confirmed"
```
