feat(ITC-WP-0017): establish AgenticDrivesFunctional pattern

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a025c2-407a-7a32-b40a-f37a52f03f62

infospace/agent/briefs/practice-pattern-agentic-drives-functional.md

@@ -0,0 +1,37 @@
+---
+id: agent-brief/practice-pattern-agentic-drives-functional
+artifact_id: practice-pattern/agentic-drives-functional
+source_path: patterns/AgenticDrivesFunctional.md
+source_kind: practice-pattern
+generated: true
+---
+
+<!-- GENERATED by info_tech_canon; do not edit by hand. -->
+
+# Agent Brief: AgenticDrivesFunctional
+
+- Artifact ID: `practice-pattern/agentic-drives-functional`
+- Kind: `practice-pattern`
+- Canonical path: `patterns/AgenticDrivesFunctional.md`
+- Full source: `patterns/AgenticDrivesFunctional.md`
+- Summary: Reusable canon PracticePattern: AgenticDrivesFunctional.
+
+## Retrieval Hints
+
+Imports and anchors:
+- `model/capability`
+- `model/governance`
+- `model/observability`
+- `model/task`
+- `scheme/practice-pattern`
+
+## Owned Concepts
+
+- `AgenticDrivesFunctional`
+- `AgenticFallback`
+- `DemandSignature`
+- `FunctionalInterfaceCandidate`
+
+## Related Distinctions
+
+- **Agentic fallback vs direct functional interface**: Use cross-repository agentic work to interpret novel demand; use an owned API, CLI, or MCP surface when the outcome is stable and recurring.