Agents API Duplicated Substrate Inventory
Issue: #1762
Parent: #1755
Data Machine now consumes automattic/agents-api at 109576b004ef61783456e27ad841e553aa59f25a, which includes Automattic/agents-api PRs #65-#73. This inventory records the Data Machine surfaces that duplicate the newly landed substrate primitives. It is intentionally an inventory only: no broad behavioral migrations happen in this dependency bump.
Inventory
| Agents API substrate | Duplicated Data Machine surface | Follow-up | Boundary decision |
|---|---|---|---|
| Guideline capability metadata from Automattic/agents-api#65 | MemoryFileRegistry editability/layer metadata, MemoryPolicyResolver, SelfMemoryWritePolicy, and guideline-backed memory store capability checks | #1763 | Adopt capability vocabulary where it gates memory/guideline access; keep Data Machine’s concrete file registry, memory commands, and store selection product-owned. |
| Consent operations and decisions from Automattic/agents-api#66 | Memory/transcript writes in AgentMemory, DailyMemory, ConversationManager, DataMachinePipelineTranscriptPersister, and memory tools/directives currently rely on Data Machine mode/config checks rather than a generic consent policy | #1760 | Wire consent checks at Data Machine adapter boundaries only. Do not add compatibility shims for old consent vocabulary because there is no persisted consent contract yet. |
| Workspace scope contracts from Automattic/agents-api#67 | DirectoryManager, DiskAgentMemoryStore, GuidelineAgentMemoryStore, AgentMemoryScope usage, and ConversationStoreFactory::get_transcript_store() encode user/agent/site identity directly | #1756 | Use AgentWorkspaceScope to stamp memory, transcripts, and audit records while keeping Data Machine paths, tables, and migration behavior in Data Machine. |
| Memory context registries from Automattic/agents-api#68 | MemoryFileRegistry, SectionRegistry, ComposableFileGenerator, ComposableFileInvalidation, and prompt directives implement Data Machine’s memory/context registry and composition model | #1761 | Adopt generic registry/projection vocabulary for context authority. Keep generated files, convention paths, invalidation hooks, and operator CLI as Data Machine product behavior. |
| Memory provenance metadata from Automattic/agents-api#69 | DiskAgentMemoryStore, GuidelineAgentMemoryStore, AgentMemoryStoreFactory, DailyMemoryStorage, and memory list/read/write results currently expose Data Machine hash/path metadata but not generic provenance/query/capability metadata | #1761 | Extend adapters to return provenance metadata where backed by real storage data. Do not invent compatibility rows for unsupported metadata. |
| Retrieved context authority cascade from Automattic/agents-api#70 | DirectivePolicyResolver, CoreMemoryFilesDirective, MemoryFilesReader, ClientContextDirective, CallerContextDirective, and PromptBuilder order and merge context without the upstream authority/conflict vocabulary | #1761 | Adopt authority/conflict contracts when composing retrieved context. Keep Data Machine directive registration and product modes outside Agents API. |
| Durable pending-action approval contracts from Automattic/agents-api#71 | PendingActionStore, PendingActionStoreAdapter, PendingActionResolverAdapter, PendingActionHelper, ResolvePendingActionAbility, and pending-action REST/handler plumbing | #1759 | Data Machine remains the concrete store/resolver/product route. Expand adapters to the durable audit contract; do not duplicate generic lifecycle/status vocabulary locally. |
| Generic tool and action policy contracts from Automattic/agents-api#72 | ToolPolicyFilter, ToolPolicyResolver, ActionPolicyResolver, DataMachineToolAccessPolicy, DataMachineAgentToolPolicyProvider, DataMachineMandatoryToolPolicy, ToolSourceRegistry, and ToolExecutionCore | #1758 | Move generic allow/deny/action-policy evaluation to Agents API contracts. Keep Data Machine source providers, adjacent-handler preservation, persisted agent config, and legacy tool registry adapters local. |
| Authorization grants, tokens, and capability ceilings from Automattic/agents-api#73 | AgentAccess, AgentTokens, AgentTokenAbilities, agent-call abilities, materializer owner grants, and runtime caller/agent permission checks | #1757 | Adapt Data Machine repositories to Agents API authorization contracts. Persisted Data Machine tables remain product-owned until an explicit storage migration exists. |
Non-Goals
- Do not move broad runtime, memory, approval, authorization, or tool-policy behavior in this PR.
- Do not add backward-compatibility aliases or shims for renamed substrate vocabulary unless a later adoption issue proves persisted data requires one.
- Do not move Data Machine flows, pipelines, jobs, handlers, queues, retention, content operations, admin UI, or CLI product surfaces into Agents API.