Region Package Standard
A region package is the single mechanism that makes the firm’s systems and products repeatable across areas of operation. One package per AO. Every domain consumes the same package through the ART-region-package seam; standing up a new AO means authoring one package, never forking a system.
The chain
Assessment drives configuration; configuration drives operation. Every configuration value (place term, venue, feed, contact) traces to a section of the driving assessment. Config invented without assessment basis is a defect.
Required components
| Component | Form | Derived from |
|---|---|---|
| Region descriptor | region.md cell (type region, RGN- DID) | this standard |
| Driving assessment | assessment/ (TVTA-class document package) | engagement scoping |
| Gazetteer / lexicon | config/keywords.yaml (threat terms weighted; place terms tiered) | assessment threat landscape and AO geography |
| Venues / geodata | assessment/*.csv, *.kml | assessment venue analysis |
| Feeds | config/feeds.yaml (RSS/API), config/x_accounts.yaml (curated sources) | AO media landscape survey |
| Contacts | config/contacts.yaml (LE, medical, embassy, vendors) | advance work |
Missing components are declared GAP rows in the descriptor’s component manifest, never omitted.
Lifecycle
author (engagement scoping) → validate (detail + intel review) → operate (systems load the package) → retire (archive with the engagement AAR). Package validity windows are stated in the descriptor.