feat(ontology): add core service catalog
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
# Ontology Documents
|
||||
|
||||
Primary documents:
|
||||
|
||||
- `CANONICAL_ENTITY_CATALOG.md`
|
||||
- `RELATION_CATALOG.md`
|
||||
- `EVIDENCE_LEDGER.md`
|
||||
- `GUARDRAILS.md`
|
||||
- `TERMS_GLOSSARY.md`
|
||||
- `OPEN_QUESTIONS.md`
|
||||
- `IMPLEMENTATION_READINESS.md`
|
||||
|
||||
Current accepted baseline:
|
||||
|
||||
- Canonical Entity Catalog v0.4-pre is the active pre-release baseline.
|
||||
- HUB has an open contour and a managed client/company context.
|
||||
- `hub.public_pool_client` is a source-backed special Client used by the public pool context.
|
||||
- `hub.open_contour` must not be treated as an ordinary `hub.client_context`.
|
||||
- `ops.card` is the canonical OPS work object.
|
||||
- OPS Product, OPS Gateway, and ENGINE-side OpsLayer are different entities.
|
||||
- ENGINE L1/L2 workflow split is source-evidenced enough for first resolver implementation.
|
||||
- Engine-side OPS / Agent Monitor / tender-agent config is non-canonical tech debt.
|
||||
- Future Interface Layer is a planned separate layer/service, not more custom UI inside ENGINE core.
|
||||
|
||||
Current working evidence artifacts:
|
||||
|
||||
- `EVIDENCE_HARDENING_PLAN_V0_3_1.md`
|
||||
- `EVIDENCE_LEDGER_HUB_P0.md`
|
||||
- `EVIDENCE_LEDGER_OPS_P0.md`
|
||||
- `EVIDENCE_LEDGER_OPS_GATEWAY_P1.md`
|
||||
- `EVIDENCE_LEDGER_ENGINE_DIRTY_BOUNDARY_P1.md`
|
||||
- `EVIDENCE_LEDGER_ENGINE_WORKFLOW_P1.md`
|
||||
- `ONTOLOGY_SERVICE_PLACEMENT_AND_USE_CASES.md`
|
||||
Reference in New Issue
Block a user