01
ADPS Practice Sources
Workshops
ADPS workshops preserve first-hand production questions, practices, and disagreements, then record how they inform module overviews and pattern revisions.
02
Module overview
Synthesizes formal patterns, workshop findings, and public engineering practice at subsystem level.03
Pattern specification
Defines a recurring problem, mechanism, boundary, and method of verification.26 August 2026
Reasoning
Decision artifacts, complexity and risk routing, parallel exploration, hypothesis testing, live interaction, and validation.
25 August 2026
Collaboration
Topology lowering, delegated authority, handoff contracts, cross-session conflicts, hook composition, and three collaboration planes.
2026-08-18
Governance
Two-layer authorization, durable intent, capability-specific authority, agent control plane, cross-cutting observability, and lifecycle.
2026-08-13
Perception
Signal admission, event ingress, the boundary between multi-source and multi-modal input, and context in AI-driven software engineering.
2026-08-12
Reflection
Online and offline reflection, feedback latency, evaluation evidence, skill evolution, attribution, and self-repair boundaries.
2026-08-06
Action
Plan and ReAct, structured plans, tool admission, GUI action, sandboxes, and event-driven execution.
2026-08-05
Memory
Adoption criteria, engineering boundaries, lifecycle, storage forms, and governance of agent memory.
A term introduced in a workshop does not automatically become a pattern. ADPS checks whether it identifies an independent problem, has a describable mechanism, and is supported by enough practice. Questions that cross several modules move to Topics.