feat(ITC-WP-0017): establish AgenticDrivesFunctional pattern
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a025c2-407a-7a32-b40a-f37a52f03f62
This commit is contained in:
tegwick 2026-08-22 18:54:01 +02:00
parent 9e7e1d8c1e
commit 0ab196829e
21 changed files with 725 additions and 109 deletions

View file

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

View file

@ -5,8 +5,8 @@
This brief summarizes the current canon service surface for agents.
- Infospace slug: `canon`
- Artifact count: 70
- Retrieval index items: 70
- Artifact count: 71
- Retrieval index items: 71
- Primary confidence command: `make validate`
- Refresh generated indexes and views with: `make index`
- Refresh agent briefs and interface templates with: `make agent-briefs`
@ -29,6 +29,7 @@ This brief summarizes the current canon service surface for agents.
## Common 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.
- **Interface deprecation vs retirement vs removal**: Deprecation guides and observes callers, retirement ends legacy behavior while retaining a metered tombstone, and removal deletes that tombstone only after the evidence gate passes.
- **Actor vs Subject vs Principal**: Use actor for the acting entity in a context, subject for the entity a policy evaluates, and principal for the authenticated identity bound to access decisions.
- **Organization Role vs AccessRole vs CARING role**: Organization roles describe responsibility or position; access roles describe permissions; CARING roles classify access-governance needs and analysis.

View file

@ -1,5 +1,13 @@
{
"common_distinctions": [
{
"id": "agentic-fallback-direct-interface",
"source_artifacts": [
"practice-pattern/agentic-drives-functional"
],
"summary": "Use cross-repository agentic work to interpret novel demand; use an owned API, CLI, or MCP surface when the outcome is stable and recurring.",
"title": "Agentic fallback vs direct functional interface"
},
{
"id": "interface-deprecation-retirement-removal",
"source_artifacts": [
@ -51,7 +59,7 @@
}
],
"infospace": "canon",
"item_count": 70,
"item_count": 71,
"items": [
{
"canonical_path": "assimilation/it-capability-canon/ASSIMILATION.md",
@ -1531,6 +1539,54 @@
"title": "Intent Scope Purposes Pattern",
"warnings": []
},
{
"canonical_path": "patterns/AgenticDrivesFunctional.md",
"id": "practice-pattern/agentic-drives-functional",
"imports": [
"model/capability",
"model/governance",
"model/observability",
"model/task",
"scheme/practice-pattern"
],
"kind": "practice-pattern",
"owned_concepts": [
"AgenticDrivesFunctional",
"AgenticFallback",
"DemandSignature",
"FunctionalInterfaceCandidate"
],
"relationships": [
{
"target": "scheme/practice-pattern",
"type": "conforms_to"
},
{
"target": "model/capability",
"type": "uses"
},
{
"target": "model/governance",
"type": "uses"
},
{
"target": "model/observability",
"type": "uses"
},
{
"target": "model/task",
"type": "uses"
},
{
"target": "practice-pattern/interface-deprecation-strangler",
"type": "related_to"
}
],
"source_path": "patterns/AgenticDrivesFunctional.md",
"summary": "Reusable canon PracticePattern: AgenticDrivesFunctional.",
"title": "AgenticDrivesFunctional",
"warnings": []
},
{
"canonical_path": "patterns/InterfaceDeprecationStrangler.md",
"id": "practice-pattern/interface-deprecation-strangler",

View file

@ -4,10 +4,11 @@
Schema: `info-tech-canon.retrieval-index.v1`
Infospace: `canon`
Items: **70**
Items: **71**
## Common 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. Sources: `practice-pattern/agentic-drives-functional`
- **Interface deprecation vs retirement vs removal**: Deprecation guides and observes callers, retirement ends legacy behavior while retaining a metered tombstone, and removal deletes that tombstone only after the evidence gate passes. Sources: `practice-pattern/interface-deprecation-strangler`
- **Actor vs Subject vs Principal**: Use actor for the acting entity in a context, subject for the entity a policy evaluates, and principal for the authenticated identity bound to access decisions. Sources: `model/organization`, `model/access-control`, `standard/caring`
- **Organization Role vs AccessRole vs CARING role**: Organization roles describe responsibility or position; access roles describe permissions; CARING roles classify access-governance needs and analysis. Sources: `model/organization`, `model/access-control`, `standard/caring`
@ -456,6 +457,16 @@ Items: **70**
- Imports and anchors: `model/governance`, `model/task`
- Owned concepts: `Intent Scope Purposes Pattern`, `IntentScopePurposePattern`
### AgenticDrivesFunctional
- ID: `practice-pattern/agentic-drives-functional`
- Kind: `practice-pattern`
- Canonical path: `patterns/AgenticDrivesFunctional.md`
- Source path: `patterns/AgenticDrivesFunctional.md`
- Summary: Reusable canon PracticePattern: AgenticDrivesFunctional.
- Imports and anchors: `model/capability`, `model/governance`, `model/observability`, `model/task`, `scheme/practice-pattern`
- Owned concepts: `AgenticDrivesFunctional`, `AgenticFallback`, `DemandSignature`, `FunctionalInterfaceCandidate`
### InterfaceDeprecationStrangler
- ID: `practice-pattern/interface-deprecation-strangler`

View file

@ -1,6 +1,6 @@
schema: info-tech-canon.retrieval-index.v1
infospace: canon
item_count: 70
item_count: 71
items:
- id: assimilation/it-capability-canon
kind: assimilation
@ -973,6 +973,37 @@ items:
- type: uses
target: model/task
warnings: []
- id: practice-pattern/agentic-drives-functional
kind: practice-pattern
title: AgenticDrivesFunctional
canonical_path: patterns/AgenticDrivesFunctional.md
source_path: patterns/AgenticDrivesFunctional.md
summary: 'Reusable canon PracticePattern: AgenticDrivesFunctional.'
owned_concepts:
- AgenticDrivesFunctional
- AgenticFallback
- DemandSignature
- FunctionalInterfaceCandidate
imports:
- model/capability
- model/governance
- model/observability
- model/task
- scheme/practice-pattern
relationships:
- type: conforms_to
target: scheme/practice-pattern
- type: uses
target: model/capability
- type: uses
target: model/governance
- type: uses
target: model/observability
- type: uses
target: model/task
- type: related_to
target: practice-pattern/interface-deprecation-strangler
warnings: []
- id: practice-pattern/interface-deprecation-strangler
kind: practice-pattern
title: InterfaceDeprecationStrangler
@ -1623,6 +1654,12 @@ items:
target: model/task
warnings: []
common_distinctions:
- id: agentic-fallback-direct-interface
title: Agentic fallback vs direct functional interface
summary: Use cross-repository agentic work to interpret novel demand; use an owned
API, CLI, or MCP surface when the outcome is stable and recurring.
source_artifacts:
- practice-pattern/agentic-drives-functional
- id: interface-deprecation-retirement-removal
title: Interface deprecation vs retirement vs removal
summary: Deprecation guides and observes callers, retirement ends legacy behavior