agentic-atlas

Field-tested patterns for designing agentic systems.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Atlas Orient: Discover canonical identity from an ordinary-language query — the entry point when no canonical id is held. Ranked: identity fields and sealed claims decide candidacy, Section text only
  • Atlas Cards: Read 1-4 canonical ids as one ordered Card per id: identity, Hook, and sealed claims with source addresses. Set provenance=true to expand every cited source's Release-bound audit facts in
  • Atlas Read: Read a complete Node (bare id: identity, hierarchy, Hook, and every Section — relationships are recovered through atlas_links), one Section ('node-id#section-slug'), one Decision record ('

What data it sees

Do you need an account

No: the server works without sign-in

Field-tested patterns for designing agentic systems. Eight read-only tools let an agent orient by ordinary design vocabulary, then read pattern Cards, one Section, or a whole Node from a single published Release, so consultation cost stays proportional to relevance.

Server tool list (5)

Raw names from tools/list. Only developers need these.

atlas_orientDiscover canonical identity from an ordinary-language query — the entry point when no canonical id is held. Ranked: identity fields and sealed claims decide candidacy, Section text only when no identity field matches; ordered by identity score, then Section score, then how many words matched, then manifest position. Node candidates carry id, status, Hook, and disclosure class; Decision and term candidates carry exactly a read address and Hook. A term's Hook is its full sealed definition. Results are paged. A miss is a successful empty payload.
atlas_cardsRead 1-4 canonical ids as one ordered Card per id: identity, Hook, and sealed claims with source addresses. Set provenance=true to expand every cited source's Release-bound audit facts in the same atomic response. Use atlas_read for Section wording or a complete Node.
atlas_readRead a complete Node (bare id: identity, hierarchy, Hook, and every Section — relationships are recovered through atlas_links), one Section ('node-id#section-slug'), one Decision record ('decision:<decision-id>'), or one exact glossary definition ('term:<key>'). A Card from atlas_cards is usually cheaper than a whole Node.
atlas_linksPage one subject's relationship occurrences, outbound then inbound, each with direction, reference class, source Section, and the far end's Hook, plus its identity unless the class is 'undisclosed'. Use atlas_read for the full Node.
atlas_navigateRead 'tree', the canonical ordered traversal of every published node, or 'tour', the publisher-curated first learning path. Use atlas_orient for relevance-ranked discovery.