GovForge Backend
Python backend for GovForge: services + policy engine + FastMCP server + FastAPI HTTP API + SQLAlchemy models.
Stack
- Python 3.12+
- FastMCP 3.x — MCP server framework
- FastAPI — local HTTP API on
127.0.0.1:8787 - SQLAlchemy 2 + Alembic — ORM + migrations
- Pydantic v2 — schemas
- GitPython — read-only Git extraction
- SQLite (Phase 1, local-only) → Postgres (Phase 3 SaaS)
Layout
backend/
├── pyproject.toml
├── src/govforge/
│ ├── core/
│ │ ├── enums.py # 9 StrEnums (RiskLevel, DecisionStatus, …)
│ │ ├── ids.py # display-id helpers (TASK-001, DEC-001, …)
│ │ ├── models.py # 12 SQLAlchemy 2 entities + relationships
│ │ ├── git.py # read-only Git extractor (allowlisted verbs)
│ │ ├── policies/ # Policy ABC + 5 defaults + TOML loader + runner
│ │ └── services/ # 9 services orchestrating models + git + events
│ ├── mcp/ # FastMCP server (11 tools / 5 resources / 3 prompts)
│ ├── api/ # FastAPI app, deps, errors, routers/, schemas
│ └── db/ # engine + session factory + SQLite pragmas
└── tests/
├── unit/ # 88 unit tests across services / policies / API / MCP / git / security
└── integration/ # full pipeline test (devis §21.2)
Setup
cd backend
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest -q # 97 tests, ~3s
ruff format --check src tests
ruff check src tests
mypy src # strict mode
Running components directly
The user-facing CLI is gf (Go binary, in ../cli/). The backend is normally
spawned by gf mcp serve / gf api serve. For local development you can run
each component directly:
# MCP server (stdio transport — for Claude Code / Codex / Cursor / Cline)
python -m govforge.mcp.server
# HTTP API
python -m govforge.api.server # 127.0.0.1:8787
# or with reload during dev:
uvicorn govforge.api.app:app --host 127.0.0.1 --port 8787 --reload
The DB defaults to .govforge/govforge.db in the current directory; override
with GOVFORGE_DB=/path/to/file.db (or a full SQLAlchemy URL like
postgresql://…).
Architecture in one breath
agents (Claude / Codex / Cursor / …)
│ stdio
▼
FastMCP server ──┐
│
gf CLI ──HTTP─▶ FastAPI ──▶ Services ──▶ Models / SQLite
│ │ │
UI cockpit ───────┘ │ └──▶ Event store (audit log)
│
└─▶ Git extractor (read-only)
│
└─▶ Policy engine (5 defaults)
See ../docs/architecture.md for the full picture
and ../docs/data-model.md for the entity diagram.
Tests
| Layer | Coverage |
|---|---|
core/ |
84-100% |
mcp/ |
73-100% |
api/ |
76-100% |
| TOTAL | 90% |
pytest --cov=govforge --cov-report=term-missing
Security guarantees are pinned by source-grep tests in
tests/unit/test_security.py. See
../docs/threat-model.md.
License
Apache 2.0 — see ../LICENSE.
Metadata
Release files for govforge 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| govforge-0.1.2.tar.gz | 116.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| govforge-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 222.3 kB
Release files / govforge-0.1.2.tar.gz
| Download URL | govforge-0.1.2.tar.gz |
|---|---|
| Size | 116.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f5b3fbae417d5687b477daf71f09db1a0d60c1bf4c1e06c8dfc586545db0d11
|
|
BLAKE2b-256 checksum How to use checksums |
ec5617220e6ee259d98d3147bef1f0204bc22dd69f56bf3aab468e8020a10ed6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logRelease files / govforge-0.1.2-py3-none-any.whl
| Download URL | govforge-0.1.2-py3-none-any.whl |
|---|---|
| Size | 106.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c7ac9b4a6c6aaefd7acac173daf399950962ac836b37cf159df692b2be203c1
|
|
BLAKE2b-256 checksum How to use checksums |
eef418a94e35f19115a41d5238a46e2f3788d67d71de469f7f3f7abd3f6b9925
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logSecurity for govforge 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for govforge-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.