# Implementation Readiness v0.4-pre

Status: ready to start first implementation phase
Date: 2026-06-18

This is the stop point for the current ontology design pass. The next phase is implementation planning/code, not more broad ontology discussion.

## Ready Baseline

The following documents form the implementation baseline:

- `CANONICAL_ENTITY_CATALOG.md`
- `RELATION_CATALOG.md`
- `GUARDRAILS.md`
- `TERMS_GLOSSARY.md`
- `EVIDENCE_LEDGER.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`
- `OPEN_QUESTIONS.md`

## Target Home

Final platform home:

```text
/Users/dcconstructions/Downloads/mnt/NODEDC/platform/services/ontology-core
```

Current working home:

```text
/Users/dcconstructions/Downloads/mnt/NODEDC_ONTOLOGY
```

Do not move source repositories during this phase. The next implementation step can create a clean service skeleton under `platform/services/ontology-core` and copy accepted docs there.

## First Implementation Slice

1. Create `platform/services/ontology-core` as docs-first platform service/module.
2. Add machine-readable catalog files:
   - `catalog/entities.json`
   - `catalog/relations.json`
   - `catalog/aliases.json`
   - `catalog/guardrails.json`
   - `catalog/evidence.json`
3. Add schema validation for entity/relation IDs and evidence statuses.
4. Add resolver MVP for two high-value flows:
   - OPS -> ENGINE: resolve project/card/user request into Engine workflow/L1/L2 context.
   - ENGINE -> OPS: resolve workflow/node/domain context into target OPS project/card path.
5. Add read-only lookup API or CLI only after schema and resolver rules are stable.
6. Wire OPS Gateway grant/tool preflight later; ontology advises context, Gateway enforces permission.

## Non-Goals For First Slice

- No database migration yet unless schema pressure requires it.
- No runtime refactor.
- No Engine-side OpsLayer cleanup.
- No tender/Agent Monitor rewrite.
- No full UI constructor yet.
- No broad domain ontology buildout.
- No secret/env/runtime/data/storage ingestion.

## First Useful Product Outcomes

- User in OPS can ask assistant to inspect, switch, or reason about an Engine workflow by human-readable project/workflow/card context.
- User in Engine can ask assistant to create/update the right OPS cards without manually switching OPS project context.
- Agents stop confusing:
  - OPS Product;
  - OPS Gateway;
  - ENGINE-side OpsLayer.
- Future interface layer has a stable conceptual runway and does not repeat the current ENGINE hardcoded UI pattern.

## Handoff Prompt For Implementation

```text
Implement Ontology Core first slice as docs-first platform service at
/Users/dcconstructions/Downloads/mnt/NODEDC/platform/services/ontology-core.

Use /Users/dcconstructions/Downloads/mnt/NODEDC_ONTOLOGY/ontology as accepted baseline.
Do not edit HUB/OPS/Gateway/ENGINE source code in this task.
Create catalog JSON files and validation around canonical entity/relation/alias/guardrail data.
Focus first resolver MVP on OPS -> ENGINE and ENGINE -> OPS context routing.
Keep Gateway permissions as enforcement authority; ontology only resolves/advises context.
Do not read env/secrets/runtime/data/storage/logs/dumps.
```

## Stop Point

The ontology design pass should pause here. Additional browser ChatGPT creativity is useful only as RFC review against these files, not as a replacement for the accepted baseline.

