Standards and best practices
Operator ETL follows established patterns for agentic data systems, government FOIA workflows, and maintainable Python projects. This page is the single index — why each pattern matters and which test proves it: FOUNDATIONS.md .
Knowledge and documentation
Standard
Reference
How we apply it
OKF v0.1
Google Knowledge Catalog OKF
okf/ bundle with typed frontmatter; validate with python3 scripts/okf_validate.py okf --strict
Progressive disclosure
OKF index.md pattern
Root okf/index.md → playbooks → code
README conventions
Make a README
Prerequisites, quick start, commands, doc map in README.md
Data architecture
Agentic AI
Security and compliance
Standard
Reference
How we apply it
PII fail-closed
FOUNDATIONS.md §5 — NIST SP 800-122
Scan before insight; encrypted vault; no MCP vault access
FOIA workflow
FOUNDATIONS.md §9
Public comments intake and redaction queue
Secrets hygiene
SECURITY.md
No .env, vault, or tfvars in git
Least privilege (GCP)
White paper §12.3
Separate service accounts per workload in Terraform
Engineering decisions (ADRs)
Documented in docs/Operator-ETL-White-Paper.md §3:
ADR
Decision
ADR-001
Medallion bronze / silver / gold
ADR-002
LangGraph over implicit agent loops
ADR-003
MCP as agent boundary
ADR-004
Fail-closed quality gate
ADR-005
DuckDB local → BigQuery GCP — okf/decisions/duckdb-local-bigquery-gcp.md
Python and repository
Implementation status
What is coded vs specified: okf/models/implementation-status.md
Update that matrix when shipping features; sync white paper badges on major releases.