---
id: ITC-WP-0017
type: workplan
title: "AgenticDrivesFunctional PracticePattern"
domain: infotech
topic_slug: canon
repo: info-tech-canon
status: finished
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
state_hub_workstream_id: "bd5c26dc-2751-5502-8151-c1eb09ce3378"
---

# 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: done
priority: high
state_hub_task_id: "dc7f97f0-251c-5344-a951-12f66c58b71e"
```

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: done
priority: medium
state_hub_task_id: "ce2cb013-7f15-5818-b80b-0cb1f52ddaab"
```

Register the artifact and its relationship to `InterfaceDeprecationStrangler`,
add it to the pattern catalog, refresh generated retrieval assets, and validate
the canon.

## Acceptance

- [x] `AgenticDrivesFunctional` conforms to PracticePattern v0.1.
- [x] The pattern distinguishes direct interfaces from cross-repo task routing.
- [x] Repetition is treated as evidence for interface review, not an automatic
      mandate to build an interface.
- [x] Interfaces preserve authorization, credential custody, and third-party
      approval boundaries.
- [x] The pattern is registered, retrieval-visible, validated, committed, and
      synchronized.

## Result

Completed 2026-08-22. The canon now carries the active
`AgenticDrivesFunctional` PracticePattern, backed by Repo Manager's scoped
identifier registrar as its first complete known use. The artifact is indexed,
agent-retrievable, related to `InterfaceDeprecationStrangler`, and validated by
the canon service and full test suite.

## 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.