• Name: SIMULATION — AICT Guidelines (structured)
• Role: Reasoning half of the AICT Insight Generator — the director's judgment. Twin of F (the generator, the mechanical half that ENACTS these).
• Purpose: Sortable / shuffleable guideline store. Each guideline is a unit you can re-order, re-kind, or re-status. Derived from the prose in 'SIMULATION — Per-Document Population.md' (003 - AICT Schema); that .md stays the narrative, this is the workbench.
• Created: 2026-06-09
• Sort_keys: ['kind', 'status', 'seq']
• Kinds: ['Core Position', 'Director Guideline', 'Principle', 'Assumption', 'Candidate']
• Statuses: ['active', 'parked', 'candidate', 'promoted']

• Kind: Core Position
• Status: active
• Source: A - Design Foundations
• Targets: document_type, phase, milestone

Document Type is the valve and platform where the EA-process lineage (Phase → Milestone) is expressed and evolves. We design INTO the existing system, not OVER it — EPIC's Phase/Milestone values stay as-is for now; Document Type carries both today's state and the direction of travel.

---

• Kind: Core Position
• Status: active
• Source: A - Design Foundations
• Targets: document_type, act-legislation

Doc-type values take their names from the artifacts the legislation names (order, certificate, exemption…), NOT from Phase/Milestone labels. The Act is the source of the vocabulary; as the operative Act changes (1996→2002→2018→future) the named-artifact set is what Document Types align to. (Direct tie to PRIN-02 root-concept threading.)

---

• Kind: Core Position
• Status: active
• Source: A - Design Foundations
• Targets: legislation, operative-act, date

Record Act-year as the standard anchor, but Document Date is first-class. In a transition window (2018 EAA enacted 2018, in force 16 Dec 2019) the year alone can't resolve the operative Act — the AICT resolves it from the document's date and event sequence. Deeper pass runs only when an overlap arises.

---

• Kind: Director Guideline
• Status: active
• Targets: assessment, evidence, triangulation

Consult the record around the document; EPIC fields are evidence sites, not authorities. Triangulate and weight by reliability.

• Arrival volume is a prior — tide membership ≈ application bulk; solo drips raise the spine prior. Volume is inversely correlated with meaning.
• Triangulate the witnesses — Description × Phase × Milestone, weighted (TYPE holds at volume, PHASE wobbles, MILESTONE worst where the record is most alive).
• Mine the title — titles smuggle externalized attributes (condition numbers, revisions, gate status, case IDs); densest classification signal in the corpus.
• Know where the vocabulary goes silent — post-decision 'Other'-milestone ≈ certificate-holder lifecycle material the vocabulary never named; silence is signal.

---

• Kind: Director Guideline
• Status: active
• Targets: legislation, act-transition, project-level-finding

Multi-Act is retrospective, never an in-the-moment fact. The director scans a project's docs for transition signals (Act Transition Request · Act Transition Decision · New Act Notification · Cross-Act Consolidation · Cross-Act Narrative). Per-doc legislation stays SINGLE-Act; the cross-Act span is a project-level AICT finding assembled from evidence.

AICT lives as placeholders inside dimensions (e.g. LEGISLATION.AICT) for now — clean carve-out is sound long-term but no runway. Empty placeholders are deliberate.

---

• Kind: Director Guideline
• Status: active
• Targets: document_type, assessment, drift-check

Assess L1/L2/L3 independently against the full document + context, then synthesize a Suggested Match. The declared value (EPIC's label) is a signal to check, NOT the path to descend. Disagreement (between levels, or suggested-vs-declared) is signal, not error. Greedy top-down locks in early wrong turns; holistic with full info doesn't. Records: Value(declared) · L1/L2/L3 · Suggested Match.

---

• Kind: Director Guideline
• Status: active
• Targets: graze, triage, scope

Runs BEFORE doc-type assessment. A fast graze flags project-content bulk (application materials, descriptions, technical memos, studies, plans — ~76%), sets it aside (Project Content = YES), and does NOT individually classify it. Detailed assessment runs only on the remainder (orders, decisions, certificates, amendments, letters). First Cariboo pass: 434 isolated / 150 assessed = 74% scope cut. Flag rides as a filename SUFFIX (see DG-05).

---

• Kind: Director Guideline
• Status: active
• Targets: vein, sort, filename, coarse-prior

After the graze, append a coarse two-letter vein as a filename SUFFIX — ' -[VV] -P.json'. Original names preserved; the vein is a reference handle ('if not here, look in this body'). It's a coarse prior the fine doc-type assessment can agree/disagree with. Coarse and reversible by design.

Code	Name	Precedence	Note
PT	Project Technical Detail	1	graze bulk; kept tight
CP	Certificate Proper	2	core issued certificate, isolated
PE	Public Engagement	3	public-facing signatures
AT	Act Transition	4	carved out even from a communication
CM	Communication	5	residual letters; lowest-precedence function vein
OA	Official EA Artifacts	6	orders, amendments, transfers, extensions, certifications, C&E
LF	Leftover	7	deeper look

---

• Kind: Principle
• Status: active
• Targets: value, glyph, drift-check

Declared values come from the data schema (🔒 ETL (EPIC) / System (DFL)); AI-assessed values come from the director (🔒✨🤖✨ AICT). Keeping both side by side is the built-in drift check.

---

• Kind: Principle
• Status: parked
• Targets: rollup, phase, milestone, artifact, act-legislation

One root noun threads through all three levels wearing a different qualifier at each: application → 'Application Development & Review' (phase) / 'EAC Application' (milestone) / 'Application Materials' (artifact). Follow the root to roll a document up to its phase/milestone; the QUALIFIER sets the level (phase=stage descriptor, milestone=checkpoint, artifact=doc suffix); the static reference (Act/e-guide) fixes the phase vocabulary.

---

• Kind: Assumption
• Status: active
• Targets: project, reference, snapshot

Population presumes a project table the AICT reads at assessment time. Reality: EPIC has no project record system — the DFL must mint it. User values are never accepted raw; they're validated against project state — and the document under assessment may itself ADVANCE that state (decisions, orders, transfers, amendments). Hence the per-doc Project Snapshot = state at that moment, not forever. Reference home: C → REFERENCE TABLES → Projects.

---

• Kind: Candidate
• Status: promoted
• Source: A - Design Foundations
• Targets: director, graze

Candidate position that has since been realized — promoted into DG-04 (the grazing pre-pass). Kept here for lineage.

---