AI Strategy — Action Plans¶
This folder contains the execution plans that operationalise the Feoda Corporate AI Strategy. Each action plan turns a strategic objective or roadmap deliverable into a tracked workstream with an owner, milestones, and exit criteria.
The strategy says what and why. Action plans say how, who, and when.
Index¶
| ID | Action Plan | Strategy Reference | Owner | Target | Status |
|---|---|---|---|---|---|
| AP-01 | Identity-Bound AI Access | Objective 1; Phase 1 | Head of Technology | Month 6 | Not Started |
| AP-02 | Foundational AI Literacy Training | Objective 7; Phase 1 | Head of Technology | Month 6 | Not Started |
| AP-03 | Approved Provider List | Phase 1 deliverable; Section 8 | Head of Technology | Month 2 | Not Started |
| AP-04 | Documentation Governance Workflow | Objective 3; Phase 1 | Head of Technology | Month 9 | Not Started |
| AP-05 | Audit Logging Infrastructure | Phase 1 deliverable; Principle 5 | Head of Technology | Month 6 | Not Started |
Authoring Rules¶
- One action plan per file. Use the ID format
ap-NN-short-slug.md. - Each action plan must trace back to a numbered objective or named roadmap deliverable in the strategy.
- Update the status column above when status changes.
- Plans are living documents. Update milestones, blockers, and decisions as work progresses.
- When a plan completes, mark it
Completedhere and in its frontmatter; do not delete it. - Add a
CHANGELOG.mdentry when a new action plan is created or marked complete.
Status Definitions¶
| Status | Meaning |
|---|---|
| Not Started | Approved but no work begun |
| In Progress | Active delivery underway |
| Blocked | Awaiting decision or dependency |
| Completed | All exit criteria met and verified |
| Cancelled | Withdrawn before completion (with reason) |