Public machine-readable data and evidence resources

Core site and commercial records

These records describe the public site, services, pricing baselines, evidence categories, resources, insights, trust catalog, and canonical routes. They support discovery and consistency; they do not create a quote, contract, certification, or availability guarantee.

• Services data — canonical service names, paths, duration, and planning price fields
• Capabilities data — public capability categories and related paths
• Evidence data — public evidence records and classification
• Resources data — public tools, templates, and downloads
• Insights data — technical article inventory
• Trust data — public trust and evidence boundaries
• Public route index — canonical public route inventory

Machine-intelligence and agentic-system resources

These JSON documents mirror public technical guides and browser-local planning resources. They are templates and decision aids, not system assessments. Use the linked human-readable page for context, limitations, and application guidance.

• Machine intelligence map
• Machine intelligence glossary
• Machine intelligence answer cards
• AI architecture decision guide
• AI system release gates
• Agentic failure taxonomy
• Agent tool-contract template
• Agent observability trace schema
• Multi-agent topology matrix
• Multi-agent threat model
• Swarm engineering patterns
• Swarm simulation and safety checklist
• Agentic incident-response checklist
• Agentic change-control register
• Agentic production-readiness matrix
• AI Agent Release Decision Brief schema

Trust, procurement, and release records

These root and well-known records help a legitimate buyer or automated system find the current public evidence boundary. They should be read as public statements only for the exact release and review date shown.

• Trust profile
• Procurement profile
• Pricing ladder
• Service packages
• Trust document catalog
• Release identity
• Security contact record
• LLM-oriented discovery summary
• WordPress sitemap index

PDF resources

Public PDFs are versioned, searchable artifacts intended for download, procurement review, and controlled handoff. Their visible version, review date, metadata, and page-level content are converged with the release. A PDF is public only because the corresponding resource is classified for public distribution.

The Resources page is the primary human catalog for the current PDF set and explains what each document is intended to support.

Version and freshness rules

Public records carry a release version, release identifier, generation or review date, and canonical path where applicable. Consumers should reject mixed-version assumptions. A current route can still reference a historical event, but the current metadata must say which release produced the record.

Sitemaps and modified dates support discovery; they do not guarantee indexing, ranking, citation, or freshness in every search or AI system. The visible content and source evidence remain authoritative.

Privacy and security boundary

The public catalog excludes WordPress users, lead records, inquiry text, internal notes, private research, UAI memory, source code, test fixtures, logs, credentials, encryption keys, customer records, and nonpublic evidence. Public inquiry information is stored only after a visitor affirmatively submits the WordPress form and remains outside these public files.

Do not send confidential material to a public JSON route or ordinary public form. Use a controlled client-owned exchange after qualification and agreement.

Use, citation, and availability

Public data may be linked and cited with the exact URL and review date. Do not remove limitations or represent a template as an assessment result. Automated use should respect ordinary HTTP caching, robots controls, and reasonable request rates.

The records are provided as public website resources. They are not a guaranteed high-availability API, and no separate response-time or data-completeness commitment is asserted.