Why
The Weaver Stack story currently lives mostly in weaver-spec. To make 8 repos read as one coherent project (and cross-pollinate stars), every repo needs the same "Part of the Weaver Stack" block, the same diagram, and a shared discovery topic. This is the ChainWeaver side of weaver-spec#6.
Proposal
- Add a standardized "Part of the Weaver Stack" README section with the shared stack diagram (request path: contextweaver → ChainWeaver → agent-kernel → agentfence; adjacent: vibeguard, lessonweaver, skdr-eval) and one-line "use standalone or together" note.
- Reuse an identical block/wording across all stack repos (coordinate with weaver-spec#6).
- Add the
weaver-stack GitHub topic to this repo.
Acceptance criteria
Coordinates with: weaver-spec#6, weaver-spec#5.
Why
The Weaver Stack story currently lives mostly in
weaver-spec. To make 8 repos read as one coherent project (and cross-pollinate stars), every repo needs the same "Part of the Weaver Stack" block, the same diagram, and a shared discovery topic. This is the ChainWeaver side of weaver-spec#6.Proposal
weaver-stackGitHub topic to this repo.Acceptance criteria
weaver-stacktopic added.Coordinates with: weaver-spec#6, weaver-spec#5.