Skip to content
GBOGEBPublic

About

CodeLLM and Deep Agent place to view and drop all files

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

8,501 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ABACUS — DOW analytical runtime, first-red diagnosis and CI

main version last release Enhanced CI Gating runtime: Python 3.14 GitHub Pages License: Apache-2.0

ABACUS runs the 12-cluster DMAIC analysis of cryogenic engineering data, and is where federation CI goes red-to-green at source: diagnose the first real failure, repair it, prove it on the exact head.

At a glance

Domain Multi-agent DMAIC analysis of cryogenic engineering data and documents (the DOW runtime) on the 12-cluster contract, plus first-red diagnosis, source-level CI repair and independent security for the federation
EPICs carried here CODE PURPLE evidence and coverage (#2720, #2326, #1944) · DAB static-analysis burn-down (#1609, #1866–#1868) · U-series CI hardening (#2669, #2721, #2722) · GOV-001 QPS cost roundtrip (#633) · QPS DOW coverage (#785)
Owner and decision authority Repository owner GBOGEB (CODEOWNERS): admission to main, releases and every external grant. No agent, bot or CI verdict holds this authority.
Role in the federation The runtime and repair shop: it executes the DMAIC analysis and fixes red CI where it starts; it does not own QPS engineering acceptance or federation governance.
Owns DMAIC_V3 runtime and the abacus CLI, the 12-cluster orchestrator, DOW/KEB bridges, the CI census and ratchets (TC0–TC4, DAB, Bandit, A10 guard), the docs/ Pages site
Does not own QPS engineering SSOT, OCD/ADR and release identity (cryoplant-project) · semantic provenance, federation contracts and the canonical Bradley–Terry/PCA engine (CODEX) · Kahn scheduling and the JADE census (Hub) · numerical method ownership (gg_MATH)
Status snapshot main@da5b6b7, read 15 November 2026 — 50 open issues, 16 open PRs. Details and closure proofs ↓

New here? Read §1 (2 min), then the route that matches you:

I want to… Open this first
Understand purpose, ownership and flow BIOS and from source to decision
Find the code for a cluster or DMAIC phase What is inside
Browse the rendered docs and dashboards Documentation site and the repository map page (finds files that used to sit at the root)
Run the tests myself rather than trust CI badges Run it locally
Know what is red, open, or next Status and open gates
Add or change a workflow Workflow rationalization and workflow policy
Read the release history (v2.2 → v4.4.0) Historical lineage

1. Why ABACUS exists — BIOS

B — Baseline. pyproject.toml [project].version is the release identity: main declares v5.0.0, and the last published release is v4.4.0 (18 May 2026). The 12-cluster contract is the architecture baseline; everything else is lineage.

I — Identity and integrity. A status claim names the main SHA it was read at. Release-era figures (v4.4.0's 95 % completion, 92.1 quality score, 90 % coverage) stay bound to that release and are never quoted as current-main health. New and changed files pass the A10 confidentiality guard before they land.

O — Orchestration with ownership. One canonical orchestrator, DMAIC_V3/core/twelve_cluster_orchestrator.py, drives DMAIC phases 1–8 across the twelve clusters. Wave claims in .waves/WAVE_CLAIMS.yaml are rolled up by CODEX; the JADE pointer .jade/repo.yaml names where each repository fact lives.

S — Safety and source-qualified status. UNKNOWN is not PASS or zero. A test stage that collects nothing is a failure. Coverage, false-green and lint ratchets are never relaxed to turn a check green.

Who uses it:

Reader Comes for Leaves with
External visitor What ABACUS is and how it is governed This page, the docs site, live issues
Engineer / analyst Run or extend the DMAIC analysis A feature branch, native tests, a PR
CI repair agent The next measured red to fix One root cause per PR, exact-head proof
Federation peer (CODEX, Hub, cryoplant) Runtime support receipts and QA A pinned ABACUS SHA and its evidence
Owner Decide admission A PR whose required checks are green on the final head

Where authority lives: pyproject.toml (release identity) · .jade/repo.yaml (repo pointer) · ci/governance/workflow_policy.json and docs/ci/WORKFLOW_RATIONALIZATION.md (which workflows are live) · governance/release_policy.yaml and governance/branching_model.yaml · .waves/WAVE_CLAIMS.yaml.

2. From source to decision

Every change, CI repair or status update follows the same loop:

  1. Refresh live main and read the open and recently merged PR state.
  2. Recover exact-head evidence for the commit in question: tests, checks, coverage.
  3. Re-census (TC0–TC4 completeness plus the DAB residual) so work is chosen from measurement, not memory.
  4. Repair the first material repo-local red only — one root cause per PR.
  5. Keep the ratchets: test count, coverage, false-green and lint baselines may only improve.
  6. Prove on the final head: the required checks on main (§6) must pass on the PR's last commit.
  7. Merge, read back main, and re-census before promoting the next residual.

3. What is inside

Block Native source Input → output Boundary
Canonical orchestrator DMAIC_V3/core/twelve_cluster_orchestrator.py, wrapper local_mcp/agent_orchestrator_v3.0.py Repository and document inputs → phase-by-phase DMAIC run with temporal hooks Orchestration evidence, not engineering acceptance
DMAIC phases 1–8 DMAIC_V3/phases/ Intake → metrics → root cause → improvement → control → knowledge → actions → TODO Each phase's output is input to the next, not a release claim
CLI DMAIC_V3/__main__.py (abacus entry point in pyproject.toml) abacus version (default) prints product and engine versions; abacus self-smoke runs configuration, import and schema probes (self_smoke.py) Does not run the DMAIC phases; a smoke receipt is not an analysis run
E6 knowledge layer phase6_knowledge.py, temporal_metadata_engine.py, handover_bridge.py Phase outputs → versioned knowledge references and handover state Handover documents are views of execution state
Tuple metadata src/dmaic/tuple_metadata.py, scripts/validate_tuple_metadata.py Tuple entries → validated bridge keys and status Schema validity ≠ content truth
CI governance and ratchets ci/governance/workflow_policy.json, tools/a10_guard.py, scripts/dab_formatter_lane.py, governance/dab/ Workflows, findings, diffs → classified census and fail-closed gates A green census row is not a release
Docs site and HTML exports docs/, scripts/generate_docs_html.py, deploy-docs.yml Markdown and data → Pages dashboards Rendered pages are not source authority
Federation and waves federation/, MIP/, .waves/ Peer receipts and wave claims → roll-up inputs for CODEX No transfer of another repo's ownership

12-cluster map

Cluster Phase Responsibility Entry point
C1–C2 1 Define Discovery and intake DMAIC_V3/phases/phase1_define.py
C3–C4 2 Measure Static metrics and baselines DMAIC_V3/phases/phase2_measure.py
C5–C6 3–4 Analyze / Improve Root cause and implementation changes phase3_analyze.py, phase4_improve.py
C7–C8 5–6 Control / Knowledge Quality control and orchestration hub phase5_control.py, phase6_knowledge.py, core/twelve_cluster_orchestrator.py
C9–C10 7 Action tracking KEB / GBOGEB runtime operations phase7_action_tracking.py, local_mcp/knowledge_integration_v2.3.py
C11–C12 8 TODO + temporal monitoring Temporal hooks and task governance phase8_todo_management.py

Architecture reading: 12-cluster vision · tool ecosystem map · bridges and connections.

4. Where ABACUS sits in the federation

ABACUS links to these repositories; it does not re-implement them.

Repository Keeps authority for ABACUS interface
pipeline-automation-hub (master) Mission Control, Kahn scheduling, JADE census, merge-governance evidence Census and readiness inputs; reusable workflows
CODEX Semantic provenance, federation contracts, MIP kit, Pages governance, canonical pca_engine Wave-claims roll-up; MIP kit pin; metrics schema shared with docs/api/dmaic_metrics.json
cryoplant-project (private) QPS engineering SSOT, OCD/ADR, release identity Exact-pin runtime support receipts (validation support only)
gg_MATH Numerical kernels and uncertainty methods Method source
GEMINI Cross-agent handover contracts Ecosystem dispatch target

Cross-repo hub map and public/private boundary: docs/integration/CROSS_REPO_MAP.md. Last cross-repo integration pass (25 Oct 2026): docs/INTEGRATION_REPORT.md.

5. Process diagrams

Declared architecture, not an execution receipt.

flowchart LR
    M["Live main"] --> E["Exact-head evidence"]
    E --> C["TC0–TC4 + DAB census"]
    C --> R["First material red"]
    R --> F["One-cause repair PR"]
    F --> G["Required checks on final head"]
    G --> MG["Merge + main readback"]
    MG --> C
Loading
flowchart TB
    A["Analysis tier · C1–C4"] --> D["Documentation tier · C5–C6"]
    D --> RC["Recursive tier · C7–C8 (orchestration hub)"]
    RC --> K["Knowledge and monitoring tier · C9–C12"]
    K -. "feedback into next DMAIC pass" .-> A
Loading

6. Status and open gates

Snapshot: main@da5b6b7, read 15 November 2026. Rows point at live owners; open the link for the current position.

Gate Status What would close it
Release identity main declares v5.0.0; last published release v4.4.0 (18 May 2026). No v5 tag yet. A tagged release cut from an admitted main SHA under release_policy.yaml
main protection Ruleset active: pull request required; required checks Python proof completeness, ABACUS compatibility gate, CodeQL, osv-scanner. 0 required approvals, so independent review is not enforced. Owner decision on review requirements, read back from the ruleset
Merge admission #1860 admission HOLD with a resume queue Exact-head findings dispositioned, manual review recorded
Flaky test leg #2669 coverage DataError under -n auto --cov Deterministic coverage combine under xdist
Workflow fan-in #2722 PR Feedback Gate Evaluator triggered by 15 workflows Fan-in collapsed; superseded-run cancellation already merged in #2741
Collection gaps #2721 deselected tests; #2733 open Each deselection collected or skipped with a recorded reason
Dashboard deploy #2728 gh-pages 403; #2758 removes the dead job PR merged; Pages stays workflow-built
Formatter burn-down Black lanes W00–W02 of 4 merged 15 Nov (#2747, #2748, #2750); Bandit ratchet key fix #2740 open Lane W03 merged; ratchet keyed wrap-insensitively (#2712)
Workflow estate 224 workflow YAML files under .github/workflows/ at this snapshot; which ones are live is decided by policy, not by count Workflow policy and rationalization kept current

Live metrics (self-updating, read from docs/api/dmaic_metrics.json on main):

DMAIC quality commits test files workflows metrics SHA

7. Run it locally

PR checks run on Python 3.14 (.python-version, Enhanced CI, smoke-test, a10-guard); pyproject.toml declares >=3.11. Test on 3.14 before calling a change verified.

git clone https://github.com/GBOGEB/ABACUS.git
cd ABACUS
python -m pip install -r requirements-dev.txt   # as the Enhanced CI test job does
python -m pip install -e .
python -m pip install pytest pytest-cov pytest-benchmark pytest-xdist
make test                      # pytest DMAIC_V3/tests -q
python -m pytest -q            # testpaths from pytest.ini: tests, DMAIC_V3/tests
python tools/a10_guard.py --staged    # pre-commit mode: checks staged files only

Do not combine requirements.txt with requirements-test.txt: their pytest-asyncio pins conflict on Python ≥ 3.10. a10_guard.py has no --help; without --staged or --diff BASE it scans every tracked blob. Local runs are a development path, not native CI. Exact-head evidence lives in Actions on the PR's final commit.

8. Evidence rules and non-compensation

  • Source → validator → exact-head execution → owner admission → derived view. A later step never stands in for an earlier one.
  • UNKNOWN is not PASS or zero; zero collected tests is a failure.
  • Historical release figures are bound to their release; current-main health comes from the live census and Actions.
  • Raw debt counts are kept next to classified counts; classification never erases the raw number.
  • Runtime support to QPS is validation support only: it transfers no engineering, procurement or acceptance authority.
  • Deferred reviews follow ABACUS_DEFERRED_REVIEW_POLICY.md. Report vulnerabilities via SECURITY.md.

9. Repository map and next actions

Source Why open it
DMAIC_V3/ Runtime package: core, phases, tests
src/, tools/, scripts/ Libraries, guards, CI and analysis scripts
tests/ Repository-level tests (plus DMAIC_V3/tests)
ci/, governance/ Workflow policy, ratchet baselines, release and branching policy
docs/ Pages site source, CI docs, integration reports
docs/repo-structure/ Root refactor plan and the map of moved root files
federation/, MIP/, .waves/ Federation inputs, MIP rollout, wave claims
CODE_MAROON/ Security check-and-fix programme notes
docs_versioned/ Versioned handover and release-era documentation
Issues, pull requests, Actions Live queue, PR heads and CI evidence

Next governed actions, in order:

  1. Land the open repair PRs one cause at a time: #2758 (dead deploy job), #2740 (Bandit key), #2733 (staging skip reason).
  2. Fix the flaky coverage leg (#2669) so required checks stop needing reruns.
  3. Collapse the PR Feedback Gate fan-in (#2722).
  4. Finish the formatter lanes (W03) and keep the flake8/Bandit ratchets moving down.
  5. Owner: decide whether main requires an independent approval, then read the ruleset back.
  6. Re-cut this status snapshot at the new main SHA when any of these moves.

Historical lineage

Release-era records (v2.2 → v4.4.0) and superseded status pointers

These records are kept for traceability. They describe the state at their own date, not current main.

Record What it was
v4.4.0 release notes, announcement, final status dashboard, completion report Last published release (18 May 2026): 95 % completion, 92.1 quality score, 90 % coverage — release snapshot figures
Master handover index V2.2/V2.3-era one-page overview
docs_versioned/v2.2_archived/ V2.2 (Nov 2025): orchestrator framework, MCP controller, 21/21 tasks
docs_versioned/v2.3_active/ V2.3 development snapshot that led to v4.4.0
Progress tracker Module status as of May 2026
Execution state of 2 Oct 2026 Pointed at commit 329562a, PR #1667 and the ci-enhanced.yml rank-1 lane (#1671). Superseded; see commit history
Cross-repo smoke pass of 25 Oct 2026 6254 passed / 37 skipped at that time; full record in docs/INTEGRATION_REPORT.md

Still-open proof gates carried from that era: repository-wide folder refactor closure, end-to-end deployment readiness and production readiness. None is claimed by this page.


BIOS: 12-cluster DMAIC runtime + exact-head first-red repair. Release authority: repository owner; identity from pyproject.toml. Source licence: Apache-2.0, GBOGEB as source generator and owner. Landing: R2 of the shared skeleton, cut at main@da5b6b7 on 2026-11-15.

About

CodeLLM and Deep Agent place to view and drop all files

Resources

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages