Gas City Runtime & Pack Architecture Contract¶

Operating Principle¶

GAS_CITY_RUNTIME=YES

GASTOWN_RUNTIME=NO
GASTOWN_CONTROL_PLANE=NO

GASTOWN_PACK=OPTIONAL

Platform Architecture¶

Gas City
  = runtime / orchestration

BluCity
  = Bluefly's Gas City composition

BluCity-Packs
  = Bluefly reusable Gas City Packs

DrupalWorks
  = public reusable Gas City Pack

Gas Town
  = NOT our runtime

Explicit Boundary Discipline¶

GASTOWN_AS_RUNTIME=NO
GASTOWN_AS_AUTHORITY=NO
GASTOWN_AS_REQUIRED_DEPENDENCY=NO

GASTOWN_AS_OPTIONAL_UPSTREAM_PACK=YES
ONLY_IF_CAPABILITY_IS_USEFUL=YES

GAS_CITY_AS_RUNTIME=YES
GAS_CITY_AS_ORCHESTRATION_AUTHORITY=YES

Registry Evaluation Directive¶

Evaluate first-party Gas City registry Packs for reusable capabilities. Import only capabilities we actually need. The gastown Pack is optional configuration and does not reintroduce Gas Town as a runtime or control plane.

Application Rules:¶

Reusable roles, formulas, prompt fragments, and workflows defined in public registry Packs (including gastown) may be evaluated and selectively imported into Gas City pack configuration if and only if they provide required capabilities.
The presence of gastown Pack configuration does NOT introduce gt, Gas Town runtime stores, supervisors, path-derived identity, or ~/gt authority.
Gas City remains the sole runtime platform and orchestration authority across all Cities and Rigs.