- Home
- Reference API & ontology — Ethotechnics
Reference API & ontology
Canonical objects and a read-only API plan for consuming Ethotechnics standards in tools and audits.
Machine-readable
Plan for programmatic access.
The goal is a stable object model that tools can cite, cache, and validate against.
Jump to
Key sections
Canonical objects
The object model this API will publish.
Use these names in integrations and audit tooling.
- Standard: Top-level standard metadata, version, and published clauses.
- Clause: Atomic right requirement with a stable clause ID (e.g., §3.2).
- Mechanism: Reusable enforcement spec with tags, artifacts, and implementation notes.
- Validator: Diagnostic definition with inputs, thresholds, and output schema.
- Finding: Canonical diagnostic artifact linking gaps to clauses and fixes.
- Diagnostic result: Generated report card, risk statement, and remediation recommendations.
- Evidence pack: Minimum evidence bundles required to verify clause compliance.
- Crosswalk control: Control-level mapping across EU AI Act, NIST AI RMF, and ISO/IEC 42001.
- Post-market stage: Operational incident reporting stages with expected outcomes and references.
- Anti-pattern: Negative examples that look compliant but fail the clause intent.
- Diagram: Diagram objects aligned to the micro-diagram language spec.
- Agent safety object model: Machine-readable profile for autonomy level, action classes, override authority, and receipts.
Interoperability specs
Draft contracts for decision and repair workflows.
Use these specs to wire decisions, appeals, and clock events into tooling.
- Control plane OpenAPI: /standards/ethotechnics-control-plane.openapi.yaml — Decision retrieval and appeal intake endpoints aligned to the agent receipt schema.
- Events AsyncAPI: /standards/ethotechnics-events.asyncapi.yaml — Deadline and repair log events for clocked governance and remediation workflows.
FHIR resources
FHIR Resources (healthcare-specific interop)
- Target: healthcare payers, providers, regulators.
- If you care about healthcare, this is non-optional.
- Why: FHIR is the only sanctioned exchange substrate in U.S. health. TEFCA rides on top of it.
-
What to ship: custom FHIR profiles for:
- Decision
- Denial
- Appeal
- RepairStatus
- PendingClock
- FHIR makes refusal + repair first-class healthcare data.
-
Decision retrieval:
GET /api/decisions/{decision_id} - Appeal submission:
POST /api/appeals -
Events:
decision.deadline.reminder,appeal.deadline.breached,repair.log.updated
Agent object model
Agent Safety Object Model
Publish a machine-readable profile for agent governance in tooling.
- Spec page: /agents/spec
- JSON schema: /agents/spec.json
- Receipt and remedy schemas:
Read-only endpoints
Current machine-readable exports.
These endpoints are stable exports for tooling, audits, and archival use.
| Endpoint | Purpose |
|---|---|
| /api/agent-index.json | Quick-start index for agent discovery and tooling. |
| /api/site-index.json | Index of standards, validators, and research metadata. |
| /api/standards.json | Standard metadata with embedded clause objects. |
| /api/clauses.json | Clause-level obligations with evidence requirements and mappings. |
| /api/mechanisms.json | Mechanism catalog entries with filters and citations. |
| /api/validators.json | Validator definitions with inputs, thresholds, and clause mappings. |
| /api/anti-patterns.json | Negative patterns that surface legitimacy theater risks. |
| /api/evidence-packs.json | Evidence pack templates per clause. |
| /api/crosswalks.json | Control crosswalks with framework mappings and evidence artifacts. |
| /api/post-market-monitoring.json | Post-market monitoring and incident reporting workflow stages. |
| /api/findings.json | Canonical finding objects for remediation workflows. |
| /api/diagnostic-results.json | Portable diagnostic result artifacts. |
| /api/rag-corpus.jsonl?limit=200 | JSONL corpus for retrieval pipelines (add a limit query param for previews). |
| /api/glossary.json | Glossary terms with permalinks. |
| /api/research.json | Research publications and bridge artifacts. |
| /api/releases.json | Versioned release index for stable citations. |
| /api/v/2026.01/ | Versioned snapshot endpoints for reproducible analysis. |
Versioning
Versioned citations stay stable.
Each object should carry a version, updated timestamp, and canonical permalink.
- Semantic versioning for standards, mechanisms, and validators.
- Immutable permalinks for citations in contracts and audit logs.
- Changelogs that describe material changes to rights or thresholds.
- Snapshot endpoints under /api/v/ to pin analyses in time.
- Signed releases with verifiable citation hashes.
- Schema validation automation for new objects.
- Expanded clause mapping for emerging standards.
- OpenAPI draft for decision retrieval and appeal intake.
- AsyncAPI events for deadline clocks and repair log updates.