Pack Catalog¶
Authority: Portfolio-Registry.yaml (Engineering-Standard/authority/) Scope: Gas City packs — conceptual composition guidance plus inventory with immutable repository/release authority. Excludes application code. OBSERVED 2026-08-19 (docs.gascity.com/reference/specs/pack-spec): pack.toml carries only source+version (no ref/commit/hash fields); resolution is a separate pack-lockfile concern (gc import install). "Resolved Ref" means that lockfile-resolved value, not a value pack.toml would ever hold. Status: Authoritative Last verified: 2026-08-29
Upstream: Understanding packs, Pack spec, Shareable packs
Bluefly pack source: blueflyio/blu/blucity-packs
Purpose¶
Explain how Bluefly uses Gas City packs and list the inventory Bluefly products consume.
This file is the single Pack catalog (STD-CAT-003). Former gc-packs.md content lives here.
What a pack is¶
A pack is a reusable Gas City capability bundle (pack.toml, agents, formulas, orders,
doctor checks, assets). Cities import packs; they do not fork pack contents into
Engineering-Standard docs.
Upstream: pack.toml carries source + version; resolution/lock is a separate
pack-lockfile concern (gc import install).
Pack vs Mountain vs Rig¶
A Pack is reusable Gas City behavior — distinct from both portfolio and engineering-domain vocabulary (see gc-catalog.md):
- Mountain (portfolio taxonomy) does not directly "have" Packs. A Mountain's Projects may be delivered through Rigs that import Packs.
- Rig (engineering domain) is what imports/consumes a Pack via
[imports.*]. - Pack is the reusable unit itself, versioned and imported — it carries no portfolio ownership beyond its source repo.
How Gas City consumes packs¶
- City/root pack declares
[imports.*] - Rig defaults may import packs for every rig
- Builtin packs (
core,bd, …) are repaired bygc doctor --fix - Runtime install state on Oracle is evidence, not this catalog
Bluefly composition notes¶
| Concern | Owner |
|---|---|
| Pack source / version pins | blucity-packs + city/pack lockfiles |
| Pack inventory listing | this file (from Portfolio-Registry.yaml) |
| Builtin Gas City packs | Upstream Gas City |
| Runtime pack install state | Oracle city + gc import |
Catalog¶
Source of truth for rows is
Portfolio-Registry.yaml, reconciled againstblueflyio/blu/blucity-packs(release/v0.1.x). Blank Resolved Ref means lockfile not reconciled — fix via import/lock, not hand-filled SHAs here. Do not maintain a separate hardcoded prose count; verify count against the table rows directly.
Upstream / builtin packs (not in blucity-packs): 3
| Pack | Source Repo | Path | Imported By | Resolved Ref | Notes |
|---|---|---|---|---|---|
| core | gascityhall/gascity (upstream) | — | blucity root pack.toml | — | — |
| bd | gascityhall/gascity examples/bd (upstream) | — | blucity root pack.toml | — | — |
| gascity | gascityhall/gascity-packs (upstream) | — | blucity root pack.toml, defaults.rig.imports | — | — |
Bluefly packs (blueflyio/blu/blucity-packs, release/v0.1.x): 20
| Pack | Source Repo | Path | Imported By | Resolved Ref | Notes |
|---|---|---|---|---|---|
| amcs | blucity-packs | amcs/ | amcs rig only | — | Scope=rig; must NOT be city-level import (gc 1.4.x cartesian product) |
| bluguide | blucity-packs | bluguide/ | — | — | — |
| delivery | blucity-packs | delivery/ | — | — | — |
| digital-service-baseline | blucity-packs | digital-service-baseline/ | — | — | — |
| docs | blucity-packs | docs/ | — | — | — |
| drupal | blucity-packs | drupal/ | — | — | — |
| foundation-governance | blucity-packs | foundation/governance/ | blucity root pack.toml | — | Provides governance-weekly-audit order |
| foundation-identity | blucity-packs | foundation/identity/ | blucity root pack.toml | — | — |
| foundation-observability | blucity-packs | foundation/observability/ | blucity root pack.toml | — | — |
| foundation-security | blucity-packs | foundation/security/ | blucity root pack.toml | — | — |
| industry | blucity-packs | industry/ | — | — | — |
| kingstown-core | blucity-packs | kingstown-core/ | blucity root pack.toml | — | Provides blu agent and kingstown-core.blu named session |
| knowledge | blucity-packs | knowledge/ | — | — | — |
| lextown-criminal-core | blucity-packs | lextown-criminal-core/ | — | — | — |
| organization | blucity-packs | organization/ | blucity root pack.toml | — | Provides drupal, forge, foundry, harbormaster, sentinel agents |
| platform-beads | blucity-packs | platform/beads/ | blucity root pack.toml | — | — |
| platform-docker | blucity-packs | platform/docker/ | blucity root pack.toml | — | — |
| platform-openclaw | blucity-packs | platform/openclaw/ | blucity root pack.toml | — | Provides openclaw-ops agent, platform-openclaw-health-patrol order |
| repository-governance | blucity-packs | repository-governance/ | — | — | Provides repository-release-flow-adoption order |
| seo-pack | blucity-packs | seo-pack/ | — | — | Provides seo-specialist agent |
Relationships¶
Packs are imported by Products (see products.md). Source repos are governed by platform-ownership-matrix.md, not this file alone.
Rules¶
- Do not invent pack rows from memory or transcripts.
- Prefer extending an existing pack over creating a parallel Bluefly pack namespace.
- Pack schema / dirty Beads tables on a pack rig are runtime defects; remediate with Beads/Gas City native tools, not catalog edits.
- Do not recreate custom pack/database sync scripts when native GC/Beads primitives exist.