---
artifact_kind: policy-bundle-card
artifact_name: <e.g., "maat-procurement-standard-v1">
version: <semver>
owner: <team>
last_reviewed: <YYYY-MM-DD>
next_review: <YYYY-MM-DD>
domain: <maat | themis | kuanyin | yemaya | iris | aje | ...>
related_phase_179_tasks: [<...>]
---

# Policy Bundle Card — <artifact_name> v<version>

## 1. Identity

- **Bundle name:** <name>
- **Domain:** <subject-matter domain — procurement, governance, restorative,
  creative, etc.>
- **Use-case classes it applies to:** <subset of `ConcordiaUseCaseClass`>
- **Operational mode:** <which §179.1.2.3 mode this bundle runs in>

## 2. Contents

- **Clause templates included:** <list, each with short description and
  provenance>
- **Constraints enforced:** <discrete, temporal, fairness, legality>
- **Mandatory human-review flags:** <which clauses trigger which reviewer queue>
- **Jurisdictional coverage:**
  <which jurisdictions this bundle is appropriate for>

## 3. Sources

- **Drafting authority:** <who wrote the clause templates — counsel, procurement
  experts, restorative practitioners, DAO stewards>
- **Academic / professional references:** <cite sources; link to
  [`../../research/bibliography.md`](../../research/bibliography.md)>
- **Related institutional rules:** <AAA, JAMS, UNCITRAL, internal ombuds policy,
  etc.>

## 4. Evaluation

- **Coverage against domain precedent corpus:** <metric>
- **Enforceability audit:** <has counsel reviewed the clause templates?>
- **Fairness posture:** <does the bundle systematically favor one party type?
  How is this mitigated?>

## 5. Use

- **How Concordia loads this bundle:** <via `USE_CASE_CLASS_PROFILES` and tenant
  config>
- **Consumers:** <candidate-generation (§179.4.1), clause mutator (§179.4.1.3),
  static validator (§179.2.3.4)>

## 6. Refresh

- **Drift triggers:** <what changes in law, rules, or precedent force a bump>
- **Last refresh:** <YYYY-MM-DD>

## 7. References

- <links to the clause templates themselves, legal review memos, related cards>