Project maps
Show the few files, systems, owners, and decisions that actually define the work.
A smaller first web
Useful structure before grand orchestration.
Weaver starts with the ordinary things that make a project durable: an explicit map, current evidence, bounded capabilities, and a clear checkpoint for whoever enters next—human or agent.
Context checkpoints
Leave a concise, evidence-linked state from which another contributor can safely resume.
Capability boundaries
Describe what a tool or agent may do, what it can spend, and where it must escalate.