cloud-itonami-isic-0620

Open Business Blueprint for ISIC Rev.5 0620: Natural Gas Extraction -- gas-well intake, per-jurisdiction well-construction/well-control/sour- service regulatory assessment, gas extraction, and production settlement for a community operator.

This repository publishes a natural-gas-extraction actor -- gas-well intake, per-jurisdiction gas-well-safety regulatory assessment, gas extraction and production settlement -- as an OSS business that any qualified operator can fork, deploy, run, improve and sell, so a regional producer never surrenders well-integrity and production- accounting data to a closed SCADA/production-AI SaaS.

Built on this workspace's langgraph StateGraph runtime (portable .cljc, supervised superstep loop, interrupts, Datomic/in-mem checkpoints) -- the same actor pattern as every prior actor in this fleet -- here it is GasFieldAdvisor ⊣ Gas Well Safety Governor. This blueprint's own :itonami.blueprint/governor keyword, :gas-well-safety-governor, is a UNIQUE keyword fleet-wide (grep-verified: no other blueprint declares it) -- a fresh, independent build, modeled on the closest sibling cloud-itonami-isic-0610 (crude petroleum extraction, ISIC 0610).

Unlike cloud-itonami-isic-4920 (which wraps a pre-existing bespoke capability library kotoba-lang/logistics), this vertical is SELF-CONTAINED: there is no kotoba-lang/natural-gas to delegate gas-well-safety validation to, so the reservoir-pressure / annular-vs- MAASP / CO2-corrosion / H2S-vs-IDLH range checks live as pure functions in gasfield.registry and are re-verified independently by the governor, rather than wrapping an external capability library's own validated function.

Why an actor layer at all? An LLM is great at drafting a gas-well summary, normalizing records, and reading a pressure gauge -- but it has no notion of which jurisdiction's well-construction/well- control/sour-service law is official, no license to open a real gas well to flow against a live reservoir or settle real production, and no way to know on its own whether the measured reservoir pressure actually lies inside the declared safe window, whether the annulus pressure is actually below the MAASP, whether the CO2 content is actually below the corrosion ceiling, or whether the H2S concentration is actually below the IDLH. Letting it extract gas or settle production directly invites fabricated regulatory citations, a gas well flowing with a lost zonal-isolation envelope or a corroded tubing string, and an extraction starting into a sour column above the IDLH -- exposing the crew to a lethal blowout and the operator to real liability, for whoever runs it. This project seals the GasFieldAdvisor into a single node and wraps it with an independent Gas Well Safety Governor, a human approval workflow, and an immutable audit ledger.

Scope: what this actor does and does not do

This actor covers gas-well intake through well-construction/well- control/sour-service regulatory assessment, gas extraction and production settlement. It does not, by itself, hold any mining/concession right or operating authority required to run a natural-gas-extraction business in a given jurisdiction, and it does not claim to. It also does not perform the actual physical drilling/workover itself, or judge reservoir economics -- reservoir simulation and recovery-factor optimization (the blueprint's own :optimization technology) is a follow-up slice, not in this R0. Whoever deploys and operates a live instance (a qualified production superintendent/operator) supplies any jurisdiction-specific operating authority, the real gas-wellhead/workover-robot dispatch integration and the real SCADA/production-accounting integrations, and bears that jurisdiction's liability -- the software supplies the governed, spec-cited, audited execution scaffold so that operator does not have to build the compliance layer from scratch.

Actuation

Extracting gas from a real well and settling real production are never autonomous, at any phase, by construction. Two independent layers enforce this (gasfield.governor's :well/extract/:production/ settle high-stakes gate and gasfield.phase's phase table, which never puts either op in any phase's :auto set) -- see gasfield.phase's docstring and test/gasfield/phase_test.cljk's well-extract-never-auto-at-any-phase/production-settle-never-auto-at- any-phase. The actor may draft, check and recommend; a human production superintendent is always the one who actually opens a gas well to flow or settles a production period. Grounded in well-control doctrine (the same discipline every regulator in gasfield.facts codifies: a real extraction and a real settlement are human sign-off acts) -- a genuine DUAL-actuation shape, applied SEQUENTIALLY to the SAME gas well (extraction first, settlement later), unlike retailops/4711's own :kind-distinguished alternative-action shape.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗