An architecture you can read, verify, and own

Every layer of a Keewo application is inspectable: contracts are YAML, modules are XML, provenance is hash-verified, and governance controls are documented. Public repository access is planned.

Readable modules

Application modules are declarative XML files covering data, logic, UI, security, tests, themes, and i18n. No compiled black box — teams can read and review every artifact.

YAML contracts

Feature contracts are structured YAML that define entities, screens, functions, and security rules. Contracts are the governed source of truth for generated code.

Hash-verified provenance

Every generated file carries a manifest with spec hash, content hash, generator version, and timestamp — a Logic Bill of Materials for business features.

Transparent governance

Governance controls are numbered, documented, and enforced at known pipeline stages. See the Governance Control Catalog for the full list.

What "open architecture" means

Every artifact in the delivery chain can be inspected by humans and tools: requirement documents, YAML contracts, generated XML modules, hash-verified manifests, and governance check results. Nothing is hidden behind proprietary runtime behavior.

Public repository access

Public repository access is coming soon. The architecture is designed for inspectability and community contribution from the ground up. Documentation and technical content are available now.