info-tech-canon/workplans/ITC-WP-0017-agentic-drives-functional.md

id	type	title	domain	topic_slug	repo	status	priority	created	updated	owner	related	spec_refs
ITC-WP-0017	workplan	AgenticDrivesFunctional PracticePattern	infotech	canon	info-tech-canon	active	medium	2026-08-22	2026-08-22	codex	ITC-WP-0016	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

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

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.