Concepts/Concept
ADPS Engineering Concept Registry
Memory Envelope
Assemble a versioned context package for one model call.
Application context
A reasoning step that decides how to associate employees needs the task goal, current plan node, relevant policy, created payroll-group identifier, and unresolved exceptions. It does not need every tool response and discussion from earlier stages. Passing the full history raises cost and lets recent detail displace the original goal.
Definition
A Memory Envelope is the versioned context package assembled for one model call. It combines the stable Anchor, current progress, selected evidence, exact state references, recalled experience, and the output contract expected from this step.
Engineering mechanism
goal: ref://anchor/17
step: associate-employees
progress: ref://workspace/node-4
facts: [ref://state/pay-group-id]
evidence: [ref://policy/sg-payroll@v8]
experience: [ref://lesson/bulk-association@v3]
output_schema: AssociationDecisionThe runtime records the envelope hash and source versions with the model call. A later replay can therefore reconstruct what the model was allowed to see without storing a hidden, mutable prompt.
Boundary
The envelope is a read package, not the system of record. It points to authoritative values and artifacts. Selection policy may use relevance and priority, but permissions, validity, and task scope filter candidates before ranking.
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
- The implementation structure is ReasonContext; ADPS supplied the name Memory Envelope.
- 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