AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
system-detail K.PUBLIC.SYSTEM

kap-language

KAP Language

A declarative contract style used across this repository to describe the public site, navigation, content, layout, motion, time, traffic and early access in machine-readable files (.kap).

Status: active Last updated: 2026-08-16

System ID

kap-language

Status

active

Architecture layers

  • L3 Public Data (contracts)
  • L2 Public Application (consumers)

Inputs

  • Public-safe facts about the site, navigation, content and traffic channel

Outputs

  • Declarative contract files (kap/*.kap) and their machine-verified JSON companions (contracts/*.json)

Public interfaces

  • kap/*.kap (declarative documentation)
  • contracts/*.json (machine-verified runtime companions)

Connected systems

Security boundary

KAP files are declarative documentation only. They never import, modify or execute code from ../aenet or ../k-language. They are never a log file and never a database.

Data direction

Public facts → declarative contracts → validated JSON companions. No executable path in any direction.

What

Express public, read-only contracts in a declarative KAP style so the public surface can be described, checked and validated without any executable path into the AENET Core.

Why

The public repository needs a way to declare contracts (site, navigation, content, traffic, time, layout, motion) that is inspectable by humans and machines but can never run anything or reach the core.

How

Public facts → declarative contracts → validated JSON companions. No executable path in any direction.

  • Declare the public site identity and hard limits (public-site.kap)
  • Declare navigation topology (public-navigation.kap)
  • Declare content sources → snapshot targets (public-content.kap)
  • Declare the anonymous traffic channel contract (public-traffic.kap)
  • Declare time, layout, motion, language, system map, queue and early access contracts

Example

kap/public-site.kap declares the public site identity and hard limits; its machine-verified JSON companion lives in contracts/ and is validated by npm run check.

Inputs

  • Public-safe facts about the site, navigation, content and traffic channel

Outputs

  • Declarative contract files (kap/*.kap) and their machine-verified JSON companions (contracts/*.json)

Dependencies

aenet-cloud-public

Lifecycle

  • declarative authoring
  • JSON runtime companion
  • contract validation

Use cases

  • Document the public site contract and limits
  • Declare the anonymous traffic channel contract
  • Provide machine-verified JSON companions validated by npm run check

Limitations

  • KAP files in this repository were not parsed by a kap CLI at authoring time
  • If the KAP runtime does not support a construct, the JSON contract is the authority
  • KAP is not an executable path — never a control channel

Connected systems

  • AENET Cloud Public — The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
  • Early Access — The public waitlist for testing the AENET public gateway. Applicant records live only in D1, are never indexed, exported or published, and registration is fail-closed without Turnstile verification.
  • K Language — The language family that KAP declarative contracts are associated with. This repository contains limited public evidence about K Language internals.
  • Public API — The read-only public API v1 of AENET Cloud Public. It serves public status, time, architecture, development queue, roadmap and early access — with a strictly bounded surface.
  • Public Time — The public time service of AENET Cloud Public. It serves canonical UTC with an explicit quality, and never claims atomic verification without a verified atomic source.
  • RGBM — The semantic color role system of the AENET public UI. Components reference roles (navigation, action, insight, guard, system, warning) — never raw color names.
  • UI Contract — The single source of truth for the public UI structure — pages, navigation, components, coordinates, states, motion, colors, typography and locales — consumed by both the web and Swift renderers.
  • XGRID — The adaptive spatial grid system of the AENET public UI: desktop 12 / tablet 8 / mobile 1 columns, content-intrinsic sizing, with a 1920x1080 canvas used only as a design reference.

Questions people ask

These questions are answered by the content on this page.

  • What is KAP?
  • What is the KAP language used for?
  • What KAP contracts exist in AENET Cloud Public?
  • Is KAP executable or connected to the AENET Core?
  • What is the relationship between KAP and K Language?

Evidence

Verified states only — nothing on this page is a prediction.

  • kap/README.md
  • kap/*.kap
  • contracts/public-language.contract.json

Next step