epic: Phase 1 — useful steward corpus (public parity first)

Open
#716 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 1. Docs first. This epic is the order and the gates. #700 is the design.

Decision (Derek Roberts, 2026-09-24)

Order is docs, then reliability, then forkability. Forkability is nice-to-have, not a priority. He would rather the app be down than serve an incorrect answer.

Public parity first. Member-portal documents only after an export path exists. my.bcgeu.ca cannot be fetched by the public HTML sentinel. Member docs are out of this epic until #711 is done.

If a fork ever happens, a stranger forks, brings their own documents (URLs, PDFs, Markdown), and hosts on their own Hugging Face Space. Not a template product. Not MinionTech-hosted multi-tenant. Victoria School Board is an illustration only. They are not customers. Nobody is a customer. Do not build a Victoria bot. The parked contract is #712. Phase 1 ingest stays declarative so that stays possible. Forkability is a constraint on ingest shape, not a workstream in this phase.

Alert channel, when a human is paged, is GitHub issues only. No Slack. No email. That paging work is Phase 2, not this epic.

Telemetry (#340, draft PR #679) stays untouched.

Gates

  • No committed legal file is deleted without substantive parity. A human pull request updates legal text. The image build does not fetch upstream legal text.
  • #696 is the HTML sentinel already in flight (feat/automate-doc-ingestion). Do not open another pull request for that work.
  • Public sources already in git (statutes, OHS, WCB, agreements) get a parity pass before replacement.
    • PDFs: #699
    • HTML sentinel: #695 and PR #696
  • #701, #702, and #703 stay out of this epic until #711 (export of my.bcgeu.ca, plus Derek's yes to commit that text).

#697 and #698 stay children of the design epic #700. They are not re-filed here and they are not a Phase 1 gate.

Sequenced work

  • #700 — design: declarative link-driven knowledge base
  • #695 / PR #696 — HTML sentinel already in flight. No second pull request.
  • #699 — PDF extraction and shadow-audit of multi-part statutes
  • #711 — member-portal export gate. Blocks #701, #702, #703. Not part of the public parity pass.

Acceptance criteria

  • Every public source already committed under app/data/ (statutes, OHS, WCB, agreements) has a recorded parity result against its upstream before any replacement. PDF sources are the work in #699. HTML sources are the sentinel in #695 and PR #696.
  • No pull request in this phase deletes a committed legal file unless that parity result shows substantive parity.
  • Legal text changes land only through a human-reviewed pull request. app/Containerfile and .github/workflows/pr.yml do not fetch upstream legal text during the image build.
  • PR #696 remains the in-flight HTML sentinel. No second pull request is opened for that sentinel from this epic.
  • app/data/sources.yaml stays the declarative registry (URLs, PDFs, Markdown), so #712 stays possible without a second bot.
  • #701, #702, and #703 have no ingestion work under this epic. They stay blocked on #711.
  • #340 and draft PR #679 are unchanged by this epic.

Later public sources

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.