banhmi: Instructions file for Codex

Repository rules

Project status

Development and maintenance have stopped. Retain the repository as an archive. Hosted endpoints are unsupported; deployment descriptions are historical. This status supersedes earlier delivery, maintenance, and cutover directions in the retained plans and designs. Do not resume development without new owner instructions. Repository safety, review, and Git rules still apply to authorized archival work.

Authority and reading order

AGENTS.md is the single current rule authority. Topic files add task-specific safeguards. Direct owner instructions take precedence. If project documents conflict, stop dependent work and resolve the shared documentation with the change. Read the documentation index, architecture, the applicable topic rules below, and the spec or design for the task. Read only the delivery plan sections the task touches. Designs are proposals unless labeled approved or implemented. Keep durable decisions in tracked repository records, not tool memory. Read short-term work for the current execution queue. The owning plans retain scope, milestone acceptance, evidence, and open decisions.

Product and evidence boundaries

• The former planned product was Tra cứu quy định at tracuuquydinh.vn, the approved, unbuilt direction in Website. banhmi remains the engine, repository, and corpus name.
• The archived scope prioritized Vietnam and retained Malaysia, Singapore, Indonesia, Thailand, and Cambodia on their existing danny.vn hostnames. That maintenance plan is no longer active.
• VNGCloud in Vietnam was the approved, unbuilt target for the new Vietnam system: serving, corpus writer and workers, review services, and artifact and backup storage. Keep writer and worker capacity separate from the serving host in the archived design. The Vietnam cutover is no longer planned. The former hosting requirements remain in the hosting decision.
• Serve evidence only. Our servers run no answer model, generative model, or reranker model. The query embedder is the only served model and runs on our own host. The user's own AI reads and judges evidence through the ChatGPT plugin or through /mcp in Claude and other clients.
• Decision: Reject a platform-run model and a reranker. Why: Sending user questions abroad is a cross-border transfer under Luật Bảo vệ dữ liệu cá nhân 91/2025/QH15, Điều 20. A reranker adds cost and latency with no gain over the user's own model. Rejected: Third-party question processing and query-time reranking. Detail: Public legal source documents may use approved cloud batch OCR and bulk embedding.
• Vietnam search accepts Vietnamese text with diacritics or a document number such as 50/2024/TT-NHNN. English is for interface text only. This requirement is approved, not deployed; the deployed MCP brief still says to translate first.
• Keep five MCP tools: guide, corpus_status, quality_gaps, search, and document.
• Keep a separate corpus and database per jurisdiction on one shared codebase. Preserve each jurisdiction's sources, language, parser, citations, validity, and evaluations. Evidence retains exact native citations, validity, relations, provenance, confidence, and known gaps. Accuracy takes priority over breadth. Never hide weak or missing evidence.
• Legacy and new corpus code are separate. Legacy is the v1 corpus code that serves the five maintained countries and the current Vietnam service: pkg/{app,ingest,extract,pipeline}, pkg/base/{jurisdiction,sourceurl}, the migration chains under deploy/migrations/, the query sources under sql/{bronze,silver,gold,ingest,config}, and their generated stores under pkg/store/{bronze,silver,gold,ingest,config}. Auth code, its chain, and pkg/store/auth are not legacy. Legacy is frozen: no new migrations, no new features, and no behavior change without an owner-approved maintenance fix. Legacy tests stay and run until the slice that retires their package deletes both together. New Vietnam code follows the approved layout.
• Decision: Build the new Vietnam corpus schema on fresh migration chains and freeze the legacy chains. Why: The Vietnam writer is a new database with no data to migrate. Appending to the legacy chains would carry their constraints, unused tables, and compatibility columns into a database that never held them. Rejected: Additive migrations on the legacy five-schema chains and a nullable legacy build_id. Detail: The corpus database spec names the chains, query sources, and generated-store paths. The engineering rules govern chain mutability and hosted generation.
• Report implemented code as coded. Report corpus behavior as validated only after checks against real documents. Report deployed behavior only after checking the deployed service.