Quality Notes - DocFlow Agent
Updated: 2026-05-30
These notes keep the repository easy to review without overstating what is production-ready.
Profile
| Field | Value |
|---|---|
| Repository | Upstage-DocuAgent |
| Primary stack | Python, Terraform, Docker |
| Review expectation | Local review should not require customer data or production credentials. |
Commands
| Purpose | Command |
|---|---|
| Full local gate | make verify |
| Test suite | python -m pytest |
CI
- .github/workflows/architecture-blueprint.yml
- .github/workflows/ci.yml
- .github/workflows/dependency-review.yml
- .github/workflows/pages-auto-deploy.yml
- .github/workflows/production-smoke.yml
- .github/workflows/repository-health.yml
- .github/workflows/repository-surface.yml
- .github/workflows/secret-scan.yml
Boundaries
- Demo, fixture, and synthetic-data modes must stay clearly labeled.
- Provider keys, tenant credentials, warehouse secrets, medical data, financial data, or customer logs must never be committed.
- Production claims require environment-specific validation, monitoring, rollback, and human approval paths.
- Screenshots, videos, and README claims should match the current implementation and documented commands.
Before Presenting
- README explains the user, the pain, the safety boundary, and the fast proof path.
docs/service-launch-playbook.mdexplains the product, pilot, service, or proof-of-value angle when relevant.- Tests or smoke checks are documented even when optional infrastructure is unavailable.
- Failure modes and unsupported claims are visible before the project is presented externally.
Checked-in evidence inventory
The following files and commands are discovered from this repository rather than inferred from a generic template. Their presence does not prove production readiness by itself; it gives reviewers a concrete path to reproduce the maintained checks.
Verification commands
make verify
Test files
tests/__pycache__/test_bugfixes.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_cors.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_demo_mode.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_edge_cases.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_extraction.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_frontend_metadata.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_gcp_artifacts.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_lms_export.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_logging_config.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_qa_pipeline.cpython-312-pytest-9.1.1.pyctests/__pycache__/test_smoke.cpython-312-pytest-9.1.1.pyctests/test_bugfixes.pytests/test_cors.pytests/test_demo_mode.pytests/test_edge_cases.pytests/test_extraction.pytests/test_frontend_metadata.pytests/test_gcp_artifacts.pytests/test_lms_export.pytests/test_logging_config.py
Continuous integration workflows
.github/workflows/architecture-blueprint.yml.github/workflows/ci.yml.github/workflows/dependency-review.yml.github/workflows/pages-auto-deploy.yml.github/workflows/production-smoke.yml.github/workflows/repository-health.yml.github/workflows/repository-surface.yml.github/workflows/secret-scan.yml
How to interpret the result
A passing local or CI check supports only the behavior covered by that check. It does not establish security certification, regulatory approval, clinical validity, production availability, or a customer outcome. Review the source, fixtures, environment assumptions, and failure paths before extending the result to another deployment.