Corpus maps Compound Engineering to docs/solutions markdown files with YAML frontmatter and future planning-agent search.
Tool profile · provisional profile
Compound Engineering
Strong human-readable solved-problem pattern. The best part is not memory storage, but explicit promotion from fix to reusable solution note.
Provisional fit
72/100
Best for: Engineering teams that want repo-local solutions to be searchable by future planning agents.
Avoid if: you need a fully governed, citation-complete knowledge architecture without adding policy, evidence capture, and review workflow around the tool.
Caution: Repo-local notes do not automatically solve multi-repo, cross-team, freshness, or context-budget problems.
Model signature: Storage primary · repo scope · Repo workflow
Layer coverage
Where this tool fits.
This is not a completed review. It is a provisional profile from public positioning plus known failure-mode mapping. Hands-on benchmarks, source snapshots, and citation-bound claims are still required before stronger conclusions.
Production
Curation
Storage
Activation
Governance
Review rule: a tool does not get credit for a layer unless it exposes inspectable behavior, not just a marketing claim.
Evidence notes
What the provisional profile has applied so far.
The pattern supports the latest research direction: promotion beats upfront classification.
Needs review for baseline context overhead, stale solution detection, and whether solution notes affect downstream task success.
Review packet
What a complete review must contain.
This page exposes the intended review structure. The current artifact is a profile, not a completed evidence-backed review.
Canonical source
Strengths
Engineering teams that want repo-local solutions to be searchable by future planning agents.
Limitations
Repo-local notes do not automatically solve multi-repo, cross-team, freshness, or context-budget problems.
Dimension assessment
Scope, volatility, authority, lifecycle, resource economics, interoperability, and evidence quality must each get a rationale and citations before final scoring.
Open questions
- What can be verified from docs, code, issues, benchmarks, and changelogs?
- Where does the tool fail under stale, contradictory, private, or high-cost knowledge?
- Which claims are vendor claims versus independently observed behavior?
Benchmark critique
No benchmark number is accepted as architectural evidence unless it says which layer it tests and what it misses: lifecycle, scope boundaries, authority, context cost, and governance.
Related systems
Related tools should be connected by evidence-backed edges: competes with, integrates with, implements concept, evaluated by, or has governance gap.
Update history
Provisional profile created. Stale-review detection, source snapshots, and changelog watching are required before this becomes a durable review.