diff --git a/workplans/ITC-WP-0017-agentic-drives-functional.md b/workplans/ITC-WP-0017-agentic-drives-functional.md
new file mode 100644
index 0000000..b5eabd1
--- /dev/null
+++ b/workplans/ITC-WP-0017-agentic-drives-functional.md
@@ -0,0 +1,69 @@
+---
+id: ITC-WP-0017
+type: workplan
+title: "AgenticDrivesFunctional PracticePattern"
+domain: infotech
+topic_slug: canon
+repo: info-tech-canon
+status: active
+priority: medium
+created: "2026-08-22"
+updated: "2026-08-22"
+owner: codex
+related:
+  - ITC-WP-0016
+spec_refs:
+  - infospace/patterns/PracticePatternScheme.md
+  - infospace/patterns/AgenticDrivesFunctional.md
+---
+
+# ITC-WP-0017 — AgenticDrivesFunctional PracticePattern
+
+## Goal
+
+Name and document the practice of using agentic cross-repository work records
+as a flexible demand-discovery channel, then converting repeated, stable demand
+into direct functional service interfaces that reduce latency, token use, cost,
+and approval relays.
+
+## T01 — Define the practice
+
+```task
+id: ITC-WP-0017-T01
+status: progress
+priority: high
+```
+
+Document the context, forces, solution, feedback dynamics, invariants, evidence,
+consequences, and failure modes. Preserve repository ownership and explicit
+third-party approval boundaries while making the direct-interface-first rule
+clear.
+
+## T02 — Register and publish the pattern
+
+```task
+id: ITC-WP-0017-T02
+status: pending
+priority: medium
+```
+
+Register the artifact and its relationship to `InterfaceDeprecationStrangler`,
+add it to the pattern catalog, refresh generated retrieval assets, and validate
+the canon.
+
+## Acceptance
+
+- [ ] `AgenticDrivesFunctional` conforms to PracticePattern v0.1.
+- [ ] The pattern distinguishes direct interfaces from cross-repo task routing.
+- [ ] Repetition is treated as evidence for interface review, not an automatic
+      mandate to build an interface.
+- [ ] Interfaces preserve authorization, credential custody, and third-party
+      approval boundaries.
+- [ ] The pattern is registered, retrieval-visible, validated, committed, and
+      synchronized.
+
+## Out of scope
+
+- Implementing a new service API, CLI, or MCP interface in a consumer repo.
+- Defining one universal numeric threshold for interface extraction.
+- Replacing agentic communication for novel, ambiguous, or exceptional work.