AI agent reference (canonical source in monorepo)

This site’s published docs live under axiom-genesis-guide/docs/. The authoritative agent briefing pack for the Axiom Genesis platform is maintained next to application code in the monorepo root:

docs/ai-agent-reference/ (relative to the Axiom-Genesis repository root)

Clone or open the main repo and read that folder directly in your editor, or browse it in source control. It is versioned with frontend and middleware so contracts stay aligned.

What is in that pack

Document	Purpose
README.md	Entry point, hard rules, code anchors
architecture-studio-and-renderer.md	Studio vs runtime renderer split
entity-crud-pattern.md	Generic /api/entity/:entity_code/* and recordService
data-model-conventions.md	Registry, profiles, tenant columns
config-table-catalog.md	Config tables ↔ entity codes
PRIORITY-roadmap-by-project.md	Cross-repo execution order
COMPLETION-assessment-*.md	Delivery status by area
conversational-ai-studio.md	Optional AI studio scope
tenant-resolution-contract.md	JWT vs x-tenant-id vs encrypted tenant header
readiness-and-startup.md	/healthz, /readyz, /livez, readiness gates, uncaught handlers
frontend-dataview-designer-split.md	Dataview root vs core/ import map (F3)

Why it is not fully inlined here

Duplicating dozens of markdown files would drift from the repo within days. This page is the stable pointer for humans and agents: start here in the guide, then open the monorepo path above for detail.

Quick rules (see monorepo README.md for full text)

• Prefer the generic entity API for CRUD; avoid one-off REST controllers for the same data.
• entity_code in URLs matches app_object_profiles.prf_code (not necessarily obj_code); middleware resolves registry via profile linkage when they differ.
• Frontend: use record.service for entity-backed config rows.