OpenClaw Runtime Integration Boundary¶
Lawbooks: BluCity-Docs/library/governance/upstream-lawbooks.md (OpenClaw + Gas City + Gas City + Beads URLs)
Scope: Bluefly integration boundary for OpenClaw when used with Gas City, Gas City, and Beads. Authority: OpenClaw upstream docs for OpenClaw behavior; Gas City, Gas City, and Beads upstream docs for their behavior.
This document does not define Gas City, Gas City, Beads, or OpenClaw behavior.
Upstream References¶
- Gas City docs: https://docs.gascity.com/
- Gas City pack and city boundaries: https://docs.gascity.com/guides/shareable-packs
- Gas City runtime model: https://docs.gascity.com/getting-started/how-gas-city-works
- Gas City docs: https://docs.gascityhall.ai/
- Gas City workspace commands: https://docs.gascityhall.ai/usage/workspace/
- Gas City work-management commands: https://docs.gascityhall.ai/usage/work-management/
- Gas City service commands: https://docs.gascityhall.ai/usage/services/
- Beads docs: https://beads.gascity.com/
- Beads CLI reference: https://beads.gascity.com/cli-reference
Upstream Boundary Applied To OpenClaw¶
| Area | Upstream owner | Bluefly integration boundary |
|---|---|---|
| Gas City orchestration, packs, formulas, orders, agents, beads, and events | Gas City docs and gc CLI |
OpenClaw integration may invoke or observe documented Gas City behavior; it does not redefine it. |
| Gas City workspaces, services, diagnostics, communication, and work management | Gas City docs and gt CLI |
OpenClaw integration may expose operator access to upstream flows; it does not create alternate runtime state. |
| Beads issue/work state and Dolt-backed storage | Beads docs and bd CLI |
OpenClaw integration may display or route Beads state through documented output; it does not mutate storage internals. |
Bluefly-Owned Integration¶
Bluefly may define:
- where OpenClaw configuration is stored,
- which infrastructure repository deploys OpenClaw,
- which operator surface launches or observes upstream tools,
- which Bluefly policy, contract, and evidence systems wrap mutations,
- which GitLab projects own CI/CD and deployment definitions.
Bluefly must not define:
- Gas City command behavior,
- Gas City pack or runtime behavior,
- Beads storage behavior,
- OpenClaw upstream runtime behavior,
- alternate semantics for
gc,gt, orbd, - manual procedures for runtime state created by upstream CLIs.
Documentation Gaps (upstream specification, not Bluefly's to resolve)¶
- Mayor → Gas City ownership mapping is currently undefined by the
authoritative Gas City specification (
gas-city-master-spec.md§5'sgt → gccommand map does not list agt mayorrow in its direct, removed, or restructured mappings). Documentation Gap. .beads/config.yamlissue_prefixmutation authority is currently undefined by the authoritative Beads/Gas City specification. No upstream document reviewed states who may change a rig'sissue_prefixonce assigned. Documentation Gap.
Deployment Verification Required (not an architecture deficiency)¶
- Which
endpoint_originmode (managed_city/city_canonicalat City scope,inherited_city/explicitat Rig scope) the current Bluefly deployment runs. - Which host currently runs the live City instance.
These are deployment inventory questions, not architecture deficiencies.
Repository Ownership¶
| Area | Bluefly owner |
|---|---|
| OpenClaw container/runtime wiring | worktrees/agent-docker |
| Runtime network attachment | worktrees/agent-tailscale |
| Infrastructure provisioning | worktrees/iac |
| CI/CD components | worktrees/gitlab_components |
| Bluefly-owned Gas City packs | worktrees/blucity-packs |
OpenClaw gateway — Oracle only (binding)¶
RETRIEVED: OpenClaw upstream model is one authoritative gateway process per deployment — not active dual-gateway architecture.
OBSERVED (operator decision, 2026-07-07):
| Host | Role |
|---|---|
| Oracle | Authoritative OpenClaw gateway (copaw.us / production actuator) |
| NAS (Synology) | Storage, archive, install target, observability sidecars — not an OpenClaw gateway in this pass |
Deferred: NAS OpenClaw gateway, Synology Chat channel inventory, and second-gateway IaC. Revisit only after Oracle gateway is stable and repo cleanup completes.
IaC → Oracle → OpenClaw Gateway (authoritative)
NAS → storage / backup / operator tools (no OpenClaw gateway)
Upstream: https://github.com/orgs/openclaw/repositories
Convergence gates: infra-convergence-roadmap.md.
Runtime State¶
Runtime state belongs to the runtime that creates it. Bluefly integration documents may identify state boundaries, but repairs must use upstream-documented CLI commands or official diagnostics.
If upstream documentation does not prescribe a command or lifecycle, this document does not prescribe one.