Platform Architecture
Public Agent Access
This route is essential because agent access is part of the product reality, not an optional add-on.
Public agent access explains how non-human consumers can reach specific CITAQ surfaces and what the boundaries are.
This route sits inside the platform architecture family and exists to explain one structural part of the verification system in focused, indexable detail.
Key Points
What matters on this route
Public agent access explains how non-human consumers can reach specific CITAQ surfaces and what the boundaries are.
This route is essential because agent access is part of the product reality, not an optional add-on.
Platform architecture pages should explain how a specific layer behaves, not repeat high-level homepage language.
Each platform route should bridge into docs, trust, implementation, and adjacent platform concepts.
Route Detail
How this page fits into the CITAQ system
Public agent access explains how non-human consumers can reach specific CITAQ surfaces and what the boundaries are.
This route is essential because agent access is part of the product reality, not an optional add-on.
CITAQ is large enough that major platform concepts need isolated pages with their own metadata, schema, and internal-link role.
Connected Routes
Keep moving through the route graph
See how this concept fits into the broader infrastructure story.
Move into the docs system for method and reference detail.
See how this platform layer eventually shows up in public trust routes.
Open the integrations system for the upstream inputs that support this layer.
Next Step
Use the workflow route to see this layer in sequence.
The architecture page shows how the different platform layers work together across ingestion, verification, and trust output.