Skip to content

MAYOR Fact Board

Authority

FACT BOARD = document/projection
WORKING PLAN = document/projection
ACTIONABLE WORK = Beads
LIVE TRUTH = actual runtime/tool evidence
Field Value
Purpose Verified projection of Oracle production observations for MAYOR/BLU. Not live truth. Not the work graph.
Authority GitLab Markdown in this file. Beads own actions. Oracle runtime owns operational truth.
Maintainer MAYOR (curation) · BLU (architecture) · WITNESS (independent proof)
Last verified 2026-09-10 (live overlay) · recovered snapshot 2026-08-24T17:15:30Z
LEGACY_SOURCE_URL https://claude.ai/code/artifact/ebf461bd-868b-4616-a267-a69343955071
AUTHORITY of Claude artifact NO
CANONICAL_SOURCE Engineering-Standard/operating-model/mayor-fact-board.md
Recovered payload Evidence/oracle-platform/claude-artifact-recovery-2026-09-10/mayor-fact-board.recovered.json
Rebuild bead bl-tf4

Update rules

  1. Read this document and the related Beads.
  2. Verify live evidence on Oracle (process, container, Dolt, GitLab). Never infer database absence from an unprivileged filesystem scan.
  3. Update this file on a feature branch. Mark stale rows SUPERSEDED or NEEDS_VERIFICATION. Do not silently delete corrections.
  4. Update related bead evidence/status. Do not paste the whole board into a bead.
  5. MR to release/v0.1.x. Never push main. Never edit the Claude artifact as operational authority.

Allowed STATUS: CONFIRMED · DEGRADED · BLOCKED · RESOLVED · SUPERSEDED · UNKNOWN · NEEDS_VERIFICATION

Every row: FACT_ID STATUS SEVERITY OWNER SOURCE VERIFIED_AT RELATED_BEAD SUPERSEDES NOTES

Current Production State

Live overlay measured 2026-09-10 on bluefly-platform (unprivileged + sudo). This overlay is a projection. Re-measure before acting.

FACT_ID STATUS SEVERITY OWNER SOURCE VERIFIED_AT RELATED_BEAD NOTES
live-city-root CONFIRMED high MAYOR ls /opt/bluefly/blucity 2026-09-10 hq-9df5 Canonical city checkout exists at /opt/bluefly/blucity. The 2026-08-24 claim that it did not is SUPERSEDED.
live-hq-prefix CONFIRMED high MAYOR .beads/config.yaml 2026-09-10 hq-x0rl Tracked prefix is hq. Live file also carries stray issue-prefix: bl, dolt.host, dolt.port, gc.endpoint_status: verified. gc bd refuses managed_city host/port.
live-gc-identity BLOCKED high MAYOR gc session list 2026-09-10 bl-5b39 bl-54a0f native_store_unavailable / metadata project_id is missing. Mail/sling from city checkout is blocked.
live-dashboard-backup CONFIRMED high ForgeOps ps + symlink 2026-09-10 gascity-dashboard executes from /opt/bluefly/.backup/gascity-dashboard. Do not touch until governed relocate.
live-agent-docker CONFIRMED high HARBORMASTER docker inspect bluefly-postgres-core 2026-09-10 Live Postgres mounts /opt/bluefly/agent-docker/deployments/oracle/services/data/.... Not a duplicate checkout.
live-unmounted-db UNKNOWN high HARBORMASTER du + find 2026-09-10 bl-7d7 1.3G at /opt/bluefly/infra/agent-docker/deployments/oracle/data (postgres-core, keycloak, timescaledb). Live containers do not mount it. DELETION_ALLOWED=NO. Recovery value NOT_ESTABLISHED.
live-second-city NEEDS_VERIFICATION high MAYOR sudo ls /opt/bluefly/.gc 2026-09-10 hq-9df5 Top-level /opt/bluefly/{.gc,city.toml,pack.toml} not visible. Nested city-shaped trees remain (.backup/bkp-city/.gc, infra/agent-docker/.gc). NEGATIVE_EVIDENCE_STRONG is not PROOF_OF_ABSENCE.
live-cleanup-freeze CONFIRMED high BLU blucity!222 2026-09-10 bl-tf4 Cleanup freeze is overlay law. PRESERVATION_COMPLETE=NO.
live-nas-p0a UNKNOWN high HARBORMASTER NAS home search 2026-09-10 bl-7d7 hq-2ym 33-commit NAS blucity tree not found under ~/ maxdepth 4. Preservation still required.

Confirmed Facts

Standing recovered facts from the 2026-08-24 artifact (do not treat as live without re-measure):

  • HQ Beads authority is Dolt 127.0.0.1:3308 database hq. Bind; do not restore/import JSON. Related: hq-x0rl.
  • Canonical city path is /opt/bluefly/blucity. Related: hq-9df5.
  • Standing constraint: no new projects, modules, recipes, or templates. Curate existing.

Active Incidents

See live overlay rows with STATUS=BLOCKED or NEEDS_VERIFICATION. Do not clean /opt/bluefly first.

Runtime Health

See live-gc-identity, live-dashboard-backup. Re-query systemd/docker before citing.

Data / Dolt / Beads Authority

Store Role
127.0.0.1:3308 / hq Canonical work graph
GitLab Markdown (this file) Projection
Claude artifact URL Historical reference only
Mac bc- prefix / city managed_city host keys Runtime dirt, not portable source

OpenClaw

08-24 board treated OpenClaw as independent of the city release-train blocker. 09-02 factory plan recorded gateway recovery via agent-docker MRs. Re-verify runtime before claiming HEALTHY.

NAS / Backup / Durability

Related beads: bl-7d7, hq-2ym, hq-8elp. Off-host preservation is not complete.

Filesystem / Deployment Drift

Related: hq-9df5, live overlay live-second-city, live-unmounted-db. Retirement must be surgical and deployment-driven.

Security Findings

08-24 artifact recorded credential-exposure facts (f8-*, f44-0). Open P0s bc-2s5, bc-3yu exist on the live bd list. Do not copy secrets into this document.

Capacity / Resource State

08-24 disk claims were corrected in-artifact (80% / 20 GiB). Re-measure. Do not use superseded 92% figures.

Decisions Required

None from the 08-24 board remain as open architecture. Path /opt/bluefly/blucity is decided (hq-9df5). Cleanup freeze is decided (blucity!222). Preservation complete only after independent bundles outside original trees.

Active Work

Item RELATED_BEAD Class
Fact Board rebuild / artifact retirement bl-tf4 ACTION
Bind Gas City to HQ :3308 hq-x0rl ACTION
City path convergence hq-9df5 ACTION
SEC-003 / gc bd under /opt bl-5b39 bl-54a0f BLOCKER
Factory substrate restore bl-32nn0 EPIC
NAS / Harbormaster durability bl-7d7 hq-2ym ACTION
Unmounted 1.3G DB tree bl-7d7 BLOCKER

Recently Resolved

09-02 factory plan listed 08-24 P0s (OpenClaw down, blucity repin, credential wave, illegal main targeting) as CLEARED. Those rows in the catalog below remain as chronicle (SUPERSEDED / historical). Do not reopen as current P0 without new evidence.

Unknown / Needs Verification

All STATUS=UNKNOWN rows in the recovered catalog, plus live overlay live-unmounted-db, live-second-city, live-nas-p0a.

Historical Notes

Claude artifact ebf461bd-868b-4616-a267-a69343955071 was updated in place and became a maintenance problem. Local HTML at /home/ubuntu/.oracle-mayor/board/oracle-mayor-fact-board.html is 2026-08-23 and is not the newest recovered copy. Newest recovered copy is Claude file-history artifact-ebf461bd-1787591730-9782.html (2026-08-24T17:15:30Z, sha256 f49eda442d19891947bace0404a6353f5c1bbbb37c01b4df0710e915058f595d).

Recovered fact catalog (177 rows)

Source: recovered JSON. VERIFIED_AT=2026-08-24 unless a live overlay row supersedes it. SOURCE=claude-artifact:ebf461bd.

FACT_ID STATUS SEVERITY OWNER TITLE SECTION
fla-identity CONFIRMED info Mayor Canonical city identity resolved: name=bluefly-engineering, path=/opt/bluefly/blucity slatest
fla-precedence CONFIRMED info Mayor gc name precedence (binary-verified): site.toml workspace_name > city.toml [workspace].name (legacy) > basename slatest
fla-cleanup CONFIRMED info Mayor The BluCity deploy is 8 additive-with-overwrite operations and cleans NO drift slatest
fla-reginert CONFIRMED info Mayor A perfect deploy leaves the new city UNREGISTERED and unstarted — registration hole owned by Foundry slatest
fla-dolt CONFIRMED info Mayor Estate has 4 Dolt endpoints; :3308 is the sole authoritative HQ store, disjoint from the others slatest
fla-mr64 CONFIRMED info Mayor !64 verified merge-ready at ref (name+pins+guard); retargeted feature->release, release->main still Thomas slatest
fla-guard CONFIRMED info Mayor city-toml-rig-guard was an UNEXERCISED control (coverage gap), not a masked one slatest
fla-secrets CONFIRMED info Mayor Secret residue ranked by REACH not count: argv 11, runner-env ~55, 1P-SA protected=false slatest
fla-nas CONFIRMED info Mayor NAS durability is broken at the mount: mnt-nas.mount failed since 08-19, no reachable off-host target slatest
fla-stubs SUPERSEDED info Mayor The flat /opt/bluefly/ dirs are beads endpoint-config stores, not empty slop; the real finding is triplication slatest
fla-bluguide CONFIRMED info Mayor Dropping the bluguide rig binding at deploy is safe — no live consumer slatest
fla-posture CONFIRMED info Mayor MAYOR operating read-only + beads-append: audit, prove, update the work graph, route to owners, verify runtime slatest
f0-cipush CONFIRMED info Mayor ci_push_repository_for_job_token_allowed set true on blucity — verified false, then set true; not sufficient alone s0
f0-0 CONFIRMED info Mayor HQ Beads authority = Gas City :3308 — 1233 total / 1142 hq-*, an exact match to the dashboard s0
f0-1 SUPERSEDED info Mayor ubuntu-qad3 — stamp:release cannot cut a tag, so nothing deploys to Oracle s0
f0-2 CONFIRMED info Mayor Docker daemon recovered, ~14 GB reclaimed, OpenClaw job now playable s0
f1-0 CONFIRMED info measurement A staircase, one step per waiting client s1
f1-1 CONFIRMED info measurement The gate was named before the run, and one deviation is recorded rather than hidden s1
f1-2 SUPERSEDED info measurement Correlation called a mechanism, then a retraction that was too broad s1
f1-3 CONFIRMED info measurement A disk sweep left running for 36 minutes stalled every agent on the host s1
f1-4 UNKNOWN medium measurement 94% full, churning with CI, and the daemon cannot report image sizes s1
f2-0 SUPERSEDED info openclaw "Wait for the deploy job to next fire" was waiting on an event source could not produce s2
f2-1 CONFIRMED info openclaw One override, written for merge requests, deleted the job's only main-branch rule s2
f2-2 CONFIRMED info openclaw The job that does deploy the openclaw profile aborted on an image that does not exist s2
f2-3 CONFIRMED info openclaw Four merges to close the source side; the job now exists and is manual by policy s2
f2-4 CONFIRMED info openclaw "Manual" is the deploy-boundary rule working. It also means nothing will ever fire on its own. s2
f2-5 CONFIRMED info openclaw The conflicting config pair is still live, frozen at the second the gateway died s2
f3-0 CONFIRMED info bd provenance Upstream is steveyegge/beads , not gascityhall/beads — and the revision is unavailable s3
f3-1 UNKNOWN medium bd provenance Three beads versions coexist on this host, and bd links its own Dolt s3
f4-0 SUPERSEDED info the disk is not static ~300 MB/day, and the lanes I was watching are all quiet s4
f4-1 CONFIRMED info the disk is not static The openchamber disconnect loop, one fifth of every syslog line s4
f4-2 UNKNOWN medium the disk is not static The obvious candidates are all evidence in open findings s4
f5-0 SUPERSEDED info four sweeps, no actor Identical-to-the-second across separate repositories is not hand editing s5
f5-1 CONFIRMED info four sweeps, no actor Three days older than any probing s5
f7-0 SUPERSEDED info a pattern, not an incident Wherever .beads is tracked, every probe is a silent source write s7
f7-1 CONFIRMED info a pattern, not an incident "Whenever convenient" is not a reason to touch production s7
f8-0 SUPERSEDED info credential exposure Exposure duration is the variable — this does not wait s8
f8-1 CONFIRMED info credential exposure Not resident anywhere on this host s8
f8-2 SUPERSEDED info credential exposure grep found itself s8
f8-3 UNKNOWN medium credential exposure Eleven containers still pass --token in argv s8
f9-0 SUPERSEDED info the workaround, named The one working ledger is embedded, single-writer, and has no remotes s9
f9-1 CONFIRMED info the workaround, named The shared endpoint exists by design — it is the thing that is down s9
f10-0 SUPERSEDED info two incidents collapse into one The merge that reintroduced the dead rig is the merge that triggered the deploy s10
f10-1 UNKNOWN medium two incidents collapse into one Three branches still carry the bad line — and none are queued s10
f10-2 CONFIRMED info two incidents collapse into one No reviewer of an "amcs pin bump" would have seen it s10
f11-0 SUPERSEDED info role correction The title conferred nothing and I wrote as though it did s11
f11-1 CONFIRMED info role correction Cloud-init ruled out. The probe hypothesis holds. s11
f11-2 SUPERSEDED info role correction The dead rig was removed, came back, and was removed again s11
f12-0 SUPERSEDED info a reasonable request, declined The variable does not exist, and this host cannot resolve the secret s12
f12-1 CONFIRMED info a reasonable request, declined A hand-recreated container reverts on the next redeploy s12
f12-2 UNKNOWN medium a reasonable request, declined Four secrets already reach this container by some path s12
f13-0 SUPERSEDED info correction The effective setting is disabled — someone chose it s13
f13-1 UNKNOWN medium correction Something ran as root on a host where nothing else does s13
f13-2 CONFIRMED info correction 17 legacy databases checked; the estate is not riddled with this s13
f14-0 SUPERSEDED info a bead that closed over its own gap hq-e3k closed while saying the check was still outstanding s14
f14-1 UNKNOWN medium a bead that closed over its own gap Telemetry enabled to an external endpoint, in a directory named ~ s14
f15-0 SUPERSEDED info verification working Scope, method, and arithmetic s15
f15-1 CONFIRMED info verification working Upstream is already running. The fork is one line from retirement. s15
f16-0 CONFIRMED info independent verification 11 of 14, derived twice, from opposite directions s16
f16-1 SUPERSEDED info independent verification Every component runs as one account that can become root s16
f16-2 UNKNOWN medium independent verification Errors go to a log nobody reads s16
f17-0 SUPERSEDED info reboot gate A precondition cannot require what it gates s17
f17-1 CONFIRMED info reboot gate All four fail right now, which is the gate working s17
f18-0 SUPERSEDED info mutation audit gc-worker is stopped but still enabled s18
f18-1 UNKNOWN medium mutation audit bd bootstrap left an empty ad on the canonical store s18
f18-2 CONFIRMED info mutation audit Three changes the governed deploy already reproduces s18
f19-0 CONFIRMED high the loop closed The job that wiped the work store no longer exists s19
f19-1 CONFIRMED info the loop closed 202 / 99 out, hashed, source unmutated s19
f19-2 SUPERSEDED info the loop closed I read a 23-commit-stale tree all session s19
f19-3 UNKNOWN medium the loop closed Startup failed, then deliberately stayed alive s19
f20-0 SUPERSEDED info retraction Both errors live in the same 1.3.2 binary s20
f20-1 CONFIRMED info retraction Docs track 1.4.x. This host runs 1.3.2. s20
f20-2 UNKNOWN medium retraction We cannot say what code runs production orchestration s20
f21-0 SUPERSEDED info the error printed its own answer city.toml is the sole source of truth. Zero of 14 rigs declare a path. s21
f21-1 CONFIRMED info the error printed its own answer The deploy pipeline creates the phantoms. Set equality, 8 of 8. s21
f21-2 SUPERSEDED info the error printed its own answer Right values, wrong file s21
f22-0 SUPERSEDED info attribution corrected site.toml has bound non-repositories since August 21 s22
f22-1 UNKNOWN medium attribution corrected Two unidentified actors write into the paths site.toml binds s22
f22-2 CONFIRMED info attribution corrected bluguide-maine is not adoptable s22
f23-0 SUPERSEDED info verify_all_rigs Only three rigs bind to a real repository s23
f23-1 UNKNOWN medium verify_all_rigs The obvious fix would surface six more failures and leave four phantoms s23
f23-2 SUPERSEDED info verify_all_rigs No runtime surface is not the same as not used s23
f24-0 CONFIRMED info ontology settled against the deployed contract Stored as a bead. Counted in city status. s24
f24-1 CONFIRMED info ontology settled against the deployed contract Six paths and a typed lifecycle in the event stream s24
f24-2 UNKNOWN medium ontology settled against the deployed contract No representation at all in the deployed platform s24
f25-0 CONFIRMED info control plane discovered Gas City Supervisor API — /openapi.json, 430 KB, 115 paths s25
f25-1 SUPERSEDED info control plane discovered All 100+ city-scoped paths return 404 — including the agent transport I could not find s25
f25-2 UNKNOWN medium control plane discovered Half the fleet has no artifact, and the policy engine governs itself s25
f26-0 CONFIRMED info custom code reduction Identical sets — zero difference in either direction s26
f26-1 UNKNOWN medium custom code reduction 41,585 lines, and most of it has a named upstream owner s26
f26-2 CONFIRMED info custom code reduction Twelve services, zero lines of code s26
f27-0 SUPERSEDED info scope corrected to Gas City Gas City only — the hook count was inflated s27
f27-1 CONFIRMED info scope corrected to Gas City gc sees 43 logical formulas; the duplicate spelling is invisible to it s27
f28-0 CONFIRMED info upstream-first evaluation Not a missing capability. A disabled one. s28
f28-1 CONFIRMED info upstream-first evaluation Upstream provides the exact mechanism being bypassed s28
f28-2 UNKNOWN medium upstream-first evaluation The docs and the binary disagree about beads storage s28
f29-0 SUPERSEDED info estate survey 43 formulas, doubled by naming, replicated across 13 rigs, all untracked s29
f29-1 UNKNOWN medium estate survey Most repos neither track nor ignore .beads/ s29
f29-2 UNKNOWN medium estate survey gc rig add --adopt would cement a phantom into tracked source s29
f30-0 SUPERSEDED info bootstrap resolved Oracle agents have no commit, no push, no filesystem write s30
f30-1 SUPERSEDED info bootstrap resolved Unblocking the store does not produce BLU s30
f30-2 UNKNOWN medium bootstrap resolved blu is not on PATH because its install is a dangling symlink s30
f31-0 SUPERSEDED info orchestration bd will not read a config that is sitting right there s31
f31-1 UNKNOWN medium orchestration 45 hook files hardcode the old city root s31
f31-2 CONFIRMED info orchestration Assigned and claimable — not delivered s31
f32-0 SUPERSEDED high reclassified DEPLOYMENT_DESTROYS_RUNTIME_AUTHORITY_BOUNDARY s32
f32-1 SUPERSEDED info reclassified A published fingerprint that would have failed verification s32
f32-2 CONFIRMED info reclassified Containment ended a 66,133-restart crash loop s32
f33-0 SUPERSEDED info both routed lanes expired Every path to Refinery and Witness is closed s33
f33-1 CONFIRMED info both routed lanes expired Both work items are now claimable cold s33
f34-0 SUPERSEDED info hypothesis tested The peak day is a steady baseline, not outage amplification s34
f34-1 CONFIRMED info hypothesis tested Dormant, not fixed — and nothing we did stopped it s34
f34-2 UNKNOWN medium hypothesis tested The CI fix will not reclaim any of this s34
f35-0 SUPERSEDED info sentinel audit returned Two of the three lanes were never delivered s35
f35-1 SUPERSEDED info sentinel audit returned The deploy also deletes overlays/ — which tracked config points at s35
f35-2 UNKNOWN medium sentinel audit returned The work plane accepts unauthenticated root from four bridge networks s35
f35-3 CONFIRMED info sentinel audit returned Per-path classification, so the invariant stops being a slogan s35
f36-0 SUPERSEDED info agent orchestration Agent creation is blocked by the same outage it would fix s36
f36-1 CONFIRMED info agent orchestration Three lanes working in parallel, none waiting on the others s36
f36-2 UNKNOWN medium agent orchestration A reboot re-runs the wipe sequence s36
f37-0 SUPERSEDED info current root is legacy /opt/bluefly/ holds a manufactured .beads and nothing else s37
f37-1 CONFIRMED info current root is legacy The 195 are legacy prefixes in correct databases, not orphans s37
f37-2 CONFIRMED info current root is legacy Nine change groups, fingerprinted, ready for BLU s37
f38-0 SUPERSEDED info order locked The uncommitted CI change still has no .beads exclude s38
f38-1 UNKNOWN medium order locked Five rigs exist at two paths at once s38
f38-2 CONFIRMED info order locked Source fix, then deployment fix, then runtime recovery s38
f39-0 SUPERSEDED info measured per rig, not inferred :36999 is a strict superset in every case tested s39
f39-1 CONFIRMED info measured per rig, not inferred The manufactured embedded store is empty and holds no evidence s39
f40-0 SUPERSEDED info root cause rsync --delete removes .beads because .beads is gitignored s40
f40-1 SUPERSEDED info root cause GitLab is not a recovery source, and the probe defect did not cause this s40
f40-2 UNKNOWN medium root cause :36999 is the only copy of all 202 records, anywhere s40
f40-3 CONFIRMED info root cause BLUCITY_DEPLOYMENT_ARCHITECTURE s40
f41-0 SUPERSEDED info mayor session ubuntu-45 A locked pack import that was never cached s41
f41-1 CONFIRMED info mayor session ubuntu-45 The reconciler had written 86,810 times. It is stopped. s41
f41-2 CONFIRMED info mayor session ubuntu-45 Managed endpoint UP — repaired with cache, not configuration s41
f41-3 SUPERSEDED info mayor session ubuntu-45 The canonical store restores from GitLab, not from :36999 s41
f41-4 CONFIRMED info mayor session ubuntu-45 The organization pack is live — eight of nine roles present s41
f41-5 UNKNOWN medium mayor session ubuntu-45 7 of 202 recovered records are safe to move. 195 are not. s41
f41-6 UNKNOWN medium mayor session ubuntu-45 Restore is blocked by a tool permission, not by authority s41
f42-0 CONFIRMED info standing at the production boundary CUTOVER_READY=YES · CUTOVER_AUTHORIZED=NO s42
f42-1 CONFIRMED info standing at the production boundary Harbormaster answered two days ago. Nobody could hear it. s42
f42-2 CONFIRMED info standing at the production boundary The 22 "unrecovered" tables were never populated. Nothing was lost from them. s42
f42-3 SUPERSEDED info standing at the production boundary bd refuses to connect when project identity disagrees s42
f42-4 CONFIRMED info standing at the production boundary Supported bd export → bd import reproduces the work exactly s42
f42-5 SUPERSEDED info standing at the production boundary Rehearsing only the smallest database had proven almost nothing s42
f42-6 CONFIRMED info standing at the production boundary 131-issue and 80-dependency imports both reproduce exactly s42
f42-7 UNKNOWN medium standing at the production boundary Cutover repairs BluCity work authority. It does not repair Oracle. s42
f42-8 CONFIRMED info standing at the production boundary Follow-on work is routed by the City, the moment the City can hold a bead s42
f43-0 SUPERSEDED info reconciled against the public dashboard bd ready [] was reported as an empty queue. It was an unreadable one. s43
f43-1 CONFIRMED info reconciled against the public dashboard Five durable ledgers on one host. The City points at the empty one. s43
f43-2 CONFIRMED info reconciled against the public dashboard The 713 items are Gas City's ledger, not BluCity's s43
f43-3 UNKNOWN medium reconciled against the public dashboard BluCity's own work is in a recovery directory, and dormant since 08-21 s43
f43-4 SUPERSEDED info reconciled against the public dashboard The session failure is not a version mismatch. It is the empty store, again. s43
f43-5 UNKNOWN medium reconciled against the public dashboard packs.lock carries an amcs pin that no commit contains s43
f43-6 CONFIRMED info reconciled against the public dashboard Gas City is the work authority again — the outage was mine, and the mechanism is now proven both ways s43
f44-0 SUPERSEDED high MAYOR Credentials are still world-writable on the host and still tracked on origin/main s44
f44-1 SUPERSEDED info MAYOR Six beads were closed today whose close conditions were contradicted by measurement s44
f45-0 CONFIRMED info MAYOR The durable work graph exists — this is what was missing s45
f45-1 CONFIRMED info MAYOR Run one closed the full loop — by hand, four times, same result s45
f45-2 SUPERSEDED info MAYOR "The formula is merged, so the City has it" — false, and it nearly produced a lying receipt s45
f46-0 SUPERSEDED info MAYOR I authored tracked BluCity source from production and pushed it s46
f46-1 SUPERSEDED info MAYOR I wrote a close condition that a correct fix could never satisfy s46
f46-2 SUPERSEDED info MAYOR A corrupted SHA in my own generated receipt s46
f47-0 CONFIRMED info MAYOR gc refused a close, and the refusal was correct s47
f48-0 SUPERSEDED info MAYOR A component contract break stops pipelines before any job exists s48
f48-1 UNKNOWN medium MAYOR The runner repair is authorized and still cannot be performed s48
f49-0 SUPERSEDED info run 002's first execution attempt am-ulx failed: dev-# does not pin what it looks like it pins s49
f49-1 CONFIRMED info run 002's first execution attempt Pinning moved to git; consumer-path fidelity kept via content comparison s49
f49-2 CONFIRMED info run 002's first execution attempt gc lint — real pre-merge validation existed the whole time s49
f49-3 SUPERSEDED info run 002's first execution attempt Two more near-repeats of the Oracle-authors-source violation — both caught before landing s49
f52-0 SUPERSEDED high MAYOR Load 325 with 4% iowait — the ledger, not the processor s52
f55-0 UNKNOWN medium MAYOR There is no deploy path to Oracle s55
f55-1 UNKNOWN medium MAYOR The public edge has no source definition s55
f55-2 UNKNOWN medium MAYOR Formula v2 {{issue}} breaks on the next Gas City release s55
f55-3 UNKNOWN medium MAYOR Contractors cannot reach the intended control plane s55
f55-4 UNKNOWN medium MAYOR Observability is emitting into a hole s55
f55-5 CONFIRMED info MAYOR kagent is deferred behind an independent Kubernetes decision s55