epic: Phase 2 — fail closed TEST and PROD

Open
#715 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@DerekRoberts is already working on this.

Since Sep 24, 2026.

Assessment

This issue has not been assessed yet.

Description

Phase: Phase 2. Reliability, after docs. Do not start until Phase 1's public ingest path is how documents land (human pull request of text that has passed parity; the image build does not fetch upstream legal text).

Decision (Derek Roberts, 2026-09-24)

He would rather the app be down than serve an incorrect answer.

Page a human for all of: deploy/health failure, wrong answers/citations, and a stale knowledge base. The alert channel is GitHub issues only, the same channel .github/workflows/merge.yml already uses at deploy time (bcgov/actions/workflow-notifier). No Slack. No email.

Stale knowledge base is not a new system. The drift issue opened by PR #696 (the scheduled check described in #695) is that alert. Do not file another stale-KB issue. Do not add a second stale-KB workflow or channel.

Forkability stays parked at #712. Telemetry (#340, draft PR #679) stays untouched.

Child issues

  • #713 — scheduled probe of /api/health on TEST bcgeu/navigator-test and PROD bcgeu/navigator. On failure, open a GitHub issue the way merge.yml does at deploy time.
  • #714 — a small fixed golden question set with expected citations, run against TEST before prod is promoted. A failure does not promote. Operator-visible result: a GitHub issue, and do not promote. No Hugging Face pause API.

Acceptance criteria

  • No work on #713 or #714 starts before Phase 1 public ingest is the path documents land on: parity-checked text committed by a human pull request, and the image build does not fetch upstream legal text.
  • A failed /api/health probe on TEST or PROD opens a GitHub issue and does not notify Slack or email (#713).
  • A golden-question failure on TEST bcgeu/navigator-test does not promote that image to PROD bcgeu/navigator, and opens a GitHub issue (#714).
  • The operator-visible result of a wrong-answer failure is that GitHub issue and no promotion. This epic does not specify a Hugging Face pause, restart, or sleep API.
  • A stale knowledge base still alerts only by the drift GitHub issue from PR #696. No additional stale-KB issue, workflow, or channel exists when this epic is done.
  • #340 and draft PR #679 are unchanged by this epic.
Dominant language
Python
Stars
2
Forks
1
Avg merge
4h 16m
Merged PRs (30d)
38

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MinionTech/vexilon

All issues in MinionTech/vexilon

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.