Skip to content

Latest commit

 

History

History
48 lines (36 loc) · 2.81 KB

File metadata and controls

48 lines (36 loc) · 2.81 KB

Agent Instructions

Ecosystem cross-wiring

This repo is the episodic write target of the Amplifier behavioral-plasticity constellation. It is one peer in a wired-together set of five repos, governed by a separate conductor bundle (amplifier-bundle-behavioral-plasticity); you do not need to read the other repos to work here.

  • Exposes (studs): tool-memory, hooks-memory-capture, importance weighting, and the NativeMemoryStore seam onto amplifier-data.
  • The constellation: memory (this repo) · context-intelligence-survey (measurement chassis) · context-intelligence (session signal scoring) · amplifier-data (append-only substrate) · behavioral-plasticity (the conductor that composes all four).
  • Dependency direction is one-way: behavioral-plasticity → {survey, CI, memory, amplifier-data}, and memory → amplifier-data (the only intra-four edge). survey, CI, and memory are peers and MUST NOT import each other. None of the four may import the behavioral-plasticity bundle — it is the only component allowed to know all four.
  • Known primitive gap: the capture hook (hooks-memory-capture) does not yet read tool_success; the behavioral-plasticity loop (Step 2) adds it here.

Project coordination

This project uses a coordination file system in project-context/. These files give you persistent memory across sessions. Read them before starting any work.

Starting a Session

Read these files in order:

  1. project-context/PROJECT_CONTEXT.md — current project state, phase, team
  2. project-context/GLOSSARY.md — terminology (use these terms exactly)
  3. project-context/HANDOFF.md — what happened last session, what to do next

Also read when relevant:

  • project-context/STRUCTURE.md — before creating or moving files
  • project-context/WAYSOFWORKING.md — for workflows, failure patterns, verification steps
  • project-context/PROVENANCE.md — to understand why a decision was made
  • project-context/EXPERIMENT_JOURNAL.md — to see what was tried and learned

Ending a Session

Update project-context/HANDOFF.md with:

  • What you accomplished (specific files, decisions, results)
  • What's blocked or unresolved
  • What the next session should start with
  • Non-obvious context the next agent needs

Continuous Improvement

When you... Update
Use a term not in the glossary project-context/GLOSSARY.md
Make a design or architecture decision project-context/PROVENANCE.md
Hit an error and find the fix project-context/WAYSOFWORKING.md
Create or move files project-context/STRUCTURE.md
Run an experiment or benchmark project-context/EXPERIMENT_JOURNAL.md
Change the project phase or milestone project-context/PROJECT_CONTEXT.md
Finish any session project-context/HANDOFF.md