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.
Page responsibilities
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.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.