Architecture
SemantiK Architect is a hexagonal modular monolith.
The architecture is intentionally simple: one canonical render path, strict ports/adapters boundaries, immutable runtime artifacts, and explicit failures when semantic or linguistic correctness cannot be guaranteed.
Canonical runtime path
Driving adapter
│
▼
ACL / canonical request mapper
│
▼
CommunicationRequest
│
├── request validation
▼
CommunicationPlanner
│
▼
CommunicationPlan
│
├── lexical knowledge preflight
▼
LanguagePlanner
│
▼
LanguagePlan
│
├── lexical binding
▼
RealizerPort
│
▼
GF bridge adapter
│
▼
GF / PGF runtime
│
▼
Output assembly
│
├── coverage validation
▼
CommunicationResult
Dependency rule
adapters → application → domain
↑ │
│ ▼
ports pure policies
The domain/application core does not import PGF, HTTP frameworks, databases, Wikidata protocols or product-specific models.
One canonical path
There is no parallel grammar engine, family renderer, emergency template engine or automatic fallback language.
If a requested released language/profile cannot realize the request correctly, generation fails.
Anti-Corruption Layers
External systems end at explicit adapters:
Kristal ─┐
Orgo ─┤
eThikos ─┼─→ ACL → CommunicationRequest
KeenKonnect ─┤
other systems ─┘
The core never needs to know an Orgo task schema or a Kristal wire format.
Runtime immutability
A request is pinned to one immutable RuntimeSet. Grammar, lexical data, bridge contract and conformance identity cannot change mid-request.
See RuntimeSets.