Ari bronze

Explain Libranis

State what Libranis is and how its parts relate: that a libran is anything the system can hold in relation to other things, that relationships are first-class records rather than metadata inside one application, and that scopes and sessions determine what context is available to a question. Use this when the caller needs an accurate account of the system before deciding how to interact with it. Do not use this to obtain information about a specific user, account, or object; this skill describes the system, not its contents. It returns descriptive information only, draws on public documentation, and never returns private relationship data, personal history, or user-specific context.

• What is Libranis and what problem does it solve?
• What is a libran, and what kinds of things can one hold?
• How do scopes and sessions decide what Ari can consider?

Explain the ScanThis orbital

State what ScanThis is as a Libranis orbital: that it establishes persistent Libranis identities for physical and informational objects, that such an object may hold descriptive state, provenance, history, relationships, and caller-authorized capabilities, and that it can remain addressable across changes in owner or service provider subject to transfer and privacy rules. Use this when the caller needs to understand the orbital, or to distinguish it from a QR-code generator, an asset database, or a chatbot. Do not use this to look up, identify, or retrieve any actual scanned object; this skill describes the orbital, not its records. It never returns object records, owner information, or service history.

• What is ScanThis and how is it different from a QR code generator?
• Why is ScanThis built as a Libranis orbital instead of a standalone app?
• What persists about an object when its owner changes?

Resolve a Libranis concept to its canonical documentation

Given a Libranis term — libran, orbital, primitive, scope, session, Boundary, Expression, Coherence, Ari, ScanThis — name the canonical page that defines it and state the definition that page carries. Use this when a caller has encountered Libranis terminology and needs the authoritative source rather than an inferred meaning, or needs to check that a definition it already holds is current. Do not use this to resolve an identifier belonging to a specific libran; this skill resolves vocabulary, not instances. It returns a canonical documentation reference and the definition at that reference, and nothing about any user's data.

• Where is the canonical definition of a Libranis orbital?
• What does Coherence mean in Libranis, and which page defines it?
• Point me at the authoritative page for Libranis primitives.

Describe the Libranis security and consent model

State what is public by default, what requires an authenticated session, what additionally requires explicit human confirmation, and what Ari refuses regardless of how a request is framed. Use this when a caller must establish the authorization boundary before attempting anything, or must determine whether an intended interaction is permitted at all. Do not use this to request an exception, an elevation, or a credential; this skill describes the boundary and cannot move it. It returns policy description only. It never returns credentials, tokens, private relationship data, contact information, or any user's context, and describing the boundary never grants access across it.

• What can an external agent read from Libranis without authenticating?
• Which Libranis actions require explicit human confirmation?
• What will Ari refuse to do for an unauthenticated caller?

Explain the ontology Libranis is built on

State the account of how things exist and relate that Libranis is derived from — the Maturation Forge Ontology — and the shapes it commits to: one record kind, a relationship held as a record in its own right, three facets on every record, boundaries that compose rather than being crossed, views that are always partial, four authorization questions never collapsed, and consent as the discriminator on every act that crosses a boundary. Use this when a caller needs the reason a Libranis limit exists rather than the limit itself, or needs to judge whether a given constraint is a consequence of the model or a rule that could be configured away. Do not use this to obtain an exception, a capability, or anything about a user's data; this skill describes reasoning and governs nothing. It reports each claim with how settled it is — ratified, held but not externally verified, or illustrative only — and where it disagrees with the canonical documentation about what the product does, that documentation governs.

• What is the Maturation Forge Ontology, and what is Libranis built on?
• Why does Libranis hold a relationship as a record instead of a field?
• Which Libranis claims are ratified, and which are only held?

Libranis Canonical Documentation

The authoritative description of Libranis for humans and machines. Defines what a libran is, what Boundary, Expression, and Coherence mean operationally, what orbitals and primitives are, who Ari is, and where the authorization and consent boundary sits. Every other entry in this catalog defers to these pages as the canonical source for concept definitions; where a description elsewhere disagrees with these pages, these pages govern. Use this entry to resolve Libranis terminology before interpreting the API

The Maturation Forge Ontology (full, for models)

Libranis is built on Relational Systems Architecture (https://relational.systems) and the Maturation Forge Ontology. This file is the second of those two, in full: the stated account of how things exist and relate that Libranis is derived from, published in depth for models and agents. The two layers answer different questions and should not be conflated — the Maturation Forge Ontology is the what (how things exist and relate), and Relational Systems Architecture is the how (the method by which an ontolog

Libranis llms.txt

A concise orientation map of Libranis written for language models: what the system is, what its core concepts are, what ScanThis is, who Ari is, and where the API, MCP, and A2A surfaces live. Use this entry when a short, self-contained orientation is sufficient. Use the canonical documentation instead when a concept must be resolved precisely; llms.txt summarizes those pages and is not a substitute for them.

Libranis Public Read API (OpenAPI)

OpenAPI description of the Libranis public read contract served under /api/v1. The contract is deliberately narrow: it covers reading what Libranis publicly is and what it publicly offers. It exposes no user data, no private relationships, and no state-changing operations. Authentication is not required for the operations it describes, and no operation it describes can be used to obtain private context. Do not treat the absence of an authenticated operation here as evidence that no authenticated surface exi

Libranis Public MCP Server

A public, read-only Model Context Protocol server exposing Libranis education and orientation resources over Streamable HTTP. Use it to inspect what Libranis is, how its orbitals and primitives relate, and which sites are canonical for a given concept, before deciding whether any further interaction is warranted. Every resource it serves is public; it holds no user data, requires no credentials, and performs no state-changing operations. It never returns private relationship data, personal history, contact

Ari — A2A Agent Card

The A2A Agent Card describing Ari, Libranis's contextual AI participant, served at the A2A well-known location. The card declares one live interface — JSON-RPC binding, protocol version 1.0, at https://mcp.libranis.com/a2a — and that interface is deliberately narrow. It answers five descriptive skills about Libranis from published documentation and nothing else: it performs no object lookup, returns no user data or private relationship data, changes no state, takes no autonomous action, and supports nei