Concepts/Concept
ADPS Engineering Concept Registry
Anchor, Ledger, Collection
Preserve the goal, append task facts, and project only the material needed now.
Application context
A payroll setup task moves through policy confirmation, group creation, employee association, approval, and submission. Late in the run, the newest conversation may focus on one employee. That detail must not replace the original delivery goal or erase earlier milestones.
Definition
- Anchor preserves the original goal, non-goals, acceptance conditions, and stable constraints;
- Ledger appends milestones, decisions, blockers, evidence references, and supersession events;
- Collection projects the Anchor and relevant Ledger entries into the current read view.
Engineering mechanism
The Anchor changes only through an explicit revision event. Ledger entries are append-only and carry source, author, time, scope, and links to artifacts. A Collection query selects entries for the current step and records which filters and versions were used. Full source material remains outside the prompt and is loaded through references when needed.
Boundary
These structures manage task narrative, not authoritative business state. Current balances, approval status, identifiers, and tool receipts remain in the mechanical state plane. Cross-task experience belongs in a separate memory lifecycle.
Proposal and provenance
- Concept group
- Context and memory
- Initial source within ADPS
- Initial practice: Bo Liang
- First recorded in
- Dongfang Yiteng execution-agent case ()
- ADPS editorial work
- ADPS separated the original goal, append-only facts, and current read view by lifetime.
- Current standing
- Case-derived name
Initial source: Dongfang Yiteng Execution Agent case report; contributed by Bo Liang.
Chronicle
- Recorded source
- Dongfang Yiteng execution-agent case ()
- Source date
- First published on ADPS