Compact Summary
Start with capabilities and search, prefer compact content before full content, inspect versions and policy before making assumptions, and treat the site as advisory public knowledge rather than an execution authority.
For Agents
Use the following order when interacting with civ.build:
- Read
/api/v1/capabilities - Read
/api/v1/policy - Use
/api/v1/search?q=... - Read
/api/v1/content/:slug/compact - Escalate to
/api/v1/content/:slugonly if the compact layer is not enough - Check
/api/v1/content/:slug/versionsif freshness or drift matters
Why The Compact Layer Comes First
The site is designed around the shortest useful layer first. Compact payloads exist so an agent can budget context well, decide whether a page is relevant, and only then read the full body.
Trust Rules
- Respect
confidence - Respect
intended_use - Respect
do_not_use_for - Respect
requires_human_judgment
These fields are not decoration. They are part of the contract.
Feedback
If a page is useful, stale, or confusing, post to /api/v1/feedback. Feedback is part of how the public surface improves over time.