[sathish-mg]

Summary

The repository did not explain that every Areev Store product is built using Areev Core, leaving developers without a clear path from the product catalogue to building their own micro-vertical application. Lead with that relationship and move the runnable invoice example, its approved-correction outcome, and expected output ahead of the capability catalogue.

Align the FAQ, rationale, and LLM-facing overview; retain the distinction between the open-source engine/reference agents and store product packaging and availability. Replace stale repeated metric claims in the LLM overview with canonical measurement sources, and remove the community link that currently opens a banned subreddit.

Related issue

None.

Type of change

• Documentation only

Validation

• cargo test --workspace passed.
• cargo clippy --workspace --all-targets -- -D warnings passed.
• Invoice python/smoke.sh and python/improve.sh passed in an isolated copy with a fresh PyPI areev==1.13.0 install; both matched the documented completion messages.
• scripts/check_versions.py, scripts/repo_stats.py --check, local documentation link validation, and git diff --check passed.

Checklist

• Full workspace tests pass locally
• Documentation updated; no runtime behavior changes or new tests needed
• Commit signed off (DCO)
• Invariants and contributing guidelines followed