# Architecture Notes

The intended architecture is layered:

```text
markitect-tool     -> syntax layer
kontextual-engine  -> system/runtime layer
infospace-bench    -> application layer
```

The first implementation should establish repo shape before service shape:

- `infospaces/` for concrete infospace projects
- `schemas/` or dependency references for artifact schemas
- `workflows/` for application-level workflow definitions
- `reports/` for evaluation and inspection outputs
- `docs/` for migration and design records

Use direct dependencies on lower-layer projects only where they clarify the
boundary. Avoid copying infrastructure wholesale from `markitect-main`.