atlas
Agent-design pattern guidance via 5 hosted read-only tools; Streamable HTTP, no auth, one Release.
- 1.0.6
- Version
- remote
- Transport
- 5
- Tools
Security review
Review passedReviewed 1d ago.
- tools: 5 tools scanned
- metadata: scanned
No findings.
Tools (5)
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 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_cards
Read 1-8 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.
atlas_read
Read a complete Node (bare id: identity, hierarchy, Hook, and every Section; relationship occurrences are omitted), one Section ('node-id#section-slug'), one Decision record ('decision:<decision-id>'), or one exact glossary definition ('term:<key>').
atlas_links
Page 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'.
atlas_navigate
Read 'tree', the canonical ordered traversal of every published node, or 'tour', the publisher-curated first learning path.