Repository navigation
ORCS Filing Reference Sheet
This document explains the role, structure, and classification mapping rules of the ORCS Filing Reference Sheet kept in policies/ORCS-Filing-Reference-Sheet.pdf.
The ORCS Filing Reference Sheet is a scanned, single-page official policy reference document provided by the Government Information Management Office (GIMO). It outlines the Operational Records Classification System (ORCS) standards, retention classes, and disposition rules specifically applicable to environmental assessment records and government decisions.
The AI Classifier Tool (AICT) uses the rules in this reference sheet to suggest records-management tags. By using deterministic type-to-ORCS mapping, the platform achieves high reliability without relying on runtime LLM inference.
graph TD
DOC[Uploaded Document] --> TYPE[Type Keyword Match]
TYPE -->|Assessment Report| ORCS1[ORCS: 15400-20]
TYPE -->|Certificate| ORCS2[ORCS: 15400-30]
ORCS1 --> RET1[7 Years Retention]
ORCS2 --> RET2[Permanent Retention]
The following mappings are derived from the reference sheet and implemented inside the rule-based classification configuration (document-types.yaml):
| Document / Artifact Type | ORCS Code | Retention Schedule / Disposition | Reference Sheet Section |
|---|---|---|---|
| Assessment Report (AR) | 15400-20 |
Semi-active retention, then archives | Environmental Assessment Reports |
| EA Certificate (EAC) | 15400-30 |
Permanent retention (Archived) | Certificate & Amendments |
| Process Order | 15400-40 |
Active during project lifecycle | Order & Process Rules |
| Exemption Order | 15400-50 |
Permanent retention | Exemption & Termifications |
Since the original file (ORCS-Filing-Reference-Sheet.pdf) is a scanned single-page image containing no selectable text, AI models and automated workers should interpret it using this Markdown sidecar or match the document type directly against the controlled vocabularies defined in DFL-Reference-Metadata.md and the rule-based structures in Document-Types-Draft.md.
- Environment Reality & Gotchas
- Architecture
- Seeding — filling Cosmos from Track and Eagle
- Sources and Status — every source, one state
- Search & Retrieval — overview
- Search Index Reference
- Search Query Construction
- Search Measurements
- Extraction Pipeline
- Extraction Quality — coverage, word-joining, tiling
- Identity Model — which id means what
- Attribute-Level Access — field-visibility levels, catalog
- Sync Architecture — how records get in
- Eagle Mirror Reference — mirrored kinds, refusals, drift classes
- ENGAGE Rows Reference — ENGAGE-owned comment periods, reconcile
- Public-Read Backfill — filling and repairing the mirror containers
-
Short Links —
/s/{code}redirect and/api/links -
Recent Uploads —
/api/documents/recent-uploads, eagle-public homepage panel - Reports — comment export and BCGW CSV reads
-
User Data — saved map areas, preferences,
/meroutes -
Bulk Download —
/api/bulk-downloads, zip jobs - Bulk Download: Operations — enable, poison-queue runbook
- Document Intake — upload link, malware scan, release
- Connecting an Application to DEMI
- Azure Environments
- Document Backup — archive copy of originals, run and check
- Document Backup: Revert and Drill — put documents back from the archive
- PDF Titles — public name written into stored PDFs, run, restore
- Secret Sync — Key Vault, secret-sync Function app, required names
-
Operating DEMI in Azure — deploy, verify
- Operating the DEMI Data Plane — devbox access, probes, audit and cost reads
- Edge ban detector — hourly timer, modes, kill switch, soak and promote
-
CI Workflows — every GitHub Actions workflow, trigger, identity, roles
- CI Deploy Workflows — eagle-demi staging and production deploys
- CI Admin Frontend Workflows — eagle-demi-admin checks and deploys
- Release Process — cutting, tagging, shipping and rolling back a version
- Runbook: Search Outage — index/app schema drift, diagnose, fix, roll back
- BC Gov Landing Zone
- Business Rules
- EPIC.search Business Rules — where DEMI differs from EPIC.search
- 001: Typesense for DFL Search — superseded
- 002: Async Processing (MongoDB Queue) — superseded
- 003: Rule-Based Classification
- 004: Read ACL Authorization Model
- 005: Cosmos Full-Text Search Ruled Out
- 006: AI Summarization over BM25
- 007: Service-to-Service Credentials
- 008: Audit and Usage Analytics Store
- 009: Track Feed — proposed
- 010: Attribute-Level Access Control
- 011: Public Read Surface
- 012: Public Config Surface
- 013: Stored Project Summaries — proposed
- 014: Sync-out to Eagle
- 015: Malware scanning on intake