One ontology · two interfaces

The Business Ontology for the Agent Era

Understand how your business fits together — and what a change will affect.

Prime Arch gives people and AI agents a shared language for connecting customer needs, offerings, services, processes, information and technology. Use its definitions, relationships and views to structure your knowledge, analyse dependencies and identify gaps.

Want your agent to use Prime Arch?

Give it this instruction together with your question. Your agent can use the agent entry directly; you do not need to work through it yourself.

How does an agent use Prime Arch? Reading instructions and access help →

If your agent encounters a reading error, it can open the same page in its browser or fetch the linked JSON file.

Read the full agent instruction here
Use Prime Arch to help the person with their stated business question.
1. Open https://www.primearch.se/agent/read/ and read the instructions and catalog.
2. Select a view by its question, dimension and level. Follow its complete HTML reference; use the linked JSON if your tool supports it.
3. Read the actual body. Check the view code, globalId, primary question, metaobjects, relations, conditions, exclusions and provenance. A title, snippet or HTTP 200 alone is insufficient.
4. If web search or web fetch cannot read the page, open the same URL with an available browser tool and read its page content. Alternatively use an approved HTTP tool to read the linked JSON. Use only published catalog links; do not guess endpoints.
5. Distinguish ontology rules from the person's business evidence and your own interpretation. Preserve identifiers, levels, relation direction, status and limits. Do not invent missing definitions or treat an unpublished relation as permitted.
6. Answer the person's question and cite the exact URLs actually read. State any uncertainty or missing evidence.
7. If reading still fails, report the exact URL, tool, error/status and attempted fallback. For 429 respect Retry-After; for access challenges or authentication stop and report them. Do not bypass controls or repeatedly retry. Say access failed, not that the knowledge does not exist. Never claim to have read unread content.