State, not scraps.
Facts, decisions, objectives, constraints, hypotheses, questions, evidence, and superseded beliefs stay distinct.
Perch maintains living project context for agents: what matters, what changed, what was decided, what remains uncertain, and what you may be forgetting.
Facts, decisions, objectives, constraints, hypotheses, questions, evidence, and superseded beliefs stay distinct.
Agents receive a compact packet for the job at hand instead of an indiscriminate pile of nearest-neighbor chunks.
Every useful belief should retain where it came from, who captured it, and what it replaced.
Build the tools an AI agent wants in order to work effectively over long periods of time.
A future agent session should be able to resume managing Perch without a human reconstructing the project state.
Perch should expose useful capabilities through Astra rather than becoming a disconnected agent stack.
Use Perch as the working product name. It is bird-branded and avoids confusion with Meta Threads.
Start from capabilities the agent actually wishes existed, then productize capabilities that prove generally useful.
Provision and attest the dedicated Perch data plane, then run the fresh-session self-resumption test.